Home
last modified time | relevance | path

Searched +full:bus +full:- +full:err (Results 1 – 25 of 31) sorted by relevance

12

/Documentation/staging/
Drpmsg.rst7 This document describes the rpmsg bus and how to write rpmsg drivers.
17 flavor of real-time OS.
19 OMAP4, for example, has dual Cortex-A9, dual Cortex-M3 and a C64x+ DSP.
20 Typically, the dual cortex-A9 is running Linux in a SMP configuration,
25 hardware accelerators, and therefore are often used to offload CPU-intensive
28 These remote processors could also be used to control latency-sensitive
34 hardware accessible only by the remote processor, reserving kernel-controlled
37 Rpmsg is a virtio-based messaging bus that allows kernel drivers to communicate
45 physical memory, gpio banks, dma controllers, i2c bus, gptimers, mailbox
60 a unique rpmsg local address (a 32-bit integer). This way when inbound messages
[all …]
/Documentation/devicetree/bindings/spi/
Dspi-lantiq-ssc.txt4 - compatible: "lantiq,ase-spi", "lantiq,falcon-spi", "lantiq,xrx100-spi",
5 "intel,lgm-spi"
6 - #address-cells: see spi-bus.txt
7 - #size-cells: see spi-bus.txt
8 - reg: address and length of the spi master registers
9 - interrupts:
10 For compatible "intel,lgm-ssc" - the common interrupt number for
11 all of tx rx & err interrupts.
18 - clocks: spi clock phandle
19 - num-cs: see spi-bus.txt, set to 8 if unset
[all …]
/Documentation/devicetree/bindings/soc/qcom/
Dqcom,rpm.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
12 to vote for state of the system resources, such as clocks, regulators and bus
16 - Bjorn Andersson <andersson@kernel.org>
21 - qcom,rpm-apq8064
22 - qcom,rpm-msm8660
23 - qcom,rpm-msm8960
24 - qcom,rpm-ipq8064
25 - qcom,rpm-mdm9615
[all …]
/Documentation/sound/kernel-api/
Dwriting-an-alsa-driver.rst11 Architecture) <http://www.alsa-project.org/>`__ driver. The document
19 low-level driver implementation details. It only describes the standard
26 -------
56 --------------
60 sub-directories contain different modules and are dependent upon the
74 This directory and its sub-directories are for the ALSA sequencer. This
76 as snd-seq-midi, snd-seq-virmidi, etc. They are compiled only when
85 -----------------
88 to be exported to user-space, or included by several files in different
94 -----------------
[all …]
/Documentation/firmware-guide/acpi/
Denumeration.rst1 .. SPDX-License-Identifier: GPL-2.0
9 devices behind serial bus controllers.
13 that are accessed through memory-mapped registers.
15 In order to support this and re-use the existing drivers as much as
18 - Devices that have no bus connector resource are represented as
21 - Devices behind real busses where there is a connector resource
34 This means that when ACPI_HANDLE(dev) returns non-NULL the device was
36 device-specific configuration. There is an example of this below.
38 Platform bus support
42 connected to any physical bus we only need to implement a platform driver
[all …]
/Documentation/devicetree/bindings/iommu/
Dti,omap-iommu.txt4 - compatible : Should be one of,
5 "ti,omap2-iommu" for OMAP2/OMAP3 IOMMU instances
6 "ti,omap4-iommu" for OMAP4/OMAP5 IOMMU instances
7 "ti,dra7-dsp-iommu" for DRA7xx DSP IOMMU instances
8 "ti,dra7-iommu" for DRA7xx IOMMU instances
9 - ti,hwmods : Name of the hwmod associated with the IOMMU instance
10 - reg : Address space for the configuration registers
11 - interrupts : Interrupt specifier for the IOMMU instance
12 - #iommu-cells : Should be 0. OMAP IOMMUs are all "single-master" devices,
19 - ti,#tlb-entries : Number of entries in the translation look-aside buffer.
[all …]
/Documentation/driver-api/media/
Dv4l2-device.rst1 .. SPDX-License-Identifier: GPL-2.0
4 --------------------
16 dev->driver_data field is ``NULL``, it will be linked to
20 dev->driver_data manually to point to the driver-specific device structure
26 If :c:type:`v4l2_dev <v4l2_device>`\ ->name is empty then it will be set to a
30 :c:type:`v4l2_dev <v4l2_device>`\ ->name before calling
34 name and a driver-global atomic_t instance. This will generate names like
36 a dash: ``cx18-0``, ``cx18-1``, etc. This function returns the instance number.
44 You can also supply a ``notify()`` callback that can be called by sub-devices
46 sub-device. Any notifications a sub-device supports must be defined in a header
[all …]
Dv4l2-subdev.rst1 .. SPDX-License-Identifier: GPL-2.0
3 V4L2 sub-devices
4 ----------------
6 Many drivers need to communicate with sub-devices. These devices can do all
8 encoding or decoding. For webcams common sub-devices are sensors and camera
12 driver with a consistent interface to these sub-devices the
13 :c:type:`v4l2_subdev` struct (v4l2-subdev.h) was created.
15 Each sub-device driver must have a :c:type:`v4l2_subdev` struct. This struct
16 can be stand-alone for simple sub-devices or it might be embedded in a larger
18 low-level device struct (e.g. ``i2c_client``) that contains the device data as
[all …]
/Documentation/devicetree/bindings/pci/
Drockchip-dw-pcie.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/rockchip-dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Shawn Lin <shawn.lin@rock-chips.com>
11 - Simon Xue <xxm@rock-chips.com>
12 - Heiko Stuebner <heiko@sntech.de>
17 snps,dw-pcie.yaml.
20 - $ref: /schemas/pci/snps,dw-pcie.yaml#
21 - $ref: /schemas/pci/rockchip-dw-pcie-common.yaml#
[all …]
Drockchip-dw-pcie-ep.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/pci/rockchip-dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Niklas Cassel <cassel@kernel.org>
15 snps,dw-pcie-ep.yaml.
18 - $ref: /schemas/pci/snps,dw-pcie-ep.yaml#
19 - $ref: /schemas/pci/rockchip-dw-pcie-common.yaml#
24 - rockchip,rk3568-pcie-ep
25 - rockchip,rk3588-pcie-ep
[all …]
Dsnps,dw-pcie-ep.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie-ep.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Endpoint controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie-ep
23 - compatible
[all …]
Dsnps,dw-pcie.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
4 $id: http://devicetree.org/schemas/pci/snps,dw-pcie.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jingoo Han <jingoohan1@gmail.com>
11 - Gustavo Pimentel <gustavo.pimentel@synopsys.com>
16 # Please create a separate DT-schema for your DWC PCIe Root Port controller
17 # and make sure it's assigned with the vendor-specific compatible string.
21 const: snps,dw-pcie
23 - compatible
[all …]
/Documentation/hid/
Dhid-bpf.rst1 .. SPDX-License-Identifier: GPL-2.0
4 HID-BPF
17 When (and why) to use HID-BPF
20 There are several use cases when using HID-BPF is better
24 -----------------------
30 With HID-BPF, we can apply this filtering in the kernel directly so userspace
38 HID-BPF allows the userspace program to load the program itself, ensuring we
42 ---------------------------------
57 ------------------------------------------------
68 ------------------------------------------------------------------
[all …]
Duhid.rst2 UHID - User-space I/O driver support for HID subsystem
5 UHID allows user-space to implement HID transport drivers. Please see
6 hid-transport.rst for an introduction into HID transport drivers. This document
9 With UHID, a user-space transport driver can create kernel hid-devices for each
10 device connected to the user-space controlled bus. The UHID API defines the I/O
11 events provided from the kernel to user-space and vice versa.
13 There is an example user-space application in ./samples/uhid/uhid-example.c
16 ------------
18 UHID is accessed through a character misc-device. The minor number is allocated
25 write()'ing "struct uhid_event" objects. Non-blocking operations are supported
[all …]
/Documentation/devicetree/bindings/interrupt-controller/
Drenesas,rzg2l-irqc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/renesas,rzg2l-irqc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lad Prabhakar <prabhakar.mahadev-lad.rj@bp.renesas.com>
11 - Geert Uytterhoeven <geert+renesas@glider.be>
15 interrupts of NMI, IRQ, and GPIOINT and the interrupts of the built-in peripheral
17 - IRQ sense select for 8 external interrupts, mapped to 8 GIC SPI interrupts
18 - GPIO pins used as external interrupt input pins, mapped to 32 GIC SPI interrupts
19 - NMI edge select (NMI is not treated as NMI exception and supports fall edge and
[all …]
/Documentation/driver-api/
Duio-howto.rst5 :Author: Hans-Jürgen Koch Linux developer, Linutronix
6 :Date: 2006-12-11
12 ------------
18 -------
39 - The device has memory that can be mapped. The device can be
42 - The device usually generates interrupts.
44 - The device does not fit into one of the standard kernel subsystems.
47 ---------------
54 --------
64 - only one small kernel module to write and maintain.
[all …]
Dlibata.rst12 transports for ATA and ATAPI devices, and SCSI<->ATA translation for ATA
16 internals, and a couple sample ATA low-level drivers.
22 is defined for every low-level libata
23 hardware driver, and it controls how the low-level driver interfaces
26 FIS-based drivers will hook into the system with ``->qc_prep()`` and
27 ``->qc_issue()`` high-level hooks. Hardware which behaves in a manner
29 defining at a bare minimum the bus I/O addresses of the ATA shadow
33 ----------------------------------------------------------
35 Post-IDENTIFY device configuration
44 Typically used to apply device-specific fixups prior to issue of SET
[all …]
Dvfio.rst2 VFIO - "Virtual Function I/O" [1]_
7 allotted. This includes x86 hardware with AMD-Vi and Intel VT-d,
12 safe [2]_, non-privileged, userspace drivers.
19 bare-metal device drivers [3]_.
22 field, also benefit from low-overhead, direct device access from
23 userspace. Examples include network adapters (often non-TCP/IP based)
36 ---------------------------
42 as allowing a device read-write access to system memory imposes the
55 For instance, an individual device may be part of a larger multi-
59 could be anything from a multi-function PCI device with backdoors
[all …]
/Documentation/ABI/testing/
Dsysfs-platform-mellanox-bootctl1 What: /sys/bus/platform/devices/MLNXBF04:00/lifecycle_state
6 The Life-cycle state of the SoC, which could be one of the
12 GA Non-Secured Non-Secure chip and not able to change state
16 What: /sys/bus/platform/devices/MLNXBF04:00/post_reset_wdog
25 What: /sys/bus/platform/devices/MLNXBF04:00/reset_action
39 What: /sys/bus/platform/devices/MLNXBF04:00/second_reset_action
56 What: /sys/bus/platform/devices/MLNXBF04:00/secure_boot_fuse_state
72 What: /sys/bus/platform/devices/MLNXBF04:00/bootfifo
79 What: /sys/bus/platform/devices/MLNXBF04:00/rsh_log
85 "[INFO|WARN|ERR|ASSERT ]<msg>". Log level 'INFO' is used by
[all …]
/Documentation/driver-api/driver-model/
Ddevres.rst2 Devres - Managed Device Resource
20 --------
29 sufficient bugs in ->remove and ->probe failure path. Well, yes,
42 and having half broken failure path implementation in ->probe() which
48 ---------
75 dma_free_coherent(dev, this->size, this->vaddr, this->dma_handle);
91 dr->vaddr = vaddr;
100 freed whether initialization fails half-way or the device gets
111 return -ENOMEM;
113 d->ring = dmam_alloc_coherent(...);
[all …]
/Documentation/networking/
Dsfp-phylink.rst1 .. SPDX-License-Identifier: GPL-2.0
10 phylink is a mechanism to support hot-pluggable networking modules
11 directly connected to a MAC without needing to re-initialise the
12 adapter on hot-plug events.
14 phylink supports conventional phylib-based setups, fixed link setups
35 3. In-band mode
37 In-band mode is used with 802.3z, SGMII and similar interface modes,
38 and we are expecting to use and honor the in-band negotiation or
43 .. code-block:: none
47 phy-mode = "sgmii";
[all …]
Dcan.rst2 SocketCAN - Controller Area Network
20 .. _socketcan-motivation:
29 functionality. Usually, there is only a hardware-specific device
32 Queueing of frames and higher-level transport protocols like ISO-TP
34 character-device implementations support only one single process to
47 protocol family module and also vice-versa. Also, the protocol family
57 communicate using a specific transport protocol, e.g. ISO-TP, just
60 CAN-IDs, frames, etc.
62 Similar functionality visible from user-space could be provided by a
74 * **Abstraction:** In most existing character-device implementations, the
[all …]
Dtimestamping.rst1 .. SPDX-License-Identifier: GPL-2.0
43 -------------------------------------------------------------
59 -------------------------------------------------------------------
72 ----------------------------------------------------------------------
77 err = setsockopt(fd, SOL_SOCKET, SO_TIMESTAMPING, &val, sizeof(val));
138 over-report measurement, because the timestamp is generated when all
181 is derived from a per-socket u32 counter (that wraps). For datagram
208 a timestamp with counter N-1. SOF_TIMESTAMPING_OPT_ID_TCP
258 received the packet and its length at layer 2. A valid (non-zero)
283 ignore the unexpected non-zero value. But it makes behavior subtly
[all …]
/Documentation/netlink/specs/
Ddevlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 -
12 name: sb-pool-type
14 -
16 -
18 -
20 name: port-type
22 -
24 -
[all …]
/Documentation/devicetree/
Dusage-model.rst1 .. SPDX-License-Identifier: GPL-2.0
44 ----------
56 In 2005, when PowerPC Linux began a major cleanup and to merge 32-bit
57 and 64-bit support, the decision was made to require DT support on all
61 blob without requiring a real Open Firmware implementation. U-Boot,
66 existing non-DT aware firmware.
74 -------------
79 -------------------
88 per-machine hard coded selections.
101 ---------------------------
[all …]

12