/openbmc/u-boot/drivers/w1/ |
H A D | Kconfig | 5 menu "1-Wire support" 8 bool "Enable 1-wire controllers support" 12 Support for the Dallas 1-Wire bus. 17 bool "Enable 1-wire GPIO bitbanging" 21 Emulate a 1-wire bus using a GPIO. 24 bool "Enable 1-wire controller on i.MX processors" 28 Support the one wire controller found in some members of the NXP 33 Newer i.MX SoCs such as the i.MX6 do not have one wire controllers.
|
H A D | mxc_w1.c | 3 * Driver for one wire controller in some i.MX Socs 8 * Newer i.MX SoCs such as the i.MX6 do not have one wire controllers. 53 * this is the low level routine to read/write a bit on the One Wire
|
/openbmc/u-boot/doc/ |
H A D | README.VSC3316-3308 | 10 …d 8 output ports. Programming of these devices are performed by two-wire or four-wire serial inter… 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… 23 …wire or four-wire interface. In our case the interface is two-wire I2C serial interface. So the va…
|
/openbmc/u-boot/drivers/w1-eeprom/ |
H A D | Kconfig | 5 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 25 Maxim DS2502 1-Wire add-only memory support.
|
/openbmc/openbmc/meta-openembedded/meta-filesystems/recipes-filesystems/owfs/ |
H A D | owfs_3.2p3.bb | 1 SUMMARY = "1-Wire file system" 2 DESCRIPTION = "OWFS is an easy way to use the powerful 1-wire system of Dallas/Maxim" 46 DESCRIPTION:owftpd = "Anoymous FTP server for 1-wire access" 47 DESCRIPTION:owhttpd = "Tiny webserver for 1-wire control" 48 DESCRIPTION:owserver = "Backend server (daemon) for 1-wire control" 50 DESCRIPTION:libowcapi = "easy C-language 1-wire interface " 51 DESCRIPTION:libow = "easy C-language 1-wire interface to the owserver protocol" 52 DESCRIPTION:libownet = "easy C-language 1-wire interface to the owserver protocol"
|
/openbmc/qemu/qapi/ |
H A D | introspect.json | 21 # Command `query-qmp-schema` exposes the QMP wire ABI as an array of 30 # Furthermore, while we strive to keep the QMP wire format 48 # QMP wire ABI, and therefore not returned by this command. 88 # names, type names are not part of the wire ABI. Consequently, 118 # @json-type: the JSON type used for this type on the wire. 170 # Values of this type are JSON string on the wire. 201 # Values of this type are JSON array on the wire. 224 # Values of this type are JSON object on the wire. 279 # members' wire encoding is distinct, see 282 # On the wire, this can be any of the members.
|
/openbmc/u-boot/doc/device-tree-bindings/w1/ |
H A D | w1-gpio.txt | 1 W1 gpio device binding - one wire protocol over bitbanged gpio 18 This is the gpio used for one wire protocol, using bitbanging
|
/openbmc/openbmc/meta-raspberrypi/recipes-connectivity/bluez5/bluez5/ |
H A D | 0001-bcm43xx-Add-bcm43xx-3wire-variant.patch | 4 Subject: [PATCH] bcm43xx: Add bcm43xx-3wire variant 20 + { "bcm43xx-3wire", 0x0000, 0x0000, HCI_UART_3WIRE, 115200, 3000000,
|
/openbmc/u-boot/doc/device-tree-bindings/spi/ |
H A D | spi-bus.txt | 56 - spi-3wire - (optional) Empty property indicating device requires 57 3-wire mode. 69 Dual/Quad mode is not allowed when 3-wire mode is used.
|
/openbmc/u-boot/board/freescale/common/ |
H A D | vsc3316_3308.c | 31 " for 2-wire interface\n", vsc_addr); in vsc_if_enable() 33 /* enable 2-wire Serial InterFace (I2C) */ in vsc_if_enable() 63 printf("VSC:0x%x could not configured for 2-wire I/F.\n", in vsc3316_config() 125 printf("VSC:0x%x could not configured for 2-wire I/F.\n", in vsc3308_config_adjust() 227 printf("VSC:0x%x could not configured for 2-wire I/F.\n", in vsc3308_config()
|
/openbmc/u-boot/test/py/tests/ |
H A D | test_pinmux.py | 29 assert ('W1 : 1-wire gpio' in output) 66 assert ('W1 : 1-wire gpio' in output)
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-multimedia/xsp/xsp/ |
H A D | 0001-fix-incompatible-pointer-types-build-error-in-gcc-15.patch | 38 static Bool XSPWireToEvent(Display *dpy, XEvent *event, xEvent *wire); 40 static Status XSPEventToWire(Display *dpy, XEvent *event, xEvent *wire);
|
/openbmc/openbmc/meta-openembedded/meta-oe/recipes-graphics/tslib/ |
H A D | tslib_1.23.bb | 52 PACKAGECONFIG[one-wire-ts-input] = "--enable-one-wire-ts-input,--disable-one-wire-ts-input"
|
/openbmc/u-boot/arch/arm/mach-at91/include/mach/ |
H A D | at91sam9x5.h | 27 #define ATMEL_ID_TWI0 9 /* Two-Wire Interface 0 */ 28 #define ATMEL_ID_TWI1 10 /* Two-Wire Interface 1 */ 29 #define ATMEL_ID_TWI2 11 /* Two-Wire Interface 2 */
|
H A D | sama5d4.h | 45 #define ATMEL_ID_TWI0 32 /* Two-Wire Interface 0 */ 46 #define ATMEL_ID_TWI1 33 /* Two-Wire Interface 1 */ 47 #define ATMEL_ID_TWI2 34 /* Two-Wire Interface 2 */ 73 #define ATMEL_ID_TWI3 62 /* Two-Wire Interface 3 */
|
H A D | sama5d3.h | 36 #define ATMEL_ID_TWI0 18 /* Two-Wire Interface 0 */ 37 #define ATMEL_ID_TWI1 19 /* Two-Wire Interface 1 */ 38 #define ATMEL_ID_TWI2 20 /* Two-Wire Interface 2 */
|
/openbmc/qemu/tests/qapi-schema/ |
H A D | struct-base-clash.json | 2 # Here, 'name' would have to appear twice on the wire, locally and for base.
|
H A D | struct-base-clash-deep.json | 2 # Here, 'name' would have to appear twice on the wire, locally and
|
/openbmc/bmcweb/redfish-core/schema/dmtf/installed/ |
H A D | Sensor_v1.xml | 119 …s circuits with phase wiring types of Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-Wire or 5-W… 123 …uch as circuits with phase wiring types of Two-phase / 4-Wire or Three-phase / 4-Wire or 5-Wire."/> 127 …-carrying conductor, such as circuits with phase wiring types of Three-phase / 4-Wire or 5-Wire."/> 131 …ircuits with phase wiring types of Single-phase / 3-Wire, Two-phase / 4-Wire, or Three-phase / 5-W… 135 …s circuits with phase wiring types of Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-Wire or 5-W… 139 …s circuits with phase wiring types of Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-Wire or 5-W… 143 …carrying conductors, such as circuits with phase wiring types of Three-phase / 4-Wire or 5-Wire."/> 147 …carrying conductors, such as circuits with phase wiring types of Three-phase / 4-Wire or 5-Wire."/> 151 …ts with phase wiring types of Single-phase / 3-Wire, Two-phase / 4-Wire, or Three-phase / 4-Wire o… 155 …th phase wiring types of Single-phase / 3-Wire, Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-W… [all …]
|
/openbmc/bmcweb/redfish-core/schema/dmtf/csdl/ |
H A D | Sensor_v1.xml | 119 …s circuits with phase wiring types of Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-Wire or 5-W… 123 …uch as circuits with phase wiring types of Two-phase / 4-Wire or Three-phase / 4-Wire or 5-Wire."/> 127 …-carrying conductor, such as circuits with phase wiring types of Three-phase / 4-Wire or 5-Wire."/> 131 …ircuits with phase wiring types of Single-phase / 3-Wire, Two-phase / 4-Wire, or Three-phase / 5-W… 135 …s circuits with phase wiring types of Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-Wire or 5-W… 139 …s circuits with phase wiring types of Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-Wire or 5-W… 143 …carrying conductors, such as circuits with phase wiring types of Three-phase / 4-Wire or 5-Wire."/> 147 …carrying conductors, such as circuits with phase wiring types of Three-phase / 4-Wire or 5-Wire."/> 151 …ts with phase wiring types of Single-phase / 3-Wire, Two-phase / 4-Wire, or Three-phase / 4-Wire o… 155 …th phase wiring types of Single-phase / 3-Wire, Two-phase / 3-Wire or 4-Wire, or Three-phase / 4-W… [all …]
|
/openbmc/openbmc/poky/meta/lib/oeqa/runtime/cases/ |
H A D | parselogs-ignores-qemuppc.txt | 3 host side 80-wire cable detection failed, limiting max speed
|
/openbmc/u-boot/board/nokia/rx51/ |
H A D | tag_omap.h | 84 * 3 == 3 wire bidirectional 85 * 4 == 4 wire bidirectional 86 * 6 == 6 wire unidirectional (or TLL)
|
/openbmc/u-boot/cmd/ |
H A D | w1.c | 20 printf("one wire interface not found\n"); in w1_bus() 71 printf("one wire interface not found\n"); in w1_read()
|
/openbmc/qemu/include/hw/xen/interface/io/ |
H A D | xs_wire.h | 3 * Details of the "wire" protocol between Xen Store Daemon and client 99 * `incontents 150 xenstore_struct XenStore wire protocol.
|
/openbmc/openbmc/meta-raspberrypi/recipes-connectivity/bluez5/ |
H A D | bluez5_%.bbappend | 4 file://0001-bcm43xx-Add-bcm43xx-3wire-variant.patch \
|