Searched +full:device +full:- +full:addr (Results 1 – 25 of 120) sorted by relevance
12345
| /Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 1 MPC5200 Device Tree Bindings
2 ----------------------------
4 (c) 2006-2009 Secret Lab Technologies Ltd
8 ------------------
9 For mpc5200 on-chip devices, the format for each compatible value is
10 <chip>-<device>[-<mode>]. The OS should be able to match a device driver
11 to the device based solely on the compatible value. If two drivers
21 "fsl,mpc5200-<device>".
27 To express this information as completely as possible, 5200B device trees
29 compatible = "fsl,mpc5200b-<device>","fsl,mpc5200-<device>";
[all …]
|
| /Documentation/i2c/ |
| D | smbus-protocol.rst | 14 If you write a driver for some I2C device, please try to use the SMBus
15 commands if at all possible (if the device uses only that subset of the
16 I2C protocol). This makes it possible to use the device driver on both
28 transaction function, a device driver should always check (just once) for
44 Addr (7 bits) I2C 7 bit address. Note that this can be expanded to
47 the device.
52 [..] Data sent by I2C device, as opposed to data sent by the host
60 This sends a single bit to the device, at the place of the Rd/Wr bit::
62 S Addr Rd/Wr [A] P
72 This reads a single byte from a device, without specifying a device
[all …]
|
| D | i2c-protocol.rst | 16 Addr (7 bits) I2C 7 bit address. Note that this can be expanded to
20 [..] Data sent by I2C device, as opposed to data sent by the
30 S Addr Wr [A] Data [A] Data [A] ... [A] Data [A] P
38 S Addr Rd [A] [Data] A [Data] A ... A [Data] NA P
50 S Addr Rd [A] [Data] NA S Addr Wr [A] Data [A] P
58 are usually only needed to work around device issues:
64 These messages may still fail to SCL lo->hi timeout.
70 In a combined transaction, no 'S Addr Wr/Rd [A]' is generated at some
74 S Addr Rd [A] [Data] NA Data [A] P
77 we do not generate Addr, but we do generate the start condition S.
[all …]
|
| /Documentation/devicetree/bindings/sound/ |
| D | ssm4567.txt | 3 This device supports I2C only.
6 - compatible : Must be "adi,ssm4567"
7 - reg : the I2C address of the device. This will either be 0x34 (LR_SEL/ADDR connected to AGND),
8 0x35 (LR_SEL/ADDR connected to IOVDD) or 0x36 (LR_SEL/ADDR open).
|
| D | adi,ssm2518.yaml | 1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Lars-Peter Clausen <lars@metafoo.de>
13 - $ref: dai-common.yaml#
22 I2C address of the device. This will either be 0x34 (ADDR pin low)
23 or 0x35 (ADDR pin high)
32 - compatible
33 - reg
38 - |
[all …]
|
| D | tas2552.txt | 1 Texas Instruments - tas2552 Codec module
6 - compatible - One of:
7 "ti,tas2552" - TAS2552
8 - reg - I2C slave address: it can be 0x40 if ADDR pin is 0
9 or 0x41 if ADDR pin is 1.
10 - supply-*: Required supply regulators are:
16 - enable-gpio - gpio pin to enable/disable the device
21 For system integration the dt-bindings/sound/tas2552.h header file provides
29 vbat-supply = <®_vbat>;
30 iovdd-supply = <®_iovdd>;
[all …]
|
| /Documentation/devicetree/bindings/leds/ |
| D | leds-netxbig.txt | 5 - compatible: "lacie,netxbig-leds".
6 - gpio-ext: Phandle for the gpio-ext bus.
9 - timers: Timer array. Each timer entry is represented by three integers:
10 Mode (gpio-ext bus), delay_on and delay_off.
12 Each LED is represented as a sub-node of the netxbig-leds device.
14 Required sub-node properties:
15 - mode-addr: Mode register address on gpio-ext bus.
16 - mode-val: Mode to value mapping. Each entry is represented by two integers:
17 A mode and the corresponding value on the gpio-ext bus.
18 - bright-addr: Brightness register address on gpio-ext bus.
[all …]
|
| /Documentation/devicetree/bindings/nios2/ |
| D | nios2.txt | 3 This binding specifies what properties available in the device tree
6 Users can use sopc2dts tool for generating device tree sources (dts) from a
11 - compatible: Compatible property value should be "altr,nios2-1.0".
12 - reg: Contains CPU index.
13 - interrupt-controller: Specifies that the node is an interrupt controller
14 - #interrupt-cells: Specifies the number of cells needed to encode an
16 - clock-frequency: Contains the clock frequency for CPU, in Hz.
17 - dcache-line-size: Contains data cache line size.
18 - icache-line-size: Contains instruction line size.
19 - dcache-size: Contains data cache size.
[all …]
|
| /Documentation/networking/ |
| D | mctp.rst | 1 .. SPDX-License-Identifier: GPL-2.0
11 The core code provides a socket-based interface to send and receive MCTP
22 device. This is represented as a ``struct netdevice``.
24 A network defines a unique address space for MCTP endpoints by endpoint-ID
25 (described by DSP0236, section 3.2.31). A network has a user-visible identifier
39 --------------------
41 MCTP uses ``AF_MCTP`` / ``PF_MCTP`` for the address- and protocol- families.
42 Since MCTP is message-based, only ``SOCK_DGRAM`` sockets are supported.
44 .. code-block:: C
51 specified with a ``sockaddr`` type, with a single-byte endpoint address:
[all …]
|
| D | phonet.rst | 1 .. SPDX-License-Identifier: GPL-2.0
9 ------------
14 device attached to the modem. The modem takes care of routing.
17 depending on the device, such as:
19 - USB with the CDC Phonet interface,
20 - infrared,
21 - Bluetooth,
22 - an RS232 serial port (with a dedicated "FBUS" line discipline),
23 - the SSI bus with some TI OMAP processors.
27 --------------
[all …]
|
| D | xsk-tx-metadata.rst | 1 .. SPDX-License-Identifier: GPL-2.0
8 via :doc:`af_xdp`. Refer to :doc:`xdp-rx-metadata` on how to access similar
26 ``xdp_desc->addr`` in the umem frame. Within a frame, the metadata
31 +-----------------+---------+----------------------------+
33 +-----------------+---------+----------------------------+
36 xdp_desc->addr
40 use ``xdp_desc->addr - tx_metadata_len`` to locate
47 - ``XDP_TXMD_FLAGS_TIMESTAMP``: requests the device to put transmission
49 - ``XDP_TXMD_FLAGS_CHECKSUM``: requests the device to calculate L4
52 device should store the computed checksum.
[all …]
|
| /Documentation/virt/kvm/devices/ |
| D | xive.rst | 1 .. SPDX-License-Identifier: GPL-2.0
7 Device types supported:
8 - KVM_DEV_TYPE_XIVE POWER9 XIVE Interrupt Controller generation 1
10 This device acts as a VM interrupt controller. It provides the KVM
14 Only one XIVE instance may be instantiated. A guest XIVE device
19 * Device Mappings
21 The KVM device exposes different MMIO ranges of the XIVE HW which
32 - Interrupt Pending Buffer (IPB)
33 - Current Processor Priority (CPPR)
34 - Notification Source Register (NSR)
[all …]
|
| D | vfio.rst | 1 .. SPDX-License-Identifier: GPL-2.0
4 VFIO virtual device
7 Device types supported:
9 - KVM_DEV_TYPE_VFIO
11 Only one VFIO instance may be created per VM. The created device
12 tracks VFIO files (group or device) in use by the VM and features
24 KVM_DEV_VFIO_FILE_ADD: Add a VFIO file (group/device) to VFIO-KVM device
27 kvm_device_attr.addr points to an int32_t file descriptor for the
30 KVM_DEV_VFIO_FILE_DEL: Remove a VFIO file (group/device) from VFIO-KVM
31 device tracking
[all …]
|
| /Documentation/userspace-api/media/v4l/ |
| D | vidioc-dbg-g-chip-info.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DBG_G_CHIP_INFO - Identify the chips on a TV card
42 contact the linux-media mailing list
50 ``match.addr`` or ``match.name`` fields of a struct
56 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr``
58 chips by starting at zero and incrementing ``match.addr`` by one until
61 the PCI or USB bus. Non-zero numbers identify specific parts of the
64 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr``
65 selects the nth sub-device. This allows you to enumerate over all
66 sub-devices.
[all …]
|
| D | vidioc-dbg-g-register.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
13 VIDIOC_DBG_G_REGISTER - VIDIOC_DBG_S_REGISTER - Read or write hardware registers
55 ``match.type`` and ``match.addr`` or ``match.name`` fields select a chip
60 ``match.addr`` or ``match.name`` and ``reg`` fields, and call
65 When ``match.type`` is ``V4L2_CHIP_MATCH_BRIDGE``, ``match.addr``
66 selects the nth non-sub-device chip on the TV card. The number zero
71 When ``match.type`` is ``V4L2_CHIP_MATCH_SUBDEV``, ``match.addr``
72 selects the nth sub-device.
83 We recommended the v4l2-dbg utility over calling these ioctls directly.
84 It is available from the LinuxTV v4l-dvb repository; see
[all …]
|
| /Documentation/devicetree/bindings/leds/backlight/ |
| D | lp855x-backlight.yaml | 1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/leds/backlight/lp855x-backlight.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Artur Weber <aweber.kernel@gmail.com>
15 - ti,lp8550
16 - ti,lp8551
17 - ti,lp8552
18 - ti,lp8553
19 - ti,lp8555
[all …]
|
| /Documentation/devicetree/bindings/mtd/ |
| D | fsl-upm-nand.txt | 4 - compatible : "fsl,upm-nand".
5 - reg : should specify localbus chip select and size used for the chip.
6 - fsl,upm-addr-offset : UPM pattern offset for the address latch.
7 - fsl,upm-cmd-offset : UPM pattern offset for the command latch.
10 - fsl,upm-addr-line-cs-offsets : address offsets for multi-chip support.
12 - gpios : may specify optional GPIOs connected to the Ready-Not-Busy pins
13 (R/B#). For multi-chip devices, "n" GPIO definitions are required
17 - fsl,upm-wait-flags : add chip-dependent short delays after running the
20 - chip-delay : chip dependent delay for transferring data from array to
24 Each flash chip described may optionally contain additional sub-nodes
[all …]
|
| D | atmel-nand.txt | 4 Documentation/devicetree/bindings/memory-controllers/atmel,ebi.txt).
11 - compatible: should be one of the following
12 "atmel,at91rm9200-nand-controller"
13 "atmel,at91sam9260-nand-controller"
14 "atmel,at91sam9261-nand-controller"
15 "atmel,at91sam9g45-nand-controller"
16 "atmel,sama5d3-nand-controller"
17 "microchip,sam9x60-nand-controller"
18 - ranges: empty ranges property to forward EBI ranges definitions.
19 - #address-cells: should be set to 2.
[all …]
|
| /Documentation/userspace-api/media/cec/ |
| D | cec-ioc-adap-g-log-addrs.rst | 1 .. SPDX-License-Identifier: GFDL-1.1-no-invariants-or-later
15 CEC_ADAP_G_LOG_ADDRS, CEC_ADAP_S_LOG_ADDRS - Get or set the logical addresses
59 addresses have been claimed. If the file descriptor is in non-blocking mode then it will
62 A :ref:`CEC_EVENT_STATE_CHANGE <CEC-EVENT-STATE-CHANGE>` event is sent when the
74 .. flat-table:: struct cec_log_addrs
75 :header-rows: 0
76 :stub-columns: 0
79 * - __u8
80 - ``log_addr[CEC_MAX_LOG_ADDRS]``
81 - The actual logical addresses that were claimed. This is set by the
[all …]
|
| /Documentation/ABI/testing/ |
| D | sysfs-driver-hid | 1 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
2 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/report_descriptor
3 What: /sys/class/hidraw/hidraw<num>/device/report_descriptor
7 Description: When read, this file returns the device's raw binary HID
12 What: /sys/bus/usb/devices/<busnum>-<devnum>:<config num>.<interface num>/<hid-bus>:<vendor-id>:<p…
13 What: /sys/class/bluetooth/hci<addr>/<hid-bus>:<vendor-id>:<product-id>.<num>/country
14 What: /sys/class/hidraw/hidraw<num>/device/country
19 of the device's HID country code (e.g. 21 for US).
|
| /Documentation/driver-api/ |
| D | ntb.rst | 5 NTB (Non-Transparent Bridge) is a type of PCI-Express bridge chip that connects
6 the separate memory systems of two or more computers to the same PCI-Express
9 scratchpad and message registers. Scratchpad registers are read-and-writable
10 registers that are accessible from either side of the device, so that peers can
32 registration uses the Linux Device framework, so it should feel familiar to
36 ----------------------------------------
39 systems. So the NTB device features like Scratchpad/Message registers are
50 | dma-mapped |-ntb_mw_set_trans(addr) |
52 | (addr) |<======| MW xlat addr |<====| MW base addr |<== memory-mapped IO
53 |------------| |--------------| | |--------------|
[all …]
|
| /Documentation/devicetree/bindings/cpu/ |
| D | cpu-topology.txt | 6 1 - Introduction
12 - socket
13 - cluster
14 - core
15 - thread
18 symmetric multi-threading (SMT) is supported or not.
26 corresponding to the system hierarchy; syntactically they are defined as device
29 Currently, only ARM/RISC-V intend to use this cpu topology binding but it may be
39 2 - cpu-map node
42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
[all …]
|
| /Documentation/userspace-api/ |
| D | vduse.rst | 2 VDUSE - "vDPA Device in Userspace"
5 vDPA (virtio data path acceleration) device is a device that uses a
9 possible to implement software-emulated vDPA devices in userspace. And
10 to make the device emulation more secure, the emulated vDPA device's
14 Note that only virtio block device is supported by VDUSE framework now,
16 the data path is run by an unprivileged user. The support for other device
17 types can be added after the security issue of corresponding device driver
21 ----------------------------
49 .. code-block:: c
59 return -ENOMEM;
[all …]
|
| /Documentation/devicetree/bindings/iio/adc/ |
| D | microchip,mcp3911.yaml | 1 # SPDX-License-Identifier: GPL-2.0 OR BSD-2-Clause
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Marcus Folkesson <marcus.folkesson@gmail.com>
12 - Kent Gustavsson <nedo80@gmail.com>
15 Bindings for the Microchip MCP3911 Dual channel ADC device. Datasheet can be
21 - microchip,mcp3910
22 - microchip,mcp3911
23 - microchip,mcp3912
24 - microchip,mcp3913
[all …]
|
| /Documentation/devicetree/bindings/iio/light/ |
| D | veml6030.yaml | 1 # SPDX-License-Identifier: GPL-2.0+
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rishi Gupta <gupt21@gmail.com>
28 - vishay,veml6030
32 I2C address of the device.
34 - 0x10 # ADDR pin pulled down
35 - 0x48 # ADDR pin pulled up
40 Refer to interrupt-controller/interrupts.txt for generic
45 - compatible
[all …]
|
12345