Home
last modified time | relevance | path

Searched +full:five +full:- +full:cell (Results 1 – 22 of 22) sorted by relevance

/kernel/linux/linux-4.19/Documentation/devicetree/bindings/mfd/
Darizona.txt8 - compatible : One of the following chip-specific strings:
18 - reg : I2C slave address when connected using I2C, chip select number when
21 - interrupts : The interrupt line the /IRQ signal for the device is
23 - interrupt-controller : Arizona class devices contain interrupt controllers
25 - #interrupt-cells: the number of cells to describe an IRQ, this should be 2.
26 The first cell is the IRQ number.
27 The second cell is the flags, encoded as the trigger masks from
28 Documentation/devicetree/bindings/interrupt-controller/interrupts.txt
30 - gpio-controller : Indicates this device is a GPIO controller.
31 - #gpio-cells : Must be 2. The first cell is the pin number and the
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/dma/
Dst,stm32-mdma.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/st,stm32-mdma.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The STM32 MDMA is a general-purpose direct memory access controller capable of
13 described in the dma.txt file, using a five-cell specifier for each channel:
14 a phandle to the MDMA controller plus the following five integer cells:
22 -bit 0-1: Source increment mode
26 -bit 2-3: Destination increment mode
30 -bit 8-9: Source increment offset size
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/dma/
Dstm32-mdma.txt3 The STM32 MDMA is a general-purpose direct memory access controller capable of
7 - compatible: Should be "st,stm32h7-mdma"
8 - reg: Should contain MDMA registers location and length. This should include
9 all of the per-channel registers.
10 - interrupts: Should contain the MDMA interrupt.
11 - clocks: Should contain the input clock of the DMA instance.
12 - resets: Reference to a reset controller asserting the DMA controller.
13 - #dma-cells : Must be <5>. See DMA client paragraph for more details.
16 - dma-channels: Number of DMA channels supported by the controller.
17 - dma-requests: Number of DMA request signals supported by the controller.
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/pwm/
Dpwm-mediatek.txt4 - compatible: should be "mediatek,<name>-pwm":
5 - "mediatek,mt2712-pwm": found on mt2712 SoC.
6 - "mediatek,mt7622-pwm": found on mt7622 SoC.
7 - "mediatek,mt7623-pwm": found on mt7623 SoC.
8 - "mediatek,mt7628-pwm": found on mt7628 SoC.
9 - reg: physical base address and length of the controller's registers.
10 - #pwm-cells: must be 2. See pwm.txt in this directory for a description of
11 the cell format.
12 - clocks: phandle and clock specifier of the PWM reference clock.
13 - clock-names: must contain the following, except for MT7628 which
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/mfd/
Dwlf,arizona.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - patches@opensource.cirrus.com
17 - $ref: /schemas/sound/wlf,arizona.yaml#
18 - $ref: /schemas/regulator/wlf,arizona.yaml#
19 - $ref: /schemas/extcon/wlf,arizona.yaml#
20 - if:
25 - cirrus,cs47l24
26 - wlf,wm1831
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pwm/
Dpwm-mediatek.txt4 - compatible: should be "mediatek,<name>-pwm":
5 - "mediatek,mt2712-pwm": found on mt2712 SoC.
6 - "mediatek,mt7622-pwm": found on mt7622 SoC.
7 - "mediatek,mt7623-pwm": found on mt7623 SoC.
8 - "mediatek,mt7628-pwm": found on mt7628 SoC.
9 - "mediatek,mt7629-pwm": found on mt7629 SoC.
10 - "mediatek,mt8516-pwm": found on mt8516 SoC.
11 - reg: physical base address and length of the controller's registers.
12 - #pwm-cells: must be 2. See pwm.yaml in this directory for a description of
13 the cell format.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/virtio/
Diommu.txt3 When virtio-iommu uses the PCI transport, its programming interface is
6 masters. Therefore, the PCI root complex that hosts the virtio-iommu
11 - compatible: Should be "virtio,pci-iommu"
12 - reg: PCI address of the IOMMU. As defined in the PCI Bus
13 Binding reference [1], the reg property is a five-cell
18 - #iommu-cells: Each platform DMA master managed by the IOMMU is assigned
20 For virtio-iommu, #iommu-cells must be 1.
24 - DMA from the IOMMU device isn't managed by another IOMMU. Therefore the
25 virtio-iommu node doesn't have an "iommus" property, and is omitted from
26 the iommu-map property of the root complex.
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/pci/
Dpci.txt3 PCI Bus Binding to: IEEE Std 1275-1994
4 https://www.devicetree.org/open-firmware/bindings/pci/pci2_1.pdf
9 https://www.devicetree.org/open-firmware/practice/imap/imap0_9d.pdf
14 - linux,pci-domain:
21 - max-link-speed:
27 - reset-gpios:
30 - supports-clkreq:
34 not to advertise ASPM L1 Sub-States support if there is no CLKREQ signal.
36 PCI-PCI Bridge properties
37 -------------------------
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/powerpc/fsl/
Dpamu.txt5 The PAMU is an I/O MMU that provides device-to-memory access control and
10 - compatible : <string>
11 First entry is a version-specific string, such as
12 "fsl,pamu-v1.0". The second is "fsl,pamu".
13 - ranges : <prop-encoded-array>
18 PAMU v1.0, on an SOC that has five PAMU devices, the size
20 - interrupts : <prop-encoded-array>
25 - #address-cells: <u32>
27 - #size-cells : <u32>
31 - reg : <prop-encoded-array>
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/powerpc/fsl/
Dpamu.txt5 The PAMU is an I/O MMU that provides device-to-memory access control and
10 - compatible : <string>
11 First entry is a version-specific string, such as
12 "fsl,pamu-v1.0". The second is "fsl,pamu".
13 - ranges : <prop-encoded-array>
18 PAMU v1.0, on an SOC that has five PAMU devices, the size
20 - interrupts : <prop-encoded-array>
25 - #address-cells: <u32>
27 - #size-cells : <u32>
31 - reg : <prop-encoded-array>
[all …]
/kernel/linux/linux-4.19/Documentation/devicetree/bindings/thermal/
Dthermal.txt14 There are five types of nodes involved to describe thermal bindings:
15 - thermal sensors: devices which may be used to take temperature
17 - cooling devices: devices which may be used to dissipate heat.
18 - trip points: describe key temperatures at which cooling is recommended. The
20 - cooling maps: used to describe links between trip points and cooling devices;
21 - thermal zones: used to describe thermal data within the hardware;
33 - #thermal-sensor-cells: Used to provide sensor device specific information
35 Size: one cell nodes with only one sensor, and at least 1 on nodes
62 - #cooling-cells: Used to provide cooling device specific information
64 Size: one cell to specify minimum and maximum cooling state used
[all …]
/kernel/linux/linux-4.19/arch/powerpc/platforms/
DKconfig.cputype1 # SPDX-License-Identifier: GPL-2.0
3 bool "64-bit kernel"
7 This option selects whether a 32-bit or a 64-bit kernel
15 There are five families of 32 bit PowerPC chips supported.
109 bool "Cell Broadband Engine"
164 default "cell" if CELL_CPU
257 ---help---
258 This option enables kernel support for larger than 32-bit physical
263 is platform-dependent.
270 ---help---
[all …]
/kernel/linux/linux-5.10/arch/powerpc/platforms/
DKconfig.cputype1 # SPDX-License-Identifier: GPL-2.0
8 bool "64-bit kernel"
11 This option selects whether a 32-bit or a 64-bit kernel
22 There are five families of 32 bit PowerPC chips supported.
127 bool "Cell Broadband Engine"
187 default "cell" if CELL_CPU
277 This option enables kernel support for larger than 32-bit physical
282 is platform-dependent.
297 any affect on a non-altivec cpu (it does, however add code to the
313 VSX (P7 and above), but does not have any affect on a non-VSX
[all …]
/kernel/linux/linux-4.19/drivers/mtd/nand/raw/
DKconfig20 <http://www.linux-mtd.infradead.org/doc/nand.html>.
166 This is a reimplementation of M-Systems DiskOnChip 2000,
168 as opposed to the earlier self-contained MTD device drivers.
215 data on your device (created by non-Linux tools such as M-Systems'
245 partitioning to segregate write-protected blocks. On the Treo680, the
246 first five erase blocks (256KiB each) are write-protected, followed
270 include NAND flash controllers with built-in hardware ECC
296 - PXA3xx processors (NFCv1)
297 - 32-bit Armada platforms (XP, 37x, 38x, 39x) (NFCv2)
298 - 64-bit Aramda platforms (7k, 8k) (NFCv2)
[all …]
/kernel/linux/linux-4.19/Documentation/admin-guide/
Dunicode.rst4 Last update: 2005-01-17, version 1.4
10 http://www.lanana.org/docs/unicode/admin-guide/unicode.rst
13 ------------
16 characters to fonts. By downloading a single Unicode-to-font table,
17 both the eight-bit character sets and UTF-8 mode are changed to use
20 This changes the semantics of the eight-bit character tables subtly.
26 LAT1_MAP Latin-1 (ISO 8859-1) ESC ( B
34 permits for example the use of block graphics even with a Latin-1 font
38 codes nor their uses match ISO 2022; Linux has two 8-bit codes (G0 and
39 G1), whereas ISO 2022 has four 7-bit codes (G0-G3).
[all …]
/kernel/linux/linux-5.10/Documentation/admin-guide/
Dunicode.rst4 Last update: 2005-01-17, version 1.4
10 http://www.lanana.org/docs/unicode/admin-guide/unicode.rst
13 ------------
16 characters to fonts. By downloading a single Unicode-to-font table,
17 both the eight-bit character sets and UTF-8 mode are changed to use
20 This changes the semantics of the eight-bit character tables subtly.
26 LAT1_MAP Latin-1 (ISO 8859-1) ESC ( B
34 permits for example the use of block graphics even with a Latin-1 font
38 codes nor their uses match ISO 2022; Linux has two 8-bit codes (G0 and
39 G1), whereas ISO 2022 has four 7-bit codes (G0-G3).
[all …]
/kernel/linux/linux-5.10/drivers/mfd/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
44 tristate "Active-semi ACT8945A"
49 Support for the ACT8945A PMIC from Active-semi. This device
50 features three step-down DC/DC converters and four low-dropout
66 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
69 called sun4i-gpadc.
88 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
119 over at91-usart-serial driver and usart-spi-driver. Only one function
135 tristate "Atmel HLCDC (High-end LCD Controller)"
172 tristate "X-Powers AC100"
[all …]
/kernel/linux/linux-4.19/drivers/mfd/
DKconfig17 ---help---
33 tristate "Active-semi ACT8945A"
38 Support for the ACT8945A PMIC from Active-semi. This device
39 features three step-down DC/DC converters and four low-dropout
55 sun4i-gpadc-iio and the hwmon driver iio_hwmon.
58 called sun4i-gpadc.
77 tablets etc. It has 4 DC/DC step-down regulators, 3 DC/DC step-down
114 tristate "Atmel HLCDC (High-end LCD Controller)"
151 tristate "X-Powers AC100"
155 If you say Y here you get support for the X-Powers AC100 audio codec
[all …]
/kernel/linux/linux-5.10/tools/include/uapi/linux/
Dbpf.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
2 /* Copyright (c) 2011-2014 PLUMgrid, http://plumgrid.com
21 #define BPF_DW 0x18 /* double word (64-bit) */
30 #define BPF_TO_LE 0x00 /* convert to little-endian */
31 #define BPF_TO_BE 0x08 /* convert to big-endian */
62 /* BPF has 10 general purpose 64-bit registers and stack frame. */
90 /* BPF syscall commands, see bpf(2) man-page for details. */
260 /* cgroup-bpf attach flags used in BPF_PROG_ATTACH command
264 * BPF_F_ALLOW_OVERRIDE: If a sub-cgroup installs some bpf program,
265 * the program in this cgroup yields to sub-cgroup program.
[all …]
/kernel/linux/linux-5.10/include/uapi/linux/
Dbpf.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
2 /* Copyright (c) 2011-2014 PLUMgrid, http://plumgrid.com
21 #define BPF_DW 0x18 /* double word (64-bit) */
30 #define BPF_TO_LE 0x00 /* convert to little-endian */
31 #define BPF_TO_BE 0x08 /* convert to big-endian */
62 /* BPF has 10 general purpose 64-bit registers and stack frame. */
90 /* BPF syscall commands, see bpf(2) man-page for details. */
260 /* cgroup-bpf attach flags used in BPF_PROG_ATTACH command
264 * BPF_F_ALLOW_OVERRIDE: If a sub-cgroup installs some bpf program,
265 * the program in this cgroup yields to sub-cgroup program.
[all …]
/kernel/linux/linux-4.19/tools/include/uapi/linux/
Dbpf.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
2 /* Copyright (c) 2011-2014 PLUMgrid, http://plumgrid.com
21 #define BPF_DW 0x18 /* double word (64-bit) */
30 #define BPF_TO_LE 0x00 /* convert to little-endian */
31 #define BPF_TO_BE 0x08 /* convert to big-endian */
62 /* BPF has 10 general purpose 64-bit registers and stack frame. */
84 /* BPF syscall commands, see bpf(2) man-page for details. */
181 /* cgroup-bpf attach flags used in BPF_PROG_ATTACH command
185 * BPF_F_ALLOW_OVERRIDE: If a sub-cgroup installs some bpf program,
186 * the program in this cgroup yields to sub-cgroup program.
[all …]
/kernel/linux/linux-4.19/include/uapi/linux/
Dbpf.h1 /* SPDX-License-Identifier: GPL-2.0 WITH Linux-syscall-note */
2 /* Copyright (c) 2011-2014 PLUMgrid, http://plumgrid.com
21 #define BPF_DW 0x18 /* double word (64-bit) */
30 #define BPF_TO_LE 0x00 /* convert to little-endian */
31 #define BPF_TO_BE 0x08 /* convert to big-endian */
62 /* BPF has 10 general purpose 64-bit registers and stack frame. */
84 /* BPF syscall commands, see bpf(2) man-page for details. */
183 /* cgroup-bpf attach flags used in BPF_PROG_ATTACH command
187 * BPF_F_ALLOW_OVERRIDE: If a sub-cgroup installs some bpf program,
188 * the program in this cgroup yields to sub-cgroup program.
[all …]