/linux-6.14.4/Documentation/devicetree/bindings/phy/ |
D | realtek,usb2phy.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause) 4 --- 6 $schema: http://devicetree.org/meta-schemas/core.yaml# 11 - Stanley Chang <[email protected]> 20 The USB architecture includes three XHCI controllers. 23 XHCI controller#0 -- usb2phy -- phy#0 24 |- usb3phy -- phy#0 25 XHCI controller#1 -- usb2phy -- phy#0 26 XHCI controller#2 -- usb2phy -- phy#0 27 |- usb3phy -- phy#0 [all …]
|
/linux-6.14.4/Documentation/devicetree/bindings/interrupt-controller/ |
D | img,pdc-intc.txt | 10 - compatible: Specifies the compatibility list for the interrupt controller. 11 The type shall be <string> and the value shall include "img,pdc-intc". 13 - reg: Specifies the base PDC physical address(s) and size(s) of the 14 addressable register space. The type shall be <prop-encoded-array>. 16 - interrupt-controller: The presence of this property identifies the node 19 - #interrupt-cells: Specifies the number of cells needed to encode an 22 - num-perips: Number of waking peripherals. 24 - num-syswakes: Number of SysWake inputs. 26 - interrupts: List of interrupt specifiers. The first specifier shall be the 34 - <1st-cell>: The interrupt-number that identifies the interrupt source. [all …]
|
D | riscv,cpu-intc.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause 3 --- 4 $id: http://devicetree.org/schemas/interrupt-controller/riscv,cpu-intc.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: RISC-V Hart-Level Interrupt Controller (HLIC) 10 RISC-V cores include Control Status Registers (CSRs) which are local to 11 each CPU core (HART in RISC-V terminology) and can be read or written by 16 The RISC-V supervisor ISA manual specifies three interrupt sources that are 19 cores. The timer interrupt comes from an architecturally mandated real- 22 the HLIC, which are routed via the platform-level interrupt controller [all …]
|
/linux-6.14.4/arch/sh/boards/mach-dreamcast/ |
D | irq.c | 1 // SPDX-License-Identifier: GPL-2.0 18 * Dreamcast System ASIC Hardware Events - 28 * There are three 32-bit ESRs located at 0xa05f6900 - 0xa05f6908. Event 29 * types can be found in arch/sh/include/mach-dreamcast/mach/sysasic.h. 30 * There are three groups of EMRs that parallel the ESRs. Each EMR group 31 * corresponds to an IRQ, so 0xa05f6910 - 0xa05f6918 triggers IRQ 13, 32 * 0xa05f6920 - 0xa05f6928 triggers IRQ 11, and 0xa05f6930 - 0xa05f6938 39 * 6900/6910 - Events 0-31, IRQ 13 40 * 6904/6924 - Events 32-63, IRQ 11 41 * 6908/6938 - Events 64-95, IRQ 9 [all …]
|
/linux-6.14.4/drivers/gpu/drm/amd/include/ivsrcid/dcn/ |
D | irqsrcs_dcn_1_0.h | 30 …C_I2C_SW_DONE 1 // DC_I2C SW done DC_I2C_SW_DONE_INTERRUPT DISP_INTERRUPT_STATUS Level 33 … // DC_I2C DDC1 HW done DOUT_IHC_I2C_DDC1_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 36 … // DC_I2C DDC2 HW done DOUT_IHC_I2C_DDC2_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 39 … // DC_I2C DDC3 HW done DOUT_IHC_I2C_DDC3_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 42 … // DC_I2C_DDC4 HW done DOUT_IHC_I2C_DDC4_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 45 … // DC_I2C_DDC5 HW done DOUT_IHC_I2C_DDC5_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 48 … // DC_I2C_DDC6 HW done DOUT_IHC_I2C_DDC6_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 51 …DC_I2C_DDCVGA HW done DOUT_IHC_I2C_DDCVGA_HW_DONE_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level 54 …DC1 read request DC_I2C_DDC1_READ_REQUEST_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level / Pulse 57 …DC2 read request DC_I2C_DDC2_READ_REQUEST_INTERRUPT DISP_INTERRUPT_STATUS_CONTINUE21 Level / Pulse [all …]
|
/linux-6.14.4/Documentation/devicetree/bindings/opp/ |
D | opp-v2-base.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/opp/opp-v2-base.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Viresh Kumar <[email protected]> 13 Devices work at voltage-current-frequency combinations and some implementations 25 pattern: '^opp-table(-[a-z0-9]+)?$' 27 opp-shared: 36 '^opp(-?[0-9]+)*$': 39 One or more OPP nodes describing voltage-current-frequency combinations. [all …]
|
/linux-6.14.4/Documentation/scheduler/ |
D | sched-stats.rst | 20 …b/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/scheduler/sched-stats.txt?id=1e1dbb25… 24 12 which was in the kernel from 2.6.13-2.6.19 (version 13 never saw a kernel 25 release). Some counters make more sense to be per-runqueue; other to be 26 per-domain. Note that domains (and their associated information) will only 29 In version 14 of schedstat, there is at least one level of domain 35 are no architectures which need more than three domain levels. The first 39 …https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/sched-stats.… 44 …https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/sched-stats.… 53 Note that any such script will necessarily be version-specific, as the main 58 -------------- [all …]
|
/linux-6.14.4/Documentation/virt/ |
D | paravirt_ops.rst | 1 .. SPDX-License-Identifier: GPL-2.0 13 including native machine -- without any hypervisors. 16 corresponding to low-level critical instructions and high-level 18 time by enabling binary patching of the low-level critical operations 21 pv_ops operations are classified into three categories: 23 - simple indirect call 24 These operations correspond to high-level functionality where it is 27 - indirect call which allows optimization with binary patch 28 Usually these operations correspond to low-level critical instructions. They 32 - a set of macros for hand written assembly code
|
/linux-6.14.4/Documentation/usb/ |
D | functionfs.rst | 12 that kernel level composite functions provide when they are added to 28 For more information about FunctionFS descriptors see :doc:`functionfs-desc` 48 level it would look like this:: 51 $ mkdir /dev/ffs-mtp && mount -t functionfs mtp /dev/ffs-mtp 52 $ ( cd /dev/ffs-mtp && mtp-daemon ) & 53 $ mkdir /dev/ffs-hid && mount -t functionfs hid /dev/ffs-hid 54 $ ( cd /dev/ffs-hid && hid-daemon ) & 56 On kernel level the gadget checks ffs_data->dev_name to identify 64 parameter's value is just a one-element list, then the behaviour 84 zero-copy fashion, for instance between IIO and the USB stack. [all …]
|
/linux-6.14.4/Documentation/power/regulator/ |
D | overview.rst | 26 - Regulator 27 - Electronic device that supplies power to other devices. 31 Input Voltage -> Regulator -> Output Voltage 34 - PMIC 35 - Power Management IC. An IC that contains numerous 39 - Consumer 40 - Electronic device that is supplied power by a regulator. 41 Consumers can be classified into two types:- 52 - Power Domain 53 - Electronic circuit that is supplied its input power by the [all …]
|
/linux-6.14.4/arch/m68k/mac/ |
D | macints.c | 1 // SPDX-License-Identifier: GPL-2.0 7 * exclusively use the autovector interrupts (the 'generic level0-level7' 8 * interrupts with exception vectors 0x19-0x1f). The following interrupt levels 10 * 1 - VIA1 11 * - slot 0: one second interrupt (CA2) 12 * - slot 1: VBlank (CA1) 13 * - slot 2: ADB data ready (SR full) 14 * - slot 3: ADB data (CB2) 15 * - slot 4: ADB clock (CB1) 16 * - slot 5: timer 2 [all …]
|
/linux-6.14.4/Documentation/devicetree/bindings/watchdog/ |
D | linux,wdt-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/watchdog/linux,wdt-gpio.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 7 title: GPIO-controlled Watchdog 10 - Guenter Roeck <linux@roeck-us.net> 11 - Robert Marko <[email protected]> 15 const: linux,wdt-gpio 24 - description: 25 Either a high-to-low or a low-to-high transition clears the WDT counter. [all …]
|
/linux-6.14.4/Documentation/ABI/testing/ |
D | sysfs-driver-wacom | 4 Contact: linux-[email protected] 14 Contact: linux-[email protected] 25 Contact: linux-[email protected] 30 button is pressed on the stylus. This luminance level is 31 normally lower than the level when a button is pressed. 35 Contact: linux-[email protected] 44 Contact: linux-[email protected] 49 24HD) status LEDs is active (0..3). The other three LEDs on the 54 Contact: linux-[email protected] 58 and Cintiq 24HD) status LEDs is active (0..3). The other three LEDs on [all …]
|
/linux-6.14.4/Documentation/hwmon/ |
D | lm78.rst | 6 * National Semiconductor LM78 / LM78-J 10 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports) 20 Addresses scanned: I2C 0x28 - 0x2f, ISA 0x290 (8 I/O ports) 28 - Frodo Looijaard <[email protected]> 29 - Jean Delvare <[email protected]> 32 ----------- 34 This driver implements support for the National Semiconductor LM78, LM78-J 37 There is almost no difference between the three supported chips. Functionally, 38 the LM78 and LM78-J are exactly identical. The LM79 has one more VID line, 40 From here on, LM7* means either of these three types. [all …]
|
D | pc87360.rst | 22 ----------------- 25 Chip initialization level: 27 - 0: None 28 - **1**: Forcibly enable internal voltage and temperature channels, 30 - 2: Forcibly enable all voltage and temperature channels, except in9 31 - 3: Forcibly enable all voltage and temperature channels, including in9 42 ----------- 49 hardware monitoring chipsets, not only controlling and monitoring three fans, 56 PC87360 - 2 2 - 0xE1 57 PC87363 - 2 2 - 0xE8 [all …]
|
/linux-6.14.4/arch/x86/include/asm/ |
D | pgtable_32.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 8 * The Linux memory management assumes a three-level page table setup. On 9 * the i386, we use that, but "fold" the mid level into the top-level page 10 * table, so that we physically have the same two-level page table as the 36 # include <asm/pgtable-3level.h> 38 # include <asm/pgtable-2level.h> 57 * the PMD's in addition to the pages required for the last level pagetables. 70 * with only a host target support using a 32-bit type for internal 73 #define LOWMEM_PAGES ((((_ULL(2)<<31) - __PAGE_OFFSET) >> PAGE_SHIFT))
|
/linux-6.14.4/Documentation/admin-guide/ |
D | sysfs-rules.rst | 4 The kernel-exported sysfs exports internal kernel implementation details 11 low-level userspace applications, with a new kernel release, the users 12 of sysfs must follow some rules to use an as-abstract-as-possible way to 21 - Do not use libsysfs 23 offer any abstraction, it exposes all the kernel driver-core 31 - sysfs is always at ``/sys`` 38 - devices are only "devices" 39 There is no such thing like class-, bus-, physical devices, 41 just simply a "device". Class-, bus-, physical, ... types are just 47 - devpath (``/devices/pci0000:00/0000:00:1d.1/usb2/2-2/2-2:1.0``) [all …]
|
/linux-6.14.4/arch/parisc/include/asm/ |
D | pgalloc.h | 1 /* SPDX-License-Identifier: GPL-2.0 */ 14 #include <asm-generic/pgalloc.h> 16 /* Allocate the top level pgd (page directory) */ 24 /* Three Level Page Table Support for pmd's */
|
/linux-6.14.4/Documentation/devicetree/bindings/usb/ |
D | chipidea,usb2-imx.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/usb/chipidea,usb2-imx.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Xu Yang <[email protected]> 15 - enum: 16 - fsl,imx27-usb 17 - items: 18 - enum: 19 - fsl,imx23-usb [all …]
|
/linux-6.14.4/Documentation/userspace-api/media/v4l/ |
D | pixfmt-srggb8-pisp-comp.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later 3 .. _v4l2-pix-fmt-pisp-comp1-rggb: 4 .. _v4l2-pix-fmt-pisp-comp1-grbg: 5 .. _v4l2-pix-fmt-pisp-comp1-gbrg: 6 .. _v4l2-pix-fmt-pisp-comp1-bggr: 7 .. _v4l2-pix-fmt-pisp-comp1-mono: 8 .. _v4l2-pix-fmt-pisp-comp2-rggb: 9 .. _v4l2-pix-fmt-pisp-comp2-grbg: 10 .. _v4l2-pix-fmt-pisp-comp2-gbrg: 11 .. _v4l2-pix-fmt-pisp-comp2-bggr: [all …]
|
/linux-6.14.4/Documentation/core-api/ |
D | genericirq.rst | 7 :Copyright: |copy| 2005-2010: Thomas Gleixner 8 :Copyright: |copy| 2005-2006: Ingo Molnar 29 __do_IRQ() super-handler, which is able to deal with every type of 36 - Level type 38 - Edge type 40 - Simple type 44 - Fast EOI type 46 In the SMP world of the __do_IRQ() super-handler another type was 49 - Per CPU type 51 This split implementation of high-level IRQ handlers allows us to [all …]
|
/linux-6.14.4/lib/zlib_inflate/ |
D | inffast.c | 1 /* inffast.c -- fast decoding 2 * Copyright (C) 1995-2004 Mark Adler 33 available, an end-of-block is encountered, or a data error is encountered. 40 state->mode == LEN 41 strm->avail_in >= 6 42 strm->avail_out >= 258 43 start >= strm->avail_out 44 state->bits < 8 46 On return, state->mode is one of: 48 LEN -- ran out of enough output space or enough available input [all …]
|
/linux-6.14.4/Documentation/devicetree/bindings/ata/ |
D | imx-sata.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) 3 --- 4 $id: http://devicetree.org/schemas/ata/imx-sata.yaml# 5 $schema: http://devicetree.org/meta-schemas/core.yaml# 10 - Shawn Guo <[email protected]> 14 with some special extensions at integration level. 19 - fsl,imx53-ahci 20 - fsl,imx6q-ahci 21 - fsl,imx6qp-ahci 22 - fsl,imx8qm-ahci [all …]
|
/linux-6.14.4/Documentation/virt/hyperv/ |
D | overview.rst | 1 .. SPDX-License-Identifier: GPL-2.0 6 enlightened guest on Microsoft's Hyper-V hypervisor. Hyper-V 7 consists primarily of a bare-metal hypervisor plus a virtual machine 10 partitions. In this documentation, references to Hyper-V usually 15 Hyper-V runs on x86/x64 and arm64 architectures, and Linux guests 16 are supported on both. The functionality and behavior of Hyper-V is 19 Linux Guest Communication with Hyper-V 20 -------------------------------------- 21 Linux guests communicate with Hyper-V in four different ways: 24 some guest actions trap to Hyper-V. Hyper-V emulates the action and [all …]
|
/linux-6.14.4/Documentation/arch/m68k/ |
D | buddha-driver.rst | 8 ------------------------------------------------------------------------ 11 Buddha-part of the Catweasel Zorro-II version 21 product number: 0 (42 for Catweasel Z-II) 23 Rom-vector: $1000 25 The card should be a Z-II board, size 64K, not for freemem 26 list, Rom-Vektor is valid, no second Autoconfig-board on the 30 as the Amiga Kickstart does: The lower nibble of the 8-Bit 36 otherwise your chance is only 1:16 to find the board :-). 38 The local memory-map is even active when mapped to $e8: 41 $0-$7e Autokonfig-space, see Z-II docs. [all …]
|