| /linux-4.4.14/drivers/w1/masters/ |
| D | Kconfig | 2 # 1-wire bus master configuration
5 menu "1-wire Bus Masters"
8 tristate "Matrox G400 transport layer for 1-wire"
11 Say Y here if you want to communicate with your 1-wire devices
18 tristate "DS2490 USB <-> W1 transport layer for 1-wire"
38 tristate "Freescale MXC 1-wire busmaster"
41 Say Y here to enable MXC 1-wire host
44 tristate "Maxim DS1WM 1-wire busmaster"
46 Say Y here to enable the DS1WM 1-wire driver, such as that
51 tristate "GPIO 1-wire busmaster"
[all …]
|
| /linux-4.4.14/drivers/w1/slaves/ |
| D | Kconfig | 2 # 1-wire slaves configuration
5 menu "1-wire Slaves"
10 Say Y here if you want to connect 1-wire thermal sensors to your
11 wire.
16 Say Y here if you want to connect 1-wire
17 simple 64bit memory rom(ds2401/ds2411/ds1990*) to your wire.
22 Say Y here if you want to use a 1-wire
38 Say Y here if you want to use a 1-wire
45 Say Y or M here if you want to use a 1-wire
50 tristate "Counter 1-wire device (DS2423)"
[all …]
|
| /linux-4.4.14/Documentation/w1/masters/ |
| D | omap-hdq | 1 Kernel driver for omap HDQ/1-wire module.
6 HDQ/1-wire controller on the TI OMAP 2430/3430 platforms.
16 Semiconductor 1-Wire protocols. These protocols use a single wire for
23 The controller supports operation in both HDQ and 1-wire mode. The essential
24 difference between the HDQ and 1-wire mode is how the slave device responds to
47 The driver also supports 1-wire mode. In this mode, there is no need to
49 to the bus using SEARCH_ROM procedure. 1-wire mode can be selected by
|
| D | 00-INDEX | 4 - The Maxim/Dallas Semiconductor DS2482 provides 1-wire busses.
10 - HDQ/1-wire module of TI OMAP 2430/3430.
12 - GPIO 1-wire bus master driver.
|
| D | w1-gpio | 10 GPIO 1-wire bus master driver. The driver uses the GPIO API to control the
11 wire and the GPIO pin can be specified using platform data.
|
| D | ds2482 | 19 one (DS2482-100) or eight (DS2482-800) 1-wire busses.
|
| /linux-4.4.14/drivers/w1/ |
| D | Makefile | 5 obj-$(CONFIG_W1) += wire.o
6 wire-objs := w1.o w1_int.o w1_family.o w1_netlink.o w1_io.o
|
| D | Kconfig | 2 tristate "Dallas's 1-wire support"
5 Dallas' 1-wire bus is useful to connect slow 1-pin devices
11 will be called wire.
|
| /linux-4.4.14/Documentation/w1/ |
| D | 00-INDEX | 6 - Individual chips providing 1-wire busses.
8 - The 1-wire (w1) bus
|
| D | w1.generic | 1 The 1-wire (w1) subsystem
3 The 1-wire bus is a simple master-slave bus that communicates via a single
4 signal wire (plus ground, so two wires).
37 Then provided control buffer is being written to the wire.
70 Devices that support the 1-wire natively must provide the ability to write and
|
| /linux-4.4.14/Documentation/devicetree/bindings/w1/ |
| D | omap-hdq.txt | 1 * OMAP HDQ One wire bus master controller
10 - ti,mode: should be "hdq": HDQ mode "1w": one-wire mode.
|
| D | fsl-imx-owire.txt | 1 * Freescale i.MX One wire bus master controller
|
| /linux-4.4.14/Documentation/hwmon/ |
| D | adt7411 | 18 The ADT7411 can use an I2C/SMBus compatible 2-wire interface or an
19 SPI-compatible 4-wire interface. It provides a 10-bit analog to digital
|
| D | mcp3021 | 26 Communication to the MCP3021/MCP3221 is performed using a 2-wire I2C
|
| D | asc7621 | 69 fan types. We can also support pulse-stretched PWM so that 3-wire fans
79 The aSC7621 has a two wire digital interface compatible with SMBus 2.0.
106 - 2-wire, SMBus 2.0 compliant, serial interface
112 - 3 PWM fan speed control outputs for 2-, 3- or 4-wire fans and up to 4 fan
|
| D | lm85 | 52 The LM85 uses the 2-wire interface compatible with the SMBUS 2.0
92 speed of a two wire fan, but the input conditioning circuitry is different
93 for 3-wire and 2-wire mode. For this reason, the 2-wire fan modes are not
|
| D | max31790 | 20 through the I2C interface. The outputs drive "4-wire" fans directly,
|
| D | lm95245 | 20 LM95235 and LM95245 are 11-bit digital temperature sensors with a 2-wire System
|
| D | lm95234 | 20 LM95233 and LM95234 are 11-bit digital temperature sensors with a 2-wire
|
| D | adt7470 | 18 The ADT7470 uses the 2-wire interface compatible with the SMBus 2.0
|
| D | adt7475 | 40 The ADT747x uses the 2-wire interface compatible with the SMBus 2.0
|
| D | w83627ehf | 187 southbridge drives the fans. And the DHG supports SST, a one-wire serial bus.
|
| D | lm93 | 49 The LM93 hardware monitor has a two wire digital interface compatible with
|
| /linux-4.4.14/Documentation/sound/alsa/soc/ |
| D | DAI.txt | 8 AC97 is a five wire interface commonly found on many PC sound cards. It is
22 I2S is a common 4 wire DAI used in HiFi, STB and portable devices. The Tx and
44 PCM is another 4 wire interface, very similar to I2S, which can support a more
|
| /linux-4.4.14/Documentation/devicetree/bindings/input/touchscreen/ |
| D | ti-tsc-adc.txt | 6 ti,wires: Wires refer to application modes i.e. 4/5/8 wire touchscreen
18 ti,wire-config: Different boards could have a different order for
73 ti,wire-config = <0x00 0x11 0x22 0x33>;
|
| /linux-4.4.14/Documentation/devicetree/bindings/spi/ |
| 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.
|
| /linux-4.4.14/Documentation/DocBook/ |
| D | libata.xml.db | 18 API-ata-cable-40wire
19 API-ata-cable-80wire
87 API-ata-is-40wire
88 API-cable-is-40wire
|
| /linux-4.4.14/drivers/infiniband/ulp/iser/ |
| D | iser_memory.c | 379 iser_set_dif_domain(sc, sig_attrs, &sig_attrs->wire); in iser_set_sig_attrs()
380 sig_attrs->wire.sig.dif.bg_type = IB_T10DIF_CRC; in iser_set_sig_attrs()
384 sig_attrs->wire.sig_type = IB_SIG_TYPE_NONE; in iser_set_sig_attrs()
391 iser_set_dif_domain(sc, sig_attrs, &sig_attrs->wire); in iser_set_sig_attrs()
392 sig_attrs->wire.sig.dif.bg_type = IB_T10DIF_CRC; in iser_set_sig_attrs()
|
| /linux-4.4.14/Documentation/devicetree/bindings/media/i2c/ |
| D | mt9m111.txt | 4 array size of 1280H x 1024V. It is programmable through a simple two-wire serial
|
| D | mt9p031.txt | 5 two-wire serial interface.
|
| D | mt9v032.txt | 5 two-wire serial interface.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | gpio.txt | 45 value might be driven, supporting "wire-OR" and similar schemes for the
49 of pins configured as "output", which is very useful in such "wire-OR"
93 This is sometimes called a "wire-AND"; or more practically, from the negative
94 logic (low=true) perspective this is a "wire-OR".
|
| D | drivers-on-gpio.txt | 63 - w1-gpio: drivers/w1/masters/w1-gpio.c is used to drive a one-wire bus using
|
| D | gpio-legacy.txt | 32 value might be driven ... supporting "wire-OR" and similar schemes
36 of pins configured as "output", which is very useful in such "wire-OR"
417 level. This is sometimes called a "wire-AND"; or more practically, from the
418 negative logic (low=true) perspective this is a "wire-OR".
503 like the aforementioned options for input de-glitching and wire-OR output.
|
| /linux-4.4.14/drivers/spmi/ |
| D | Kconfig | 7 SPMI (System Power Management Interface) is a two-wire
|
| /linux-4.4.14/Documentation/spi/ |
| D | spi-lm70llp | 47 Note that since the LM70 uses a "3-wire" variant of SPI, the SI/SO pin
50 pin low. This can't be shared with true SPI devices, but other 3-wire
|
| D | butterfly | 57 of spare parport pins to wire this one up, such as:
|
| D | spi-summary | 8 The "Serial Peripheral Interface" (SPI) is a synchronous four wire serial
50 SPI is only one of the names used by such four-wire protocols, and
61 chips described as using "three wire" signaling: SCK, data, nCSx.
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-via | 33 can actually wire the lines.
|
| /linux-4.4.14/drivers/bluetooth/ |
| D | Kconfig | 126 bool "Three-wire UART (H5) protocol support"
129 The HCI Three-wire UART Transport Layer makes it possible to
131 Three-wire UART Transport Layer assumes that the UART
135 Say Y here to compile support for Three-wire UART protocol.
|
| /linux-4.4.14/Documentation/devicetree/bindings/bus/ |
| D | sunxi-rsb.txt | 3 The RSB controller found on later Allwinner SoCs is an SMBus like 2 wire
|
| /linux-4.4.14/drivers/infiniband/hw/mlx5/ |
| D | qp.c | 2173 struct ib_sig_domain *wire = &sig_attrs->wire; in mlx5_set_bsf() local
2197 switch (sig_attrs->wire.sig_type) { in mlx5_set_bsf()
2201 if (mem->sig.dif.pi_interval == wire->sig.dif.pi_interval && in mlx5_set_bsf()
2202 mem->sig_type == wire->sig_type) { in mlx5_set_bsf()
2205 if (mem->sig.dif.bg_type == wire->sig.dif.bg_type) in mlx5_set_bsf()
2206 basic->wire.copy_byte_mask |= MLX5_CPY_GRD_MASK; in mlx5_set_bsf()
2207 if (mem->sig.dif.app_tag == wire->sig.dif.app_tag) in mlx5_set_bsf()
2208 basic->wire.copy_byte_mask |= MLX5_CPY_APP_MASK; in mlx5_set_bsf()
2209 if (mem->sig.dif.ref_tag == wire->sig.dif.ref_tag) in mlx5_set_bsf()
2210 basic->wire.copy_byte_mask |= MLX5_CPY_REF_MASK; in mlx5_set_bsf()
[all …]
|
| /linux-4.4.14/Documentation/ |
| D | bt8xxgpio.txt | 26 GPIO pin and solder that to some tiny wire. As the chip package really is tiny
|
| D | adding-syscalls.txt | 244 To wire up your new system call for x86 platforms, you need to update the
347 To wire up the x86 architecture of a system call with a compatibility version,
506 - Suggestion from Thomas Gleixner that x86 wire-up should be in a separate
|
| D | 00-INDEX | 219 - directory with info about the I2C bus/protocol (2 wire, kHz speed).
471 - directory with documents regarding the 1-wire (w1) subsystem.
|
| D | unaligned-memory-access.txt | 124 to represent some data that comes in a fixed arrangement 'off the wire'.
|
| /linux-4.4.14/Documentation/arm/SA1100/ |
| D | ADSBitsy | 38 Contact ADS or look through the manual to wire your own. Currently,
|
| D | GraphicsMaster | 48 Contact ADS or look through the manual to wire your own. Currently,
|
| D | GraphicsClient | 92 Contact ADS or look through the manual to wire your own. Currently,
|
| /linux-4.4.14/Documentation/devicetree/bindings/leds/ |
| D | leds-ktd2692.txt | 4 It uses ExpressWire single-wire programming for maximum flexibility.
|
| /linux-4.4.14/Documentation/devicetree/bindings/interrupt-controller/ |
| D | arm,vic.txt | 5 nested or have the outputs wire-OR'd together.
|
| /linux-4.4.14/drivers/video/fbdev/ |
| D | pxa168fb.h | 192 #define CFG_SPI_3W4WB(wire) ((wire) << 1) argument
|
| /linux-4.4.14/arch/arm/ |
| D | Kconfig-nommu | 29 hex 'Hard wire the processor ID'
|
| /linux-4.4.14/arch/arc/boot/dts/ |
| D | axc001.dtsi | 74 * which acts as a wire between MB INTC and CPU INTC.
|
| D | axc003_idu.dtsi | 99 * which acts as a wire between MB INTC and CPU INTC.
|
| /linux-4.4.14/Documentation/i2c/ |
| D | summary | 5 slow two-wire protocol (variable speed, up to 400 kHz), with a high speed
|
| /linux-4.4.14/drivers/staging/lustre/ |
| D | README.txt | 56 Verify data consistency on the wire and in memory as it passes
|
| D | sysfs-fs-lustre | 501 Maximum number of parallel RPCs on the wire to allow on
527 Controls whenever to checksum bulk RPC data over the wire
|
| /linux-4.4.14/drivers/net/ethernet/freescale/ |
| D | Kconfig | 50 an external MII PHY chip or 10 Mbps 7-wire interface
|
| /linux-4.4.14/Documentation/w1/slaves/ |
| D | w1_therm | 56 location of the chip in the 1-wire bus without needing pre-existing
|
| /linux-4.4.14/include/rdma/ |
| D | opa_port_info.h | 422 u8 wire; member
|
| D | ib_verbs.h | 649 struct ib_sig_domain wire; member
|
| /linux-4.4.14/drivers/net/ppp/ |
| D | Kconfig | 43 sent over the wire. The machine at the other end of the PPP link
64 each PPP packet before it is sent over the wire. The machine at the
|
| /linux-4.4.14/Documentation/misc-devices/ |
| D | c2port.txt | 40 however it implements a two wire serial communication protocol (bit
|
| /linux-4.4.14/arch/powerpc/boot/dts/ |
| D | mpc832x_mds.dts | 15 * 2) Solder a wire from U61-21 to P19A-23. P19 is a grid of pins on the board
17 * 3) Solder a wire from U61-22 to P19K-22.
|
| /linux-4.4.14/Documentation/video4linux/bttv/ |
| D | Tuners | 38 3-wire/I2C tuning, 2-band/3-band
|
| /linux-4.4.14/Documentation/scsi/ |
| D | cxgb3i.txt | 31 the TCP segments onto the wire. It handles TCP retransmission if
|
| D | osd.txt | 168 wire. It works very well with current iSCSI transport. iSCSI is currently the
|
| /linux-4.4.14/drivers/auxdisplay/ |
| D | Kconfig | 87 For help about how to wire your LCD to the parallel port,
|
| /linux-4.4.14/Documentation/input/ |
| D | xpad.txt | 93 All generations of Xbox controllers speak USB over the wire.
116 yellow wire unconnected. The other pins have the same order on both
|
| D | joystick-parport.txt | 49 wire is +5V).
87 And the last thing is the NES / SNES data wire. Only that isn't shared and
288 And finally, you connect the Ground wire of the joystick, like done in
|
| /linux-4.4.14/Documentation/devicetree/bindings/powerpc/fsl/ |
| D | mpc5200.txt | 162 - fsl,7-wire-mode - An empty property that specifies the link uses 7-wire
|
| /linux-4.4.14/Documentation/filesystems/nfs/ |
| D | pnfs.txt | 13 The on-the-wire command LAYOUTGET corresponds to struct
|
| D | knfsd-stats.txt | 54 on the wire, this may be either more or less than the number
|
| D | nfs-rdma.txt | 28 wire bandwidth at minimal client CPU) under many workloads. The code passes
|
| /linux-4.4.14/fs/ocfs2/dlm/ |
| D | dlmdomain.c | 790 u32 *wire) in dlm_query_join_packet_to_wire() argument
795 *wire = be32_to_cpu(response.intval); in dlm_query_join_packet_to_wire()
798 static void dlm_query_join_wire_to_packet(u32 wire, in dlm_query_join_wire_to_packet() argument
803 response.intval = cpu_to_be32(wire); in dlm_query_join_wire_to_packet()
|
| /linux-4.4.14/include/linux/mlx5/ |
| D | qp.h | 361 } wire; member
|
| /linux-4.4.14/drivers/isdn/i4l/ |
| D | Kconfig | 54 sent over the wire. The machine at the other end of the PPP link
|
| /linux-4.4.14/Documentation/zh_CN/ |
| D | gpio.txt | 186 函数可以使得模拟接口(译者注:例如 GPIO 模拟 I2C、1-wire 或 SPI)的
|
| /linux-4.4.14/drivers/video/fbdev/mmp/hw/ |
| D | mmp_ctrl.h | 416 #define CFG_SPI_3W4WB(wire) ((wire)<<1) argument
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | trivial-devices.txt | 92 sii,s35390a 2-wire CMOS real-time clock
|
| /linux-4.4.14/Documentation/x86/ |
| D | earlyprintk.txt | 65 to the hardware vendor, because there is no reason not to wire
|
| /linux-4.4.14/Documentation/fb/ |
| D | udlfb.txt | 9 USB wire. That hardware framebuffer is able to drive the VGA, DVI, or HDMI
|
| /linux-4.4.14/Documentation/networking/ |
| D | PLIP.txt | 99 above calculation. It isn't an important issue, unless the wire is faulty,
|
| D | e1000e.txt | 177 packet is sent on the wire within the set amount of time. Proper tuning,
|
| D | spider_net.txt | 118 ad stop. However, RX packets may still continue arriving on the wire.
|
| D | arcnet.txt | 377 2. More than one protocol on the same wire.
470 same physical ARCnet wire. You can picture it like this:
|
| D | switchdev.txt | 284 otherwise there will be duplicate packets on the wire.
|
| D | e1000.txt | 296 packet is sent on the wire within the set amount of time. Proper tuning,
|
| D | ip-sysctl.txt | 1056 local interfaces over the wire and have them accepted properly.
|
| D | arcnet-hardware.txt | 26 types, as far as I'm aware, are not compatible and so you cannot wire a
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | tegra124-nyan.dtsi | 646 * TODO: find a way to wire this up with the USB EHCI
|
| D | am335x-pepper.dts | 515 ti,wire-config = <0x00 0x11 0x22 0x33>;
|
| D | am335x-evmsk.dts | 709 ti,wire-config = <0x00 0x11 0x22 0x33>;
|
| D | am335x-evm.dts | 725 ti,wire-config = <0x00 0x11 0x22 0x33>;
|
| D | tegra124-venice2.dts | 1113 * TODO: find a way to wire this up with the USB EHCI
|
| /linux-4.4.14/arch/xtensa/configs/ |
| D | common_defconfig | 469 # Dallas's 1-wire bus
|
| /linux-4.4.14/Documentation/isdn/ |
| D | README.concap | 51 private purpose over the wire, e.g. ppp does a lot of link level
|
| /linux-4.4.14/Documentation/video4linux/ |
| D | README.pvrusb2 | 29 1a. Low level wire-protocol implementation with the device.
|
| /linux-4.4.14/drivers/infiniband/ulp/isert/ |
| D | ib_isert.c | 2619 isert_set_dif_domain(se_cmd, sig_attrs, &sig_attrs->wire); in isert_set_sig_attrs()
2623 sig_attrs->wire.sig_type = IB_SIG_TYPE_NONE; in isert_set_sig_attrs()
2628 isert_set_dif_domain(se_cmd, sig_attrs, &sig_attrs->wire); in isert_set_sig_attrs()
|
| /linux-4.4.14/Documentation/sound/alsa/ |
| D | Audigy-mixer.txt | 31 I2S - one-way three wire serial bus for digital sound by Philips Semiconductors
|
| D | SB-Live-mixer.txt | 45 I2S - one-way three wire serial bus for digital sound by Philips Semiconductors
|
| /linux-4.4.14/drivers/input/touchscreen/ |
| D | Kconfig | 650 Say Y here if you have 4/5/8 wire touchscreen controller
1091 the on-board provided 4-wire touchscreen driver.
|
| /linux-4.4.14/drivers/leds/ |
| D | Kconfig | 426 LT3593 controller. This controller uses a special one-wire pulse
|
| /linux-4.4.14/drivers/spi/ |
| D | Kconfig | 24 SPI is one of a family of similar protocols using a four wire
|
| /linux-4.4.14/Documentation/filesystems/cifs/ |
| D | CHANGES | 449 to EOPNOTSUPP when server does not support posix acls on the wire. Fix
455 longer UTF-8 strings than the string on the wire was in Unicode. Add workaround
|
| D | README | 480 Unicode on the wire.
|
| /linux-4.4.14/drivers/staging/rdma/hfi1/ |
| D | mad.c | 707 pi->replay_depth.wire = tmp; in __subn_get_opa_portinfo()
|