Home
last modified time | relevance | path

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

12345678910>>...29

/openbmc/linux/drivers/w1/slaves/
H A 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 …]
/openbmc/u-boot/doc/
H A DREADME.VSC3316-33082 Vitesse cross-point devices, VSC3316 and VSC3308 for board B4860QDS
8 VSC 3316/3308 is a low-power, low-cost asynchronous crosspoint switch capable of data rates upto 11…
10 …d 8 output ports. Programming of these devices are performed by two-wire or four-wire serial inter…
14 On reset, VSC devices are in low-power state with all inputs, outputs and connections in an off sta…
15 First thing required is to program it to interface with either two-wire or four-wire interface.
16 … interface is two-wire I2C serial interface. So the value in Interface mode register at address 79…
22 --------------------------
23-wire or four-wire interface. In our case the interface is two-wire I2C serial interface. So the v…
25 vsc_addr - Address of the VSC device on board.
29 ---------------------------------------------------------
[all …]
/openbmc/linux/drivers/w1/masters/
H A 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 …]
H A 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 …]
/openbmc/linux/Documentation/devicetree/bindings/iio/temperature/
H A 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 …]
/openbmc/qemu/qapi/
H A Dintrospect.json1 # -*- Mode: Python -*-
9 # This work is licensed under the terms of the GNU GPL, version 2 or later.
10 # See the COPYING file in the top-level directory.
17 # @query-qmp-schema:
19 # Command query-qmp-schema exposes the QMP wire ABI as an array of
28 # Furthermore, while we strive to keep the QMP wire format
29 # backwards-compatible across qemu versions, the introspection output
32 # non-variant, while another lists the same member only through the
33 # object's variants; or the type of a member may change from a generic
34 # string into a specific enum or from one specific type into an
[all …]
/openbmc/u-boot/drivers/w1-eeprom/
H A DKconfig5 menu "1-wire EEPROM support"
8 bool "Enable support for EEPROMs on 1wire interface"
11 Support for the EEPROMs connected on 1-wire Dallas protocol interface
19 Maxim DS24 EEPROMs 1-Wire EEPROM support
22 bool "Enable Maxim DS2502 Add-Only Memory support"
25 Maxim DS2502 1-Wire add-only memory support.
32 or as a 128 byte memory, ignoring the page redirection.
/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/
H A 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 …]
/openbmc/linux/net/rxrpc/
H A 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 …]
/openbmc/linux/Documentation/peci/
H A 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 …]
/openbmc/linux/drivers/w1/
H A 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.
/openbmc/linux/arch/sh/mm/
H A 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.
/openbmc/linux/Documentation/devicetree/bindings/display/panel/
H A 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 …]
/openbmc/linux/include/linux/platform_data/
H A 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)
/openbmc/linux/Documentation/driver-api/gpio/
H A 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 …]
/openbmc/linux/include/linux/
H A 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 …]
/openbmc/linux/Documentation/w1/
H A 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 …]
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/
H A DSensor_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Sensor v1.10.1 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/
H A DSensor_v1.xml1 <?xml version="1.0" encoding="UTF-8"?>
2 <!---->
3 <!--################################################################################ -->
4 <!--# Redfish Schema: Sensor v1.10.1 -->
5 <!--# -->
6 <!--# For a detailed change log, see the README file contained in the DSP8010 bundle, -->
7 <!--# available at http://www.dmtf.org/standards/redfish -->
8 <!--# Copyright 2014-2024 DMTF. -->
9 <!--# For the full DMTF copyright policy, see http://www.dmtf.org/about/policies/copyright -->
10 <!--################################################################################ -->
[all …]
/openbmc/linux/Documentation/devicetree/bindings/sound/
H A Dawinic,aw8738.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Stephan Gerhold <stephan@gerhold.net>
14 (set using one-wire pulse control). The mode configures the speaker-guard
18 - $ref: dai-common.yaml#
24 mode-gpios:
26 GPIO used for one-wire pulse control. The pin is typically called SHDN
27 (active-low), but this is misleading since it is actually more than
32 description: Operation mode (number of pulses for one-wire pulse control)
[all …]
/openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/
H A 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 …]
/openbmc/linux/drivers/bluetooth/
H A DKconfig1 # SPDX-License-Identifier: GPL-2.0
36 kernel or say M to compile it as module (btusb).
102 kernel or say M to compile it as module (btsdio).
117 kernel or say M to compile it as module (hci_uart).
187 bool "Three-wire UART (H5) protocol support"
191 The HCI Three-wire UART Transport Layer makes it possible to
193 Three-wire UART Transport Layer assumes that the UART
194 communication may have bit errors, overrun errors or burst
197 Say Y here to compile support for Three-wire UART protocol.
234 The Realtek protocol support enables Bluetooth HCI over 3-Wire
[all …]
/openbmc/linux/sound/ppc/
H A Dsnd_ps3_reg.h1 /* SPDX-License-Identifier: GPL-2.0-only */
39 * three wire serial
73 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
75 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
92 corresponding bit in PS3_AUDIO_INTR_0. The resulting bits are OR'd together
96 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
98 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
106 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
108 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
125 +-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-|-+-+-+-+-+-+-+-+
[all …]
/openbmc/linux/Documentation/devicetree/bindings/w1/
H A Domap-hdq.txt1 * OMAP HDQ One wire bus master controller
4 - compatible : should be "ti,omap3-1w" or "ti,am4372-hdq"
5 - reg : Address and length of the register set for the device
6 - interrupts : interrupt line.
7 - ti,hwmods : "hdq1w"
10 - ti,mode: should be "hdq": HDQ mode "1w": one-wire mode.
15 - From omap3.dtsi
17 compatible = "ti,omap3-1w";
/openbmc/linux/include/linux/mfd/
H A Dmxs-lradc.h1 /* SPDX-License-Identifier: GPL-2.0-or-later */
3 * Freescale MXS Low Resolution Analog-to-Digital Converter driver
110 #define LRADC_SINGLE_SAMPLE_MASK ((1 << LRADC_RESOLUTION) - 1)
117 * and/or touch-buttons and generic LRADC block. Therefore when using
121 * CH0 -- Touch button #0
122 * CH1 -- Touch button #1
123 * CH2 -- Touch screen XPUL
124 * CH3 -- Touch screen YPLL
125 * CH4 -- Touch screen XNUL
126 * CH5 -- Touch screen YNLR
[all …]

12345678910>>...29