Home
last modified time | relevance | path

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

12345678910>>...27

/Documentation/netlink/specs/
Ddevlink.yaml1 # SPDX-License-Identifier: ((GPL-2.0 WITH Linux-syscall-note) OR BSD-3-Clause)
5 protocol: genetlink-legacy
10 -
11 type: enum
12 name: sb-pool-type
14 -
16 -
18 -
19 type: enum
20 name: port-type
[all …]
/Documentation/devicetree/bindings/dma/
Dadi,axi-dmac.txt1 Analog Devices AXI-DMAC DMA controller
4 - compatible: Must be "adi,axi-dmac-1.00.a".
5 - reg: Specification for the controllers memory mapped register map.
6 - interrupts: Specification for the controllers interrupt.
7 - clocks: Phandle and specifier to the controllers AXI interface clock
8 - #dma-cells: Must be 1.
10 Required sub-nodes:
11 - adi,channels: This sub-node must contain a sub-node for each DMA channel. For
12 the channel sub-nodes the following bindings apply. They must match the
15 Required properties for adi,channels sub-node:
[all …]
Darm-pl08x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/dma/arm-pl08x.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Vinod Koul <vkoul@kernel.org>
13 - $ref: /schemas/arm/primecell.yaml#
14 - $ref: dma-controller.yaml#
22 - arm,pl080
23 - arm,pl081
25 - compatible
[all …]
/Documentation/driver-api/driver-model/
Dbus.rst2 Bus Types
9 int bus_register(struct bus_type * bus);
15 Each bus type in the kernel (PCI, USB, etc) should declare one static
16 object of this type. They must initialize the name field, and may
32 When a bus driver is initialized, it calls bus_register. This
33 initializes the rest of the fields in the bus object and inserts it
34 into a global list of bus types. Once the bus object is registered,
35 the fields in it are usable by the bus driver.
45 them are inherently bus-specific. Drivers typically declare an array
46 of device IDs of devices they support that reside in a bus-specific
[all …]
Dporting.rst12 Please refer to `Documentation/driver-api/driver-model/*.rst` for definitions of
16 at the bus driver layer. This was intentional, to minimize the
18 of bus drivers.
21 be embedded in larger, bus-specific objects. Fields in these generic
22 objects can replace fields in the bus-specific objects.
28 # mount -t sysfs sysfs /sys
36 Step 1: Registering the bus driver.
39 - Define a struct bus_type for the bus driver::
46 - Register the bus type.
48 This should be done in the initialization function for the bus type,
[all …]
Dbinding.rst6 driver that can control it. Bus drivers have typically handled this
7 because there have been bus-specific structures to represent the
12 Bus chapter
15 The bus type structure contains a list of all devices that are on that bus
16 type in the system. When device_register is called for a device, it is
17 inserted into the end of this list. The bus object also contains a
18 list of all drivers of that bus type. When driver_register is called
26 When a new device is added, the bus's list of drivers is iterated over
29 supports. The format and semantics for comparing IDs is bus-specific.
31 algorithm, it is up to the bus driver to provide a callback to compare
[all …]
/Documentation/ABI/testing/
Dsysfs-bus-siox1 What: /sys/bus/siox/devices/siox-X/active
3 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
5 On reading represents the current state of the bus. If it
6 contains a "0" the bus is stopped and connected devices are
8 When the file contains a "1" the bus is operated and periodically
9 does a push-pull cycle to write and read data from the
12 When writing a "0" or "1" the bus moves to the described state.
14 What: /sys/bus/siox/devices/siox-X/device_add
16 Contact: Thorsten Scherer <t.scherer@eckelmann.de>, Uwe Kleine-König <u.kleine-koenig@pengutronix.d…
18 Write-only file. Write
[all …]
Dsysfs-driver-typec-displayport1 What: /sys/bus/typec/devices/.../displayport/configuration
20 USB Type-C Standard. Functionally it equals to the situation
22 Documentation/ABI/testing/sysfs-bus-typec, and use file
23 /sys/bus/typec/devices/.../active).
25 What: /sys/bus/typec/devices/.../displayport/pin_assignment
29 VESA DisplayPort Alt Mode on USB Type-C Standard defines six
30 different pin assignments for USB Type-C connector that are
44 Note. As of VESA DisplayPort Alt Mode on USB Type-C Standard
51 What: /sys/bus/typec/devices/.../displayport/hpd
55 VESA DisplayPort Alt Mode on USB Type-C Standard defines how
[all …]
Dsysfs-bus-coresight-devices-tpdm1 What: /sys/bus/coresight/devices/<tpdm-name>/integration_test
11 Accepts only one of the 2 values - 1 or 2.
15 What: /sys/bus/coresight/devices/<tpdm-name>/reset_dataset
22 Accepts only one value - 1.
25 What: /sys/bus/coresight/devices/<tpdm-name>/dsb_trig_type
30 (RW) Set/Get the trigger type of the DSB for tpdm.
32 Accepts only one of the 2 values - 0 or 1.
33 0 : Set the DSB trigger type to false
34 1 : Set the DSB trigger type to true
36 What: /sys/bus/coresight/devices/<tpdm-name>/dsb_trig_ts
[all …]
Ddebugfs-driver-dcc27 What: /sys/kernel/debug/dcc/.../[list-number]/config
33 software triggers. The input addresses type
35 write, read-write, and loop type. The lists need to
39 each type is as follows:
45 echo R <addr> <n> <bus> >/sys/kernel/debug/dcc/../[list-number]/config
57 <bus type>
58 The bus type, which can be either 'apb' or 'ahb'.
65 echo W <addr> <n> <bus type> > /sys/kernel/debug/dcc/../[list-number]/config
75 <bus type>
76 The bus type, which can be either 'apb' or 'ahb'.
[all …]
Dsysfs-firmware-sgi_uv8 Under that directory are a number of read-only attributes::
17 The archtype entry contains the UV architecture type that
18 is used to select arch-dependent addresses and features.
22 The hub_type entry is used to select the type of hub which is
59 Each hub object directory contains a number of read-only attributes::
69 If a cnode value is not applicable, the value returned will be -1.
86 If a nasid value is not applicable, the value returned will be -1.
99 Each port object directory contains a number of read-only attributes::
107 the value returned will be -1.
112 returned will be -1.
[all …]
Dsysfs-bus-css1 What: /sys/bus/css/devices/.../type
3 Contact: linux-s390@vger.kernel.org
4 Description: Contains the subchannel type, as reported by the hardware.
7 What: /sys/bus/css/devices/.../modalias
9 Contact: linux-s390@vger.kernel.org
11 It is of the format css:t<type> and present for all
14 What: /sys/bus/css/drivers/io_subchannel/.../chpids
16 Contact: linux-s390@vger.kernel.org
21 Note: This is an I/O-subchannel specific attribute.
22 Users: s390-tools, HAL
[all …]
Dsysfs-bus-usb1 What: /sys/bus/usb/devices/<INTERFACE>/authorized
9 by writing INTERFACE to /sys/bus/usb/drivers_probe
10 This allows to avoid side-effects with drivers
15 What: /sys/bus/usb/devices/usbX/interface_authorized_default
22 What: /sys/bus/usb/device/.../authorized
28 drivers, non-authorized one are not. By default, wired
31 What: /sys/bus/usb/drivers/.../new_id
33 Contact: linux-usb@vger.kernel.org
48 # echo "8086 10f5" > /sys/bus/usb/drivers/foo/new_id
53 # echo "0458 7045 0 0458 704c" > /sys/bus/usb/drivers/foo/new_id
[all …]
Dsysfs-driver-hid-prodikeys1 What: /sys/bus/hid/drivers/prodikeys/.../channel
7 that the pc-midi keyboard will output.midi data.
9 Type: Read/write
10 What: /sys/bus/hid/drivers/prodikeys/.../sustain
16 note held by the pc-midi driver.
19 Type: Read/write
20 What: /sys/bus/hid/drivers/prodikeys/.../octave
25 Controls the octave shift modifier in the pc-midi driver.
28 Range: -2..2 (minus 2 to plus 2)
29 Type: Read/Write
Dsysfs-driver-input-exc30001 What: /sys/bus/i2c/devices/xxx/fw_version
3 Contact: linux-input@vger.kernel.org
10 What: /sys/bus/i2c/devices/xxx/model
12 Contact: linux-input@vger.kernel.org
19 What: /sys/bus/i2c/devices/xxx/type
21 Contact: linux-input@vger.kernel.org
22 Description: Reports the type identification provided by the touchscreen, for example "PCAP82H80 Se…
/Documentation/devicetree/bindings/media/
Dmicrochip,xisc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
4 ---
6 $schema: http://devicetree.org/meta-schemas/core.yaml#
11 - Eugen Hristev <eugen.hristev@microchip.com>
18 The source can be either a demuxer from a CSI2 type of bus, or a simple direct bridge to a
25 const: microchip,sama7g5-isc
36 clock-names:
38 - const: hclock
40 '#clock-cells':
43 clock-output-names:
[all …]
Dst,stm32-dcmi.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/media/st,stm32-dcmi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hugues Fruchet <hugues.fruchet@foss.st.com>
14 const: st,stm32-dcmi
25 clock-names:
27 - const: mclk
32 dma-names:
34 - const: tx
[all …]
/Documentation/devicetree/bindings/bus/
Dqcom,ssbi.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/bus/qcom,ssbi.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Qualcomm Single-wire Serial Bus Interface (SSBI)
10 Some Qualcomm MSM devices contain a point-to-point serial bus used to
15 - Andy Gross <agross@kernel.org>
16 - Bjorn Andersson <andersson@kernel.org>
25 qcom,controller-type:
27 Indicates the SSBI bus variant the controller should use to talk
[all …]
/Documentation/devicetree/bindings/media/i2c/
Dovti,ov772x.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Jacopo Mondi <jacopo@jmondi.org>
20 - ovti,ov7720
21 - ovti,ov7725
29 reset-gpios:
34 powerdown-gpios:
40 $ref: /schemas/graph.yaml#/$defs/port-base
46 $ref: /schemas/media/video-interfaces.yaml#
[all …]
Dovti,ov5642.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Fabio Estevam <festevam@gmail.com>
13 - $ref: /schemas/media/video-interface-devices.yaml#
25 AVDD-supply:
28 DVDD-supply:
31 DOVDD-supply:
34 powerdown-gpios:
38 reset-gpios:
[all …]
/Documentation/driver-api/
Di2c.rst5 the "Inter-IC" bus, a simple bus protocol which is widely used where low
7 some vendors use another name (such as "Two-Wire Interface", TWI) for
8 the same bus. I2C only needs two signals (SCL for clock, SDA for data),
10 I2C devices use seven bit addresses, and bus speeds of up to 400 kHz;
12 I2C is a multi-master bus; open drain signaling is used to arbitrate
16 The Linux I2C programming interfaces support the master side of bus
21 :c:type:`struct i2c_adapter <i2c_adapter>` representing each
22 I2C bus segment it manages. On each I2C bus segment will be I2C devices
23 represented by a :c:type:`struct i2c_client <i2c_client>`.
24 Those devices will be bound to a :c:type:`struct i2c_driver
[all …]
/Documentation/driver-api/iio/
Dcore.rst8 :file:`drivers/iio/industrialio-*`
11 ----------------------
13 * struct iio_dev - industrial I/O device
14 * iio_device_alloc() - allocate an :c:type:`iio_dev` from a driver
15 * iio_device_free() - free an :c:type:`iio_dev` from a driver
16 * iio_device_register() - register a device with the IIO subsystem
17 * iio_device_unregister() - unregister a device from the IIO
27 1. :file:`/sys/bus/iio/devices/iio:device{X}/`, this represents a hardware sensor
54 index X, attributes can be found under /sys/bus/iio/devices/iio:deviceX/
63 :file:`Documentation/ABI/testing/sysfs-bus-iio` file in the Linux kernel
[all …]
/Documentation/devicetree/bindings/memory-controllers/
Dintel,ixp4xx-expansion-bus-controller.yaml1 # 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#
7 title: Intel IXP4xx Expansion Bus Controller
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:
[all …]
/Documentation/devicetree/bindings/net/
Dmdio.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: MDIO Bus Common Properties
10 - Andrew Lunn <andrew@lunn.ch>
11 - Florian Fainelli <f.fainelli@gmail.com>
12 - Heiner Kallweit <hkallweit1@gmail.com>
15 These are generic properties that can apply to any MDIO bus. Any
16 MDIO bus must have a list of child nodes, one per device on the
17 bus. These should follow the generic ethernet-phy.yaml document, or
[all …]
/Documentation/driver-api/usb/
Dtypec_bus.rst2 API for USB Type-C Alternate Mode drivers
6 ------------
9 Messages (VDM) as defined in USB Type-C and USB Power Delivery Specifications.
13 USB Type-C bus allows binding a driver to the discovered partner alternate
16 :ref:`USB Type-C Connector Class <typec>` provides a device for every alternate
36 ------
43 space (See Documentation/ABI/testing/sysfs-class-typec). Port drivers should not
46 ``->vdm`` is the most important callback in the operation callbacks vector. It
53 needs to notify the bus using :c:func:`typec_altmode_notify()`. The driver
55 parameter. The bus driver will then configure the mux behind the connector using
[all …]

12345678910>>...27