Home
last modified time | relevance | path

Searched full:bus (Results 1 – 25 of 1506) sorted by relevance

12345678910>>...61

/Documentation/ABI/testing/
Dsysfs-bus-i3c1 What: /sys/bus/i3c/devices/i3c-<bus-id>
5 An I3C bus. This directory will contain one sub-directory per
6 I3C device present on the bus.
8 What: /sys/bus/i3c/devices/i3c-<bus-id>/current_master
12 Expose the master that owns the bus (<bus-id>-<master-pid>) at
13 the time this file is read. Note that bus ownership can change
17 What: /sys/bus/i3c/devices/i3c-<bus-id>/mode
21 I3C bus mode. Can be "pure", "mixed-fast" or "mixed-slow". See
25 What: /sys/bus/i3c/devices/i3c-<bus-id>/i3c_scl_frequency
32 What: /sys/bus/i3c/devices/i3c-<bus-id>/i2c_scl_frequency
[all …]
Dsysfs-bus-soundwire-slave1 What: /sys/bus/soundwire/devices/sdw:.../status
2 /sys/bus/soundwire/devices/sdw:.../device_number
16 physically present on the bus, and conversely devices
19 What: /sys/bus/soundwire/devices/sdw:.../dev-properties/mipi_revision
20 /sys/bus/soundwire/devices/sdw:.../dev-properties/wake_capable
21 /sys/bus/soundwire/devices/sdw:.../dev-properties/test_mode_capable
22 /sys/bus/soundwire/devices/sdw:.../dev-properties/clk_stop_mode1
23 /sys/bus/soundwire/devices/sdw:.../dev-properties/simple_clk_stop_capable
24 /sys/bus/soundwire/devices/sdw:.../dev-properties/clk_stop_timeout
25 /sys/bus/soundwire/devices/sdw:.../dev-properties/ch_prep_timeout
[all …]
Dsysfs-bus-mdio1 What: /sys/bus/mdio_bus/devices/.../statistics/
7 MDIO bus address statistics.
9 What: /sys/bus/mdio_bus/devices/.../statistics/transfers
14 Total number of transfers for this MDIO bus.
16 What: /sys/bus/mdio_bus/devices/.../statistics/errors
21 Total number of transfer errors for this MDIO bus.
23 What: /sys/bus/mdio_bus/devices/.../statistics/writes
28 Total number of write transactions for this MDIO bus.
30 What: /sys/bus/mdio_bus/devices/.../statistics/reads
35 Total number of read transactions for this MDIO bus.
[all …]
Dsysfs-platform-chipidea-usb-otg1 What: /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_req
6 Set a_bus_req(A-device bus request) input to be 1 if
7 the application running on the A-device wants to use the bus,
9 the bus(or wants to work as peripheral). a_bus_req can also
11 from the B-device, the A-device should decide to resume the bus.
16 is using the bus as host role, otherwise 0.
18 What: /sys/bus/platform/devices/ci_hdrc.0/inputs/a_bus_drop
23 The a_bus_drop(A-device bus drop) input is 1 when the
25 the bus, and is 0 otherwise, When a_bus_drop is 1, then
30 Reading: returns 1 if the bus is off(vbus is turned off) by
[all …]
Dsysfs-bus-soundwire-master1 What: /sys/bus/soundwire/devices/sdw-master-N/revision
2 /sys/bus/soundwire/devices/sdw-master-N/clk_stop_modes
3 /sys/bus/soundwire/devices/sdw-master-N/clk_freq
4 /sys/bus/soundwire/devices/sdw-master-N/clk_gears
5 /sys/bus/soundwire/devices/sdw-master-N/default_col
6 /sys/bus/soundwire/devices/sdw-master-N/default_frame_rate
7 /sys/bus/soundwire/devices/sdw-master-N/default_row
8 /sys/bus/soundwire/devices/sdw-master-N/dynamic_shape
9 /sys/bus/soundwire/devices/sdw-master-N/err_threshold
10 /sys/bus/soundwire/devices/sdw-master-N/max_clk_freq
[all …]
Dsysfs-bus-coresight-devices-cti1 What: /sys/bus/coresight/devices/<cti-name>/enable
7 What: /sys/bus/coresight/devices/<cti-name>/powered
13 What: /sys/bus/coresight/devices/<cti-name>/ctmid
19 What: /sys/bus/coresight/devices/<cti-name>/nr_trigger_cons
25 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/name
31 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_signals
37 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/in_types
44 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_signals
50 What: /sys/bus/coresight/devices/<cti-name>/triggers<N>/out_types
57 What: /sys/bus/coresight/devices/<cti-name>/regs/inout_sel
[all …]
Dsysfs-bus-coresight-devices-etm4x1 What: /sys/bus/coresight/devices/etm<N>/enable_source
11 What: /sys/bus/coresight/devices/etm<N>/cpu
17 What: /sys/bus/coresight/devices/etm<N>/nr_pe_cmp
24 What: /sys/bus/coresight/devices/etm<N>/nr_addr_cmp
31 What: /sys/bus/coresight/devices/etm<N>/nr_cntr
38 What: /sys/bus/coresight/devices/etm<N>/nr_ext_inp
44 What: /sys/bus/coresight/devices/etm<N>/numcidc
51 What: /sys/bus/coresight/devices/etm<N>/numvmidc
58 What: /sys/bus/coresight/devices/etm<N>/nrseqstate
65 What: /sys/bus/coresight/devices/etm<N>/nr_resource
[all …]
Dsysfs-driver-wacom1 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed
6 The /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/speed file
12 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/led
23 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status0_luminance
33 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status1_luminance
42 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led0_select
52 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/status_led1_select
61 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/buttons_luminance
68 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_led/button<n>_rawimg
87 What: /sys/bus/hid/devices/<bus>:<vid>:<pid>.<n>/wacom_remote/unpair_remote
[all …]
Dsysfs-bus-rbd1 What: /sys/bus/rbd/add
12 $ echo "192.168.0.1 name=admin rbd foo" > /sys/bus/rbd/add
19 What: /sys/bus/rbd/remove
30 $ echo 2 > /sys/bus/rbd/remove
38 What: /sys/bus/rbd/add_single_major
46 Usage is the same as for /sys/bus/rbd/add. If present, this
48 /sys/bus/rbd/add if /sys/bus/rbd/add_single_major is available
52 What: /sys/bus/rbd/remove_single_major
60 Usage is the same as for /sys/bus/rbd/remove. If present, this
62 /sys/bus/rbd/remove if /sys/bus/rbd/remove_single_major is
[all …]
Dsysfs-bus-most1 What: /sys/bus/most/devices/<dev>/description
11 What: /sys/bus/most/devices/<dev>/interface
19 What: /sys/bus/most/devices/<dev>/dci
29 What: /sys/bus/most/devices/<dev>/dci/arb_address
38 What: /sys/bus/most/devices/<dev>/dci/arb_value
47 What: /sys/bus/most/devices/<dev>/dci/mep_eui48_hi
55 What: /sys/bus/most/devices/<dev>/dci/mep_eui48_lo
63 What: /sys/bus/most/devices/<dev>/dci/mep_eui48_mi
71 What: /sys/bus/most/devices/<dev>/dci/mep_filter
79 What: /sys/bus/most/devices/<dev>/dci/mep_hash0
[all …]
Dsysfs-bus-iio1 What: /sys/bus/iio/devices/iio:deviceX
9 What: /sys/bus/iio/devices/triggerX
23 What: /sys/bus/iio/devices/iio:deviceX/buffer
29 What: /sys/bus/iio/devices/iio:deviceX/name
36 What: /sys/bus/iio/devices/iio:deviceX/current_timestamp_clock
43 What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency
44 What: /sys/bus/iio/devices/iio:deviceX/in_intensity_sampling_frequency
45 What: /sys/bus/iio/devices/iio:deviceX/buffer/sampling_frequency
46 What: /sys/bus/iio/devices/triggerX/sampling_frequency
59 What: /sys/bus/iio/devices/iio:deviceX/sampling_frequency_available
[all …]
/Documentation/devicetree/bindings/bus/
Dsimple-pm-bus.yaml4 $id: http://devicetree.org/schemas/bus/simple-pm-bus.yaml#
7 title: Simple Power-Managed Bus
13 A Simple Power-Managed Bus is a transparent bus that doesn't need a real
16 However, its bus controller is part of a PM domain, or under the control
17 of a functional clock. Hence, the bus controller's PM domain and/or
18 clock must be enabled for child devices connected to the bus (either
21 While "simple-pm-bus" follows the "simple-bus" set of properties, as
23 "simple-bus".
27 pattern: "^bus(@[0-9a-f]+)?$"
31 const: simple-pm-bus
[all …]
Dsocionext,uniphier-system-bus.yaml4 $id: http://devicetree.org/schemas/bus/socionext,uniphier-system-bus.yaml#
7 title: UniPhier System Bus
10 The UniPhier System Bus is an external bus that connects on-board devices to
11 the UniPhier SoC. It is a simple (semi-)parallel bus with address, data, and
14 Before any access to the bus, the bus controller must be configured; the bus
18 be optimized for faster bus access.
25 const: socionext,uniphier-system-bus
41 Provide address translation from the System Bus to the parent bus.
44 The address region(s) that can be assigned for the System Bus is
58 work. The software should initialize the bus controller according to it.
[all …]
Drenesas,bsc.yaml3 $id: http://devicetree.org/schemas/bus/renesas,bsc.yaml#
6 title: Renesas Bus State Controller (BSC)
12 The Renesas Bus State Controller (BSC, sometimes called "LBSC within Bus
13 Bridge", or "External Bus Interface") can be found in several Renesas ARM
14 SoCs. It provides an external bus for connecting multiple external
18 While the BSC is a fairly simple memory-mapped bus, it may be part of a
24 The bindings for the BSC extend the bindings for "simple-pm-bus".
27 - $ref: simple-pm-bus.yaml#
36 - {} # simple-pm-bus, but not listed here to avoid false select
53 bsc: bus@fec10000 {
[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
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
49 The purpose of the match callback is to give the bus an opportunity to
[all …]
Dporting.rst16 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.
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,
59 The bus type may be unregistered (if the bus driver may be compiled
65 - Export the bus type for others to use.
[all …]
Doverview.rst16 bus-specific drivers for bridges and devices by consolidating a set of data
21 uniformity across the different bus types.
24 a bus and the devices that can appear under the bus. The unified bus
26 of common callbacks, such as device discovery during bus probing, bus
27 shutdown, bus power management, etc.
32 Microsoft (namely ACPI) ensures that almost every device on almost any bus
34 not every bus is able to support all such operations, although most
41 Common data fields have been moved out of individual bus layers into a common
42 data structure. These fields must still be accessed by the bus layers,
45 Other bus layers are encouraged to do what has been done for the PCI layer.
[all …]
/Documentation/devicetree/bindings/arm/omap/
Dl4.txt3 These bindings describe the OMAP SoCs L4 interconnect bus.
6 - compatible : Should be "ti,omap2-l4" for OMAP2 family l4 core bus
7 Should be "ti,omap2-l4-wkup" for OMAP2 family l4 wkup bus
8 Should be "ti,omap3-l4-core" for OMAP3 family l4 core bus
9 Should be "ti,omap4-l4-cfg" for OMAP4 family l4 cfg bus
10 Should be "ti,omap4-l4-per" for OMAP4 family l4 per bus
11 Should be "ti,omap4-l4-wkup" for OMAP4 family l4 wkup bus
12 Should be "ti,omap5-l4-cfg" for OMAP5 family l4 cfg bus
13 Should be "ti,omap5-l4-wkup" for OMAP5 family l4 wkup bus
14 Should be "ti,dra7-l4-cfg" for DRA7 family l4 cfg bus
[all …]
/Documentation/driver-api/soundwire/
Dlocking.rst5 This document explains locking mechanism of the SoundWire Bus. Bus uses
6 following locks in order to avoid race conditions in Bus operations on
9 - Bus lock
13 Bus lock
16 SoundWire Bus lock is a mutex and is part of Bus data structure
17 (sdw_bus) which is used for every Bus instance. This lock is used to
18 serialize each of the following operations(s) within SoundWire Bus instance.
30 Bus data structure (sdw_bus). This lock is used to serialize the message
31 transfers (read/write) within a SoundWire Bus instance.
45 Bus in case of bank switch.
[all …]
Dsummary.rst26 interfaces share the common Bus containing data and clock line. Each of the
61 Linux device model by mapping each Slave interface connected on the bus as a
65 common setup/configuration tasks are handled by the bus.
67 Bus:
68 Implements SoundWire Linux Bus which handles the SoundWire protocol.
70 Master. Multiple instances of Bus may be present in a system.
74 can register to a Bus instance.
78 directly by the Bus (and transmitted through the Master driver/interface).
86 SoundWire Bus supports programming interfaces for the SoundWire Master
90 Each of the SoundWire Master interfaces needs to be registered to the Bus.
[all …]
/Documentation/devicetree/bindings/i2c/
Di2c-aspeed.txt6 - reg : address offset and range of bus
7 - compatible : should be "aspeed,ast2400-i2c-bus"
8 or "aspeed,ast2500-i2c-bus"
9 or "aspeed,ast2600-i2c-bus"
10 - clocks : root clock of bus, should reference the APB
17 - bus-frequency : frequency of the bus clock in Hz defaults to 100 kHz when not
19 - multi-master : states that there is another master active on this bus.
24 compatible = "simple-bus";
37 i2c0: i2c-bus@40 {
42 compatible = "aspeed,ast2400-i2c-bus";
[all …]
/Documentation/scsi/
Dadvansys.rst8 RISC-based, Bus-Mastering, Fast (10 Mhz) and Ultra (20 Mhz) Narrow
10 buses and RISC-based, Bus-Mastering, Ultra (20 Mhz) Wide (16-bit
11 transfer) SCSI Host Adapters for the PCI bus.
21 - ABP-480 - Bus-Master CardBus (16 CDB)
24 - ABP510/5150 - Bus-Master ISA (240 CDB)
25 - ABP5140 - Bus-Master ISA PnP (16 CDB)
26 - ABP5142 - Bus-Master ISA PnP with floppy (16 CDB)
27 - ABP902/3902 - Bus-Master PCI (16 CDB)
28 - ABP3905 - Bus-Master PCI (16 CDB)
29 - ABP915 - Bus-Master PCI (16 CDB)
[all …]
/Documentation/ABI/stable/
Dsysfs-driver-dma-idxd1 What: /sys/bus/dsa/devices/dsa<m>/version
7 What: /sys/bus/dsa/devices/dsa<m>/cdev_major
14 What: /sys/bus/dsa/devices/dsa<m>/errors
20 What: /sys/bus/dsa/devices/dsa<m>/max_batch_size
26 What: /sys/bus/dsa/devices/dsa<m>/max_work_queues_size
32 What: /sys/bus/dsa/devices/dsa<m>/max_engines
38 What: /sys/bus/dsa/devices/dsa<m>/max_groups
44 What: /sys/bus/dsa/devices/dsa<m>/max_tokens
53 What: /sys/bus/dsa/devices/dsa<m>/max_transfer_size
61 What: /sys/bus/dsa/devices/dsa<m>/max_work_queues
[all …]
/Documentation/i2c/
Dgpio-fault-injection.rst5 The GPIO based I2C bus master driver can be configured to provide fault
6 injection capabilities. It is then meant to be connected to another I2C bus
7 which is driven by the I2C bus master driver under test. The GPIO fault
8 injection driver can create special states on the bus which the other I2C bus
14 driven I2C bus. Each subdirectory will contain files to trigger the fault
26 because the bus master under test will not be able to clock. It should detect
35 "echo 0 > sda" you force SDA low and thus, data cannot be transmitted. The bus
36 master under test should detect this condition and trigger a bus recovery (see
38 core (see 'struct bus_recovery_info'). However, the bus recovery will not
47 device. Bus recovery should be able to fix these situations. But please note:
[all …]
/Documentation/devicetree/bindings/devfreq/
Dexynos-bus.txt1 * Generic Exynos Bus frequency device
5 for buses. Generally, each bus of Exynos SoC includes a source clock
7 of the bus in runtime. To monitor the usage of each bus in runtime,
11 The Exynos SoC includes the various sub-blocks which have the each AXI bus.
12 The each AXI bus has the owned source clock but, has not the only owned
15 There are two type of bus devices as following:
16 - parent bus device
17 - passive bus device
19 Basically, parent and passive bus device share the same power line.
20 The parent bus device can only change the voltage of shared power line
[all …]

12345678910>>...61