| /linux-6.8/Documentation/devicetree/bindings/gpio/ |
| D | nvidia,tegra186-gpio.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/gpio/nvidia,tegra186-gpio.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Thierry Reding <thierry.reding@gmail.com>
11 - Jon Hunter <jonathanh@nvidia.com>
14 Tegra186 contains two GPIO controllers; a main controller and an "AON"
15 controller. This binding document applies to both controllers. The register
16 layouts for the controllers share many similarities, but also some
25 a) Security registers, which allow configuration of allowed access to the
[all …]
|
| /linux-6.8/Documentation/driver-api/ |
| D | edac.rst | 5 ----------------------------------------
8 *sockets, *socket sets*, *banks*, *rows*, *chip-select rows*, *channels*,
43 It is typically the highest hierarchy on a Fully-Buffered DIMM memory
52 * Single-channel
55 only. E. g. if the data is 64 bits-wide, the data flows to the CPU using
56 one 64 bits parallel access. Typically used with SDR, DDR, DDR2 and DDR3
57 memories. FB-DIMM and RAMBUS use a different concept for channel, so
60 * Double-channel
63 dimms, accessed at the same time. E. g. if the DIMM is 64 bits-wide (72
65 access.
[all …]
|
| /linux-6.8/Documentation/admin-guide/ |
| D | cgroup-v2.rst | 1 .. _cgroup-v2:
11 conventions of cgroup v2. It describes all userland-visible aspects
14 v1 is available under :ref:`Documentation/admin-guide/cgroup-v1/index.rst <cgroup-v1>`.
19 1-1. Terminology
20 1-2. What is cgroup?
22 2-1. Mounting
23 2-2. Organizing Processes and Threads
24 2-2-1. Processes
25 2-2-2. Threads
26 2-3. [Un]populated Notification
[all …]
|
| /linux-6.8/Documentation/devicetree/bindings/memory-controllers/ |
| D | intel,ixp4xx-expansion-bus-controller.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/memory-controllers/intel,ixp4xx-expansion-bus-controller.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 The IXP4xx expansion bus controller handles access to devices on the
11 memory-mapped expansion bus on the Intel IXP4xx family of system on chips,
15 - Linus Walleij <linus.walleij@linaro.org>
19 pattern: '^bus@[0-9a-f]+$'
23 - enum:
24 - intel,ixp42x-expansion-bus-controller
[all …]
|
| /linux-6.8/Documentation/driver-api/gpio/ |
| D | legacy.rst | 5 This provides an overview of GPIO access conventions on Linux.
13 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
21 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
22 non-dedicated pin can be configured as a GPIO; and most chips have at least
27 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
32 - Output values are writable (high=1, low=0). Some chips also have
34 value might be driven ... supporting "wire-OR" and similar schemes
37 - Input values are likewise readable (1, 0). Some chips support readback
38 of pins configured as "output", which is very useful in such "wire-OR"
39 cases (to support bidirectional signaling). GPIO controllers may have
[all …]
|
| /linux-6.8/drivers/spi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
13 dynamic device discovery; some are even write-only or read-only.
17 chips, analog to digital (and d-to-a) converters, and more.
24 work with most such devices and controllers.
44 If your system has an master-capable SPI controller (which
56 by providing a high-level interface to send memory-like commands.
112 tristate "Aspeed flash controllers in SPI mode"
145 supports spi-mem interface.
224 this code to manage the per-word or per-transfer accesses to the
254 Flash over 1/2/4-bit wide bus. Enable this option if you have a
[all …]
|
| /linux-6.8/Documentation/gpu/ |
| D | tegra.rst | 11 supports the built-in GPU, comprised of the gr2d and gr3d engines. Starting
18 - A host1x driver that provides infrastructure and access to the host1x
21 - A KMS driver that supports the display controllers as well as a number of
24 - A set of custom userspace IOCTLs that can be used to submit jobs to the
40 device using a driver-provided function which will set up the bits specific to
48 -------------------------------
50 .. kernel-doc:: include/linux/host1x.h
52 .. kernel-doc:: drivers/gpu/host1x/bus.c
56 --------------------------
58 .. kernel-doc:: drivers/gpu/host1x/syncpt.c
[all …]
|
| /linux-6.8/Documentation/core-api/ |
| D | debugging-via-ohci1394.rst | 2 Using physical DMA provided by OHCI-1394 FireWire controllers for debugging
6 ------------
8 Basically all FireWire controllers which are in use today are compliant
9 to the OHCI-1394 specification which defines the controller to be a PCI
12 PCI-Bus master DMA after applying filters defined by the OHCI-1394 driver.
15 ask the OHCI-1394 controller to perform read and write requests on
25 With most FireWire controllers, memory access is limited to the low 4 GB
28 hardware such as x86, x86-64 and PowerPC.
30 At least LSI FW643e and FW643e2 controllers are known to support access to
34 Together with a early initialization of the OHCI-1394 controller for debugging,
[all …]
|
| /linux-6.8/include/sound/ac97/ |
| D | controller.h | 1 /* SPDX-License-Identifier: GPL-2.0
18 * struct ac97_controller - The AC97 controller of the AC-Link
20 * @controllers: linked list of all existing controllers.
21 * @adap: the shell device ac97-%d, ie. ac97 adapter
29 * controllers themselves, excepting for using @dev.
33 struct list_head controllers; member
43 * struct ac97_controller_ops - The AC97 operations
44 * @reset: Cold reset of the AC97 AC-Link.
45 * @warm_reset: Warm reset of the AC97 AC-Link.
51 * access functions. Amongst these, all but the last 2 are mandatory.
[all …]
|
| /linux-6.8/drivers/usb/usbip/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
10 machines direct access to USB devices. It provides the
17 be called usbip-core.
29 module will be called vhci-hcd.
42 int "Number of USB/IP virtual host controllers"
49 virtual host controllers as if adding physical host
50 controllers.
60 module will be called usbip-host.
71 module will be called usbip-vudc.
|
| /linux-6.8/Documentation/devicetree/bindings/fsi/ |
| D | ibm,fsi2spi.yaml | 1 # SPDX-License-Identifier: (GPL-2.0-or-later)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: IBM FSI-attached SPI controllers
10 - Eddie James <eajames@linux.ibm.com>
15 FSI slave and CFAM nodes. This FSI2SPI engine provides access to a number of
16 SPI controllers.
21 - ibm,fsi2spi
25 - description: FSI slave address
28 - compatible
[all …]
|
| /linux-6.8/Documentation/devicetree/bindings/spi/ |
| D | spi-orion.txt | 4 - compatible : should be on of the following:
5 - "marvell,orion-spi" for the Orion, mv78x00, Kirkwood and Dove SoCs
6 - "marvell,armada-370-spi", for the Armada 370 SoCs
7 - "marvell,armada-375-spi", for the Armada 375 SoCs
8 - "marvell,armada-380-spi", for the Armada 38x SoCs
9 - "marvell,armada-390-spi", for the Armada 39x SoCs
10 - "marvell,armada-xp-spi", for the Armada XP SoCs
11 - reg : offset and length of the register set for the device.
13 the SPI direct access mode that some of the Marvell SoCs support
14 additionally to the normal indirect access (PIO) mode. The values
[all …]
|
| /linux-6.8/drivers/usb/gadget/udc/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
7 # NOTE: Gadget support ** DOES NOT ** depend on host-side CONFIG_USB !!
9 # - Host systems (like PCs) need CONFIG_USB (with "A" jacks).
10 # - Peripherals (like PDAs) need CONFIG_USB_GADGET (with "B" jacks).
11 # - Some systems have both kinds of controllers.
13 # With help from a special transceiver and a "Mini-AB" jack, systems with
14 # both kinds of controller can also support "USB On-the-Go" (CONFIG_USB_OTG).
20 # The order here is alphabetical, except that integrated controllers go
22 # - integrated/SOC controllers first
23 # - licensed IP used in both SOC and discrete versions
[all …]
|
| /linux-6.8/drivers/scsi/aic7xxx/ |
| D | aic7xxx_osm_pci.c | 2 * Linux driver attachment glue for PCI based controllers.
4 * Copyright (c) 2000-2001 Adaptec Inc.
18 * 3. Neither the names of the above-listed copyright holders nor the names
50 /* aic7850 based controllers */
52 /* aic7860 based controllers */
58 /* aic7870 based controllers */
65 /* aic7880 based controllers */
75 /* aic7890 based controllers */
83 /* aic7890 based controllers */
91 /* aic7892 based controllers */
[all …]
|
| /linux-6.8/drivers/iommu/ |
| D | exynos-iommu.c | 1 // SPDX-License-Identifier: GPL-2.0-only
12 #include <linux/dma-mapping.h>
38 #define SECT_MASK (~(SECT_SIZE - 1))
39 #define LPAGE_MASK (~(LPAGE_SIZE - 1))
40 #define SPAGE_MASK (~(SPAGE_SIZE - 1))
55 * v1.x - v3.x SYSMMU supports 32bit physical and 32bit virtual address spaces
58 * All SYSMMU controllers in the system support the address spaces of the same
62 static short PG_ENT_SHIFT = -1;
68 ((0 << 15) | (0 << 10)), /* no access */
74 (0 << 4), /* no access */
[all …]
|
| /linux-6.8/Documentation/admin-guide/gpio/ |
| D | gpio-aggregator.rst | 1 .. SPDX-License-Identifier: GPL-2.0-only
11 -----------------------------
13 GPIO controllers are exported to userspace using /dev/gpiochip* character
14 devices. Access control to these devices is provided by standard UNIX file
15 system permissions, on an all-or-nothing basis: either a GPIO controller is
18 The GPIO Aggregator provides access control for a set of one or more GPIOs, by
25 Aggregated GPIO controllers are instantiated and destroyed by writing to
26 write-only attribute files in sysfs.
28 /sys/bus/platform/drivers/gpio-aggregator/
35 .. code-block:: none
[all …]
|
| /linux-6.8/drivers/hid/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
22 most commonly used to refer to the USB-HID specification, but other
27 removed from the HID bus by the transport-layer drivers, such as
58 to work on raw hid events when they want to, and avoid using transport-specific
64 tristate "User-space I/O driver support for HID subsystem"
67 Say Y here if you want to provide HID I/O Drivers from user-space.
68 This allows to write I/O drivers in user-space and feed the data from
71 user-space device.
73 This driver cannot be used to parse HID-reports in user-space and write
74 special HID-drivers. You should use hidraw for that.
[all …]
|
| /linux-6.8/drivers/firewire/ |
| D | init_ohci1394_dma.c | 1 // SPDX-License-Identifier: GPL-2.0-or-later
3 * init_ohci1394_dma.c - Initializes physical DMA on all OHCI 1394 controllers
5 * Copyright (C) 2006-2007 Bernhard Kaindl <bk@suse.de>
7 * Derived from drivers/ieee1394/ohci1394.c and arch/x86/kernel/early-quirks.c
9 * - scan the PCI very early on boot for all OHCI 1394-compliant controllers
10 * - reset and initialize them and make them join the IEEE1394 bus and
11 * - enable physical DMA on them to allow remote debugging
14 * during boot, all OHCI1394 controllers may be claimed by the firewire
18 * be sure that the stack enables it and (re-)attach after the bus reset
28 #include <asm/pci-direct.h> /* for direct PCI config space access */
[all …]
|
| /linux-6.8/drivers/memory/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
10 useful mostly on embedded systems. These could be controllers
13 access to attached peripherals through memory bus.
23 DDR SDRAM controllers.
42 Used to configure the EBI (external bus interface) when the device-
51 This driver provides access to the DPFE interface of Broadcom
68 bool "Baikal-T1 CM2 L2-RAM Cache Control Block"
72 Baikal-T1 CPU is based on the MIPS P5600 Warrior IP-core. The CPU
73 resides Coherency Manager v2 with embedded 1MB L2-cache. It's
75 tags and way-select latencies of RAM access. This driver provides a
[all …]
|
| /linux-6.8/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | pamu.txt | 1 Freescale Peripheral Management Access Unit (PAMU) Device Tree Binding
5 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>
17 physically present PAMU controllers. For example, for
20 - interrupts : <prop-encoded-array>
22 interrupt, used for reporting access violations. The second
25 - #address-cells: <u32>
[all …]
|
| /linux-6.8/Documentation/ABI/testing/ |
| D | sysfs-class-scsi_host | 7 Storage Control Unit embeds up to two 4-port controllers in
8 a single PCI device. The controllers are enumerated in order
19 feature of HP Smart Array RAID controllers using the hpsa
22 of a logical drive, bypassing the controllers firmware RAID
34 Contact: linux-ide@vger.kernel.org
60 a) It does not use host-initiated slumber mode, but it does
61 allow device-initiated slumber
68 Contact: linux-ide@vger.kernel.org
79 protocol that is being used by the driver (for eg. LED, SAF-TE,
80 SES-2, SGPIO etc).
[all …]
|
| /linux-6.8/Documentation/admin-guide/media/ |
| D | remote-controller.rst | 1 .. SPDX-License-Identifier: GPL-2.0
12 Most analog and digital TV boards support remote controllers. Several of
22 the `v4l-utils <https://git.linuxtv.org/v4l-utils.git/>`_. It provides
23 two tools to handle remote controllers:
25 - ir-keytable: provides a way to query the remote controller, list the
26 protocols it supports, enable in-kernel support for IR decoder or
29 - ir-ctl: provide tools to handle remote controllers that support raw mode
32 Usually, the remote controller module is auto-loaded when the TV card is
34 ir-kbd-i2c module.
44 applications to access the remote via /dev/input/event<n> devices.
[all …]
|
| /linux-6.8/drivers/scsi/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0-only
29 If you want to use a SCSI hard disk, SCSI tape drive, SCSI CD-ROM or
70 comment "SCSI support type (disk, tape, CD-ROM)"
81 the IOMEGA ZIP drive, say Y and read the SCSI-HOWTO,
82 the Disk-HOWTO and the Multi-Disk-HOWTO, available from
84 CD-ROMs.
100 SCSI-HOWTO, available from
103 for SCSI CD-ROMs.
114 by SCSI, FireWire, USB or ATAPI, say Y and read the SCSI-HOWTO
115 and the CDROM-HOWTO at <http://www.tldp.org/docs.html#howto>.
[all …]
|
| /linux-6.8/drivers/mux/ |
| D | core.c | 1 // SPDX-License-Identifier: GPL-2.0
10 #define pr_fmt(fmt) "mux-core: " fmt
25 * The idle-as-is "state" is not an actual state that may be selected, it
32 * struct mux_state - Represents a mux controller state specific to a given
67 ida_simple_remove(&mux_ida, mux_chip->id); in mux_chip_release()
72 .name = "mux-chip",
77 * mux_chip_alloc() - Allocate a mux-chip.
79 * @controllers: The number of mux controllers to allocate for this chip.
82 * After allocating the mux-chip with the desired number of mux controllers
84 * the number of valid mux states in the mux_chip->mux[N].states members and
[all …]
|
| /linux-6.8/drivers/usb/host/ |
| D | Kconfig | 1 # SPDX-License-Identifier: GPL-2.0
11 The Cypress C67x00 (EZ-Host/EZ-OTG) chips are dual-role
12 host/peripheral/OTG USB controllers.
28 module will be called xhci-hcd.
90 tristate "xHCI support for Renesas R-Car SoCs"
96 found in Renesas R-Car ARM SoCs.
128 Enables support for XHCI, EHCI and OHCI host controllers
132 modules will be called ohci-platform.ko, ehci-brcm.ko and
133 xhci-plat-hcd.ko
135 Disabling this will keep the controllers and corresponding
[all …]
|