/openbmc/linux/drivers/w1/masters/ |
H A D | Kconfig | 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" 29 tristate "Maxim DS2482 I2C to 1-Wire bridge" 33 I2C to 1-Wire bridge. 39 tristate "Freescale MXC 1-wire busmaster" 42 Say Y here to enable MXC 1-wire host 45 tristate "GPIO 1-wire busmaster" [all …]
|
H A D | ds2482.c | 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. 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. 69 #define DS2482_REG_CFG_1WS 0x08 /* 1-wire speed */ 112 /* 1-wire interface(s) */ 199 * 1-Wire interface code 205 * ds2482_wait_1wire_idle - Waits until the 1-wire interface is idle (not busy) 231 * The 1-wire interface must be idle before calling this function. 378 * ds2482_w1_reset_bus - Sends a reset on the 1-wire interface [all …]
|
H A D | sgi_w1.c | 3 * sgi_w1.c - w1 master driver for one wire support in SGI ASICs 41 * reset the device on the One Wire interface 56 * this is the low level routine to read/write a bit on the One Wire 128 MODULE_DESCRIPTION("Driver for One-Wire IP in SGI ASICs");
|
/openbmc/linux/drivers/w1/slaves/ |
H A D | Kconfig | 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 31 Say Y here if you want to use a 1-wire 47 Say Y here if you want to use a 1-wire 54 Say Y or M here if you want to use a 1-wire [all …]
|
/openbmc/linux/Documentation/w1/masters/ |
H A D | omap-hdq.rst | 2 Kernel driver for omap HDQ/1-wire module 7 HDQ/1-wire controller on the TI OMAP 2430/3430 platforms. 15 The HDQ/1-Wire module of TI OMAP2430/3430 platforms implement the hardware 17 Semiconductor 1-Wire protocols. These protocols use a single wire for 18 communication between the master (HDQ/1-Wire controller) and the slave 19 (HDQ/1-Wire external compliant device). 21 A typical application of the HDQ/1-Wire module is the communication with battery 24 The controller supports operation in both HDQ and 1-wire mode. The essential 25 difference between the HDQ and 1-wire mode is how the slave device responds to 29 does not respond with a presence pulse as it does in the 1-Wire protocol. [all …]
|
/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.
|
/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/linux/net/rxrpc/ |
H A D | txbuf.c | 37 txb->wire.epoch = htonl(call->conn->proto.epoch); in rxrpc_alloc_txbuf() 38 txb->wire.cid = htonl(call->cid); in rxrpc_alloc_txbuf() 39 txb->wire.callNumber = htonl(call->call_id); in rxrpc_alloc_txbuf() 40 txb->wire.seq = htonl(txb->seq); in rxrpc_alloc_txbuf() 41 txb->wire.type = packet_type; in rxrpc_alloc_txbuf() 42 txb->wire.flags = call->conn->out_clientflag; in rxrpc_alloc_txbuf() 43 txb->wire.userStatus = 0; in rxrpc_alloc_txbuf() 44 txb->wire.securityIndex = call->security_ix; in rxrpc_alloc_txbuf() 45 txb->wire._rsvd = 0; in rxrpc_alloc_txbuf() 46 txb->wire.serviceId = htons(call->dest_srx.srx_service); in rxrpc_alloc_txbuf()
|
H A D | output.c | 209 txb->wire.flags |= RXRPC_REQUEST_ACK; in rxrpc_send_ack_packet() 215 iov[0].iov_base = &txb->wire; in rxrpc_send_ack_packet() 216 iov[0].iov_len = sizeof(txb->wire) + sizeof(txb->ack) + n; in rxrpc_send_ack_packet() 220 txb->wire.serial = htonl(serial); in rxrpc_send_ack_packet() 241 trace_rxrpc_tx_packet(call->debug_id, &txb->wire, in rxrpc_send_ack_packet() 243 if (txb->wire.flags & RXRPC_REQUEST_ACK) in rxrpc_send_ack_packet() 338 txb->wire.serial = htonl(serial); in rxrpc_send_data_packet() 342 txb->wire.userStatus = RXRPC_USERSTATUS_SERVICE_UPGRADE; in rxrpc_send_data_packet() 344 iov[0].iov_base = &txb->wire; in rxrpc_send_data_packet() 345 iov[0].iov_len = sizeof(txb->wire) + txb->len; in rxrpc_send_data_packet() [all …]
|
/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/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/linux/Documentation/peci/ |
H A D | peci.rst | 24 PECI Wire 27 PECI Wire interface uses a single wire for self-clocking and data 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
|
/openbmc/linux/include/linux/mfd/ |
H A D | motorola-cpcap.h | 186 #define CPCAP_REG_OWDC 0x0eb0 /* One Wire Device Control */ 212 #define CPCAP_REG_OW1C 0x1200 /* One Wire 1 Command */ 213 #define CPCAP_REG_OW1D 0x1204 /* One Wire 1 Data */ 214 #define CPCAP_REG_OW1I 0x1208 /* One Wire 1 Interrupt */ 215 #define CPCAP_REG_OW1IE 0x120c /* One Wire 1 Interrupt Enable */ 217 #define CPCAP_REG_OW1 0x1214 /* One Wire 1 Control */ 219 #define CPCAP_REG_OW2C 0x1220 /* One Wire 2 Command */ 220 #define CPCAP_REG_OW2D 0x1224 /* One Wire 2 Data */ 221 #define CPCAP_REG_OW2I 0x1228 /* One Wire 2 Interrupt */ 222 #define CPCAP_REG_OW2IE 0x122c /* One Wire 2 Interrupt Enable */ [all …]
|
/openbmc/linux/Documentation/devicetree/bindings/iio/temperature/ |
H A D | maxim,max31865.yaml | 22 maxim,3-wire: 25 enables 3-wire RTD connection. Else 2-wire or 4-wire RTD connection. 51 maxim,3-wire;
|
/openbmc/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | intel,ce4100-lapic.yaml | 42 intel,virtual-wire-mode: 47 Virtual Wire Mode - use lapic as virtual wire interrupt delivery mode. 52 mode is configured to virtual wire compatibility mode. 70 intel,virtual-wire-mode;
|
/openbmc/linux/arch/sh/mm/ |
H A D | tlb-urb.c | 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() 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
|
/openbmc/qemu/qapi/ |
H A D | introspect.json | 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 46 # QMP wire ABI, and therefore not returned by this command. 86 # names, type names are not part of the wire ABI. Consequently, 116 # @json-type: the JSON type used for this type on the wire. 168 # Values of this type are JSON string on the wire. 199 # Values of this type are JSON array on the wire. 222 # Values of this type are JSON object on the wire. 277 # members' wire encoding is distinct, see 280 # On the wire, this can be any of the members.
|
/openbmc/linux/Documentation/devicetree/bindings/display/panel/ |
H A D | tpo,tpg110.yaml | 17 and other properties, and has a control interface over 3WIRE 39 protocol is not I2C but 3WIRE SPI. 61 spi-3wire: true 72 - spi-3wire 87 spi-3wire;
|
/openbmc/linux/drivers/w1/ |
H A D | Makefile | 3 # Makefile for the Dallas's 1-wire bus. 6 obj-$(CONFIG_W1) += wire.o 7 wire-objs := w1.o w1_int.o w1_family.o w1_netlink.o w1_io.o
|
H A D | Kconfig | 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.
|
/openbmc/linux/arch/sh/include/mach-common/mach/ |
H A D | highlander.h | 62 #define PA_SMCR (PA_BCR+0x0600) /* 2-wire Serial control */ 63 #define PA_SMSMADR (PA_BCR+0x0602) /* 2-wire Serial Slave control */ 64 #define PA_SMMR (PA_BCR+0x0604) /* 2-wire Serial Mode control */ 65 #define PA_SMSADR1 (PA_BCR+0x0606) /* 2-wire Serial Address1 control */ 66 #define PA_SMTRDR1 (PA_BCR+0x0646) /* 2-wire Serial Data1 control */ 114 #define PA_SMCR (PA_BCR+0x0500) /* 2-wire Serial control */ 115 #define PA_SMSMADR (PA_BCR+0x0502) /* 2-wire Serial Slave control */ 116 #define PA_SMMR (PA_BCR+0x0504) /* 2-wire Serial Mode control */ 117 #define PA_SMSADR1 (PA_BCR+0x0506) /* 2-wire Serial Address1 control */ 118 #define PA_SMTRDR1 (PA_BCR+0x0546) /* 2-wire Serial Data1 control */
|
/openbmc/linux/drivers/iio/common/st_sensors/ |
H A D | st_sensors_spi.c | 33 * st_sensors_is_spi_3_wire() - check if SPI 3-wire mode has been selected 36 * Return: true if SPI 3-wire mode is selected, false otherwise. 43 if (device_property_read_bool(dev, "spi-3wire")) in st_sensors_is_spi_3_wire() 54 * st_sensors_configure_spi_3_wire() - configure SPI 3-wire if needed
|
/openbmc/linux/Documentation/devicetree/bindings/input/touchscreen/ |
H A D | ti,am3359-tsc.yaml | 17 description: Wires refer to application modes i.e. 4/5/8 wire touchscreen 36 ti,wire-config: 63 - ti,wire-config 74 ti,wire-config = <0x00 0x11 0x22 0x33>;
|
/openbmc/linux/Documentation/devicetree/bindings/sound/ |
H A D | awinic,aw8738.yaml | 14 (set using one-wire pulse control). The mode configures the speaker-guard 26 GPIO used for one-wire pulse control. The pin is typically called SHDN 32 description: Operation mode (number of pulses for one-wire pulse control)
|
/openbmc/linux/Documentation/devicetree/bindings/spi/ |
H A D | icpdas-lp8841-spi-rtc.txt | 28 - spi-3wire: The master itself has only 3 wire. It cannor work in 50 spi-3wire;
|