Home
last modified time | relevance | path

Searched +full:wire +full:- +full:or (Results 1 – 25 of 1004) sorted by relevance

12345678910>>...41

/kernel/linux/linux-5.10/drivers/w1/slaves/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # 1-wire slaves configuration
6 menu "1-wire Slaves"
11 Say Y here if you want to connect 1-wire thermal sensors to your
12 wire.
17 Say Y here if you want to connect 1-wire
18 simple 64bit memory rom(ds2401/ds2411/ds1990*) to your wire.
23 Say Y or M here if you want to use a DS2405 1-wire
24 single-channel addressable switch.
25 This device can also work as a single-channel
[all …]
/kernel/linux/linux-6.6/drivers/w1/slaves/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # 1-wire slaves configuration
6 menu "1-wire Slaves"
11 Say Y here if you want to connect 1-wire thermal sensors to your
12 wire.
17 Say Y here if you want to connect 1-wire
18 simple 64bit memory rom(ds2401/ds2411/ds1990*) to your wire.
23 Say Y or M here if you want to use a DS2405 1-wire
24 single-channel addressable switch.
25 This device can also work as a single-channel
[all …]
/kernel/linux/linux-5.10/drivers/w1/masters/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # 1-wire bus master configuration
6 menu "1-wire Bus Masters"
9 tristate "Matrox G400 transport layer for 1-wire"
12 Say Y here if you want to communicate with your 1-wire devices
19 tristate "DS2490 USB <-> W1 transport layer for 1-wire"
22 Say Y here if you want to have a driver for DS2490 based USB <-> W1 bridges,
29 tristate "Maxim DS2482 I2C to 1-Wire bridge"
33 I2C to 1-Wire bridge.
39 tristate "Freescale MXC 1-wire busmaster"
[all …]
Dds2482.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * ds2482.c - provides i2c to w1-master bridge(s)
7 * It is a I2C to 1-wire bridge.
8 * There are two variations: -100 and -800, which have 1 or 8 1-wire ports.
10 * http://www.maxim-ic.com/quick_view2.cfm/qv_pk/4382
26 * The APU bit controls whether an active pullup (controlled slew-rate
27 * transistor) or a passive pullup (Rwpu resistor) will be used to drive
28 * a 1-Wire line from low to high. When APU = 0, active pullup is disabled
30 * only a single slave on the 1-Wire line.
35 "0-disable, 1-enable (default)");
[all …]
/kernel/linux/linux-6.6/drivers/w1/masters/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 # 1-wire bus master configuration
6 menu "1-wire Bus Masters"
9 tristate "Matrox G400 transport layer for 1-wire"
12 Say Y here if you want to communicate with your 1-wire devices
19 tristate "DS2490 USB <-> W1 transport layer for 1-wire"
22 Say Y here if you want to have a driver for DS2490 based USB <-> W1 bridges,
29 tristate "Maxim DS2482 I2C to 1-Wire bridge"
33 I2C to 1-Wire bridge.
39 tristate "Freescale MXC 1-wire busmaster"
[all …]
Dds2482.c1 // SPDX-License-Identifier: GPL-2.0-only
3 * ds2482.c - provides i2c to w1-master bridge(s)
7 * It is a I2C to 1-wire bridge.
8 * There are two variations: -100 and -800, which have 1 or 8 1-wire ports.
10 * http://www.maxim-ic.com/quick_view2.cfm/qv_pk/4382
25 * The APU bit controls whether an active pullup (controlled slew-rate
26 * transistor) or a passive pullup (Rwpu resistor) will be used to drive
27 * a 1-Wire line from low to high. When APU = 0, active pullup is disabled
29 * only a single slave on the 1-Wire line.
34 "0-disable, 1-enable (default)");
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/iio/temperature/
Dmaxim,max31865.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Navin Sankar Velliangiri <navin@linumiz.com>
22 maxim,3-wire:
25 enables 3-wire RTD connection. Else 2-wire or 4-wire RTD connection.
28 spi-cpha: true
31 - compatible
32 - reg
33 - spi-cpha
[all …]
/kernel/linux/linux-6.6/net/rxrpc/
Dtxbuf.c1 // SPDX-License-Identifier: GPL-2.0-or-later
11 #include "ar-internal.h"
26 INIT_LIST_HEAD(&txb->call_link); in rxrpc_alloc_txbuf()
27 INIT_LIST_HEAD(&txb->tx_link); in rxrpc_alloc_txbuf()
28 refcount_set(&txb->ref, 1); in rxrpc_alloc_txbuf()
29 txb->call_debug_id = call->debug_id; in rxrpc_alloc_txbuf()
30 txb->debug_id = atomic_inc_return(&rxrpc_txbuf_debug_ids); in rxrpc_alloc_txbuf()
31 txb->space = sizeof(txb->data); in rxrpc_alloc_txbuf()
32 txb->len = 0; in rxrpc_alloc_txbuf()
33 txb->offset = 0; in rxrpc_alloc_txbuf()
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/interrupt-controller/
Dintel,ce4100-lapic.yaml1 # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/interrupt-controller/intel,ce4100-lapic.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Rahul Tanwar <rtanwar@maxlinear.com>
28 [1] https://pdos.csail.mit.edu/6.828/2008/readings/ia32/IA32-3A.pdf
32 const: intel,ce4100-lapic
37 interrupt-controller: true
39 '#interrupt-cells':
42 intel,virtual-wire-mode:
[all …]
/kernel/linux/linux-6.6/Documentation/peci/
Dpeci.rst1 .. SPDX-License-Identifier: GPL-2.0-only
13 controller is acting as a PECI originator and the processor - as
15 PECI can be used in both single processor and multiple-processor based
24 PECI Wire
25 ---------
27 PECI Wire interface uses a single wire for self-clocking and data
28 transfer. It does not require any additional control lines - the
29 physical layer is a self-clocked one-wire bus signal that begins each
32 value is logic '0' or logic '1'. PECI Wire also includes variable data
35 For PECI Wire, each processor package will utilize unique, fixed
[all …]
/kernel/linux/linux-6.6/drivers/w1/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Dallas's 1-wire support"
6 Dallas' 1-wire bus is useful to connect slow 1-pin devices
12 will be called wire.
22 information see <file:Documentation/driver-api/connector.rst>.
24 1. Events. They are generated each time new master or slave device found
25 either due to automatic or requested search.
/kernel/linux/linux-5.10/drivers/w1/
DKconfig1 # SPDX-License-Identifier: GPL-2.0-only
3 tristate "Dallas's 1-wire support"
6 Dallas' 1-wire bus is useful to connect slow 1-pin devices
12 will be called wire.
22 information see <file:Documentation/driver-api/connector.rst>.
24 1. Events. They are generated each time new master or slave device found
25 either due to automatic or requested search.
/kernel/linux/linux-5.10/arch/sh/mm/
Dtlb-urb.c2 * arch/sh/mm/tlb-urb.c
4 * TLB entry wiring helpers for URB-equipped parts.
18 * Load the entry for 'addr' into the TLB and wire the entry.
32 * Make sure we're not trying to wire the last TLB entry slot. in tlb_wire_entry()
34 BUG_ON(!--urb); in tlb_wire_entry()
39 * Insert this entry into the highest non-wired TLB slot (via in tlb_wire_entry()
49 /* ... and wire it up. */ in tlb_wire_entry()
64 * It should also be noted that it is not possible to wire and unwire
65 * TLB entries in an arbitrary order. If you wire TLB entry N, followed
67 * respect, it works like a stack or LIFO queue.
/kernel/linux/linux-6.6/arch/sh/mm/
Dtlb-urb.c2 * arch/sh/mm/tlb-urb.c
4 * TLB entry wiring helpers for URB-equipped parts.
18 * Load the entry for 'addr' into the TLB and wire the entry.
32 * Make sure we're not trying to wire the last TLB entry slot. in tlb_wire_entry()
34 BUG_ON(!--urb); in tlb_wire_entry()
39 * Insert this entry into the highest non-wired TLB slot (via in tlb_wire_entry()
49 /* ... and wire it up. */ in tlb_wire_entry()
64 * It should also be noted that it is not possible to wire and unwire
65 * TLB entries in an arbitrary order. If you wire TLB entry N, followed
67 * respect, it works like a stack or LIFO queue.
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/display/panel/
Dtpo,tpg110.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Thierry Reding <thierry.reding@gmail.com>
17 and other properties, and has a control interface over 3WIRE
20 self-describing.
22 +--------+
23 SPI -> | TPO | -> physical display
24 RGB -> | TPG110 |
[all …]
/kernel/linux/linux-5.10/Documentation/devicetree/bindings/display/panel/
Dtpo,tpg110.yaml1 # SPDX-License-Identifier: GPL-2.0
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Linus Walleij <linus.walleij@linaro.org>
11 - Thierry Reding <thierry.reding@gmail.com>
17 and other properties, and has a control interface over 3WIRE
20 self-describing.
22 +--------+
23 SPI -> | TPO | -> physical display
24 RGB -> | TPG110 |
[all …]
/kernel/linux/linux-5.10/include/linux/platform_data/
Dusb-omap1.h15 * - "A" connector (rectagular)
17 * - "B" connector (squarish) or "Mini-B"
19 * - "Mini-AB" connector (very similar to Mini-B)
20 * ... for OTG use as device OR host, initialize "otg"
24 u8 otg; /* port number, 1-based: usb1 == 2 */
35 * 2 == usb0-only, using internal transceiver
36 * 3 == 3 wire bidirectional
37 * 4 == 4 wire bidirectional
38 * 6 == 6 wire unidirectional (or TLL)
/kernel/linux/linux-6.6/include/linux/platform_data/
Dusb-omap1.h15 * - "A" connector (rectagular)
17 * - "B" connector (squarish) or "Mini-B"
19 * - "Mini-AB" connector (very similar to Mini-B)
20 * ... for OTG use as device OR host, initialize "otg"
24 u8 otg; /* port number, 1-based: usb1 == 2 */
35 * 2 == usb0-only, using internal transceiver
36 * 3 == 3 wire bidirectional
37 * 4 == 4 wire bidirectional
38 * 6 == 6 wire unidirectional (or TLL)
/kernel/linux/linux-5.10/Documentation/driver-api/gpio/
Dintro.rst16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
17 and is described by all the files in this directory excepted gpio-legacy.txt.
18 - The legacy integer-based interface which is considered deprecated (but still
19 usable for compatibility reasons) is documented in gpio-legacy.txt.
21 The remainder of this document applies to the new descriptor-based interface.
22 gpio-legacy.txt contains the same information applied to the legacy
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
32 represents a bit connected to a particular pin, or "ball" on Ball Grid Array
37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
[all …]
/kernel/linux/linux-6.6/Documentation/driver-api/gpio/
Dintro.rst16 - The descriptor-based interface is the preferred way to manipulate GPIOs,
18 - The legacy integer-based interface which is considered deprecated (but still
21 The remainder of this document applies to the new descriptor-based interface.
23 integer-based interface.
29 A "General Purpose Input/Output" (GPIO) is a flexible software-controlled
32 represents a bit connected to a particular pin, or "ball" on Ball Grid Array
37 System-on-Chip (SOC) processors heavily rely on GPIOs. In some cases, every
38 non-dedicated pin can be configured as a GPIO; and most chips have at least
42 also "GPIO Expander" chips that connect using the I2C or SPI serial buses.
43 Most PC southbridges have a few dozen GPIO-capable pins (with only the BIOS
[all …]
/kernel/linux/linux-6.6/include/linux/
Dw1.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
12 * struct w1_reg_num - broken out slave device id
49 * struct w1_slave - holds a single slave device on the bus
51 * @owner: Points to the one wire "wire" kernel module.
84 * struct w1_bus_master - operations available on a bus master
88 * @read_bit: Sample the line level @return the level read (0 or 1)
92 * @touch_bit: the lowest-level function for devices that really support the
93 * 1-wire protocol.
94 * touch_bit(0) = write-0 cycle
95 * touch_bit(1) = write-1 / read cycle
[all …]
/kernel/linux/linux-5.10/include/linux/
Dw1.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
12 * struct w1_reg_num - broken out slave device id
49 * struct w1_slave - holds a single slave device on the bus
51 * @owner: Points to the one wire "wire" kernel module.
84 * struct w1_bus_master - operations available on a bus master
88 * @read_bit: Sample the line level @return the level read (0 or 1)
92 * @touch_bit: the lowest-level function for devices that really support the
93 * 1-wire protocol.
94 * touch_bit(0) = write-0 cycle
95 * touch_bit(1) = write-1 / read cycle
[all …]
/kernel/linux/linux-6.6/Documentation/devicetree/bindings/input/touchscreen/
Dti,am3359-tsc.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/input/touchscreen/ti,am3359-tsc.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Miquel Raynal <miquel.raynal@bootlin.com>
14 const: ti,am3359-tsc
17 description: Wires refer to application modes i.e. 4/5/8 wire touchscreen
22 ti,x-plate-resistance:
26 ti,coordinate-readouts:
36 ti,wire-config:
[all …]
/kernel/linux/linux-6.6/Documentation/w1/
Dw1-generic.rst2 Introduction to the 1-wire (w1) subsystem
5 The 1-wire bus is a simple master-slave bus that communicates via a single
6 signal wire (plus ground, so two wires).
18 - DS9490 usb device
19 - W1-over-GPIO
20 - DS2482 (i2c to w1 bridge)
21 - Emulated devices, such as a RS232 converter, parallel port adapter, etc
25 ------------------------------
29 - sysfs entries for that w1 master are created
30 - the w1 bus is periodically searched for new slave devices
[all …]
/kernel/linux/linux-5.10/Documentation/w1/
Dw1-generic.rst2 Introduction to the 1-wire (w1) subsystem
5 The 1-wire bus is a simple master-slave bus that communicates via a single
6 signal wire (plus ground, so two wires).
18 - DS9490 usb device
19 - W1-over-GPIO
20 - DS2482 (i2c to w1 bridge)
21 - Emulated devices, such as a RS232 converter, parallel port adapter, etc
25 ------------------------------
29 - sysfs entries for that w1 master are created
30 - the w1 bus is periodically searched for new slave devices
[all …]

12345678910>>...41