Home
last modified time | relevance | path

Searched refs:hooked (Results 1 – 27 of 27) sorted by relevance

/linux-4.1.27/Documentation/devicetree/bindings/power/
Drockchip-io-domain.txt9 - If the regulator hooked up to a pin like SDMMC0_VDD is 3.3V then
10 bit 7 of GRF_IO_VSEL needs to be 0. If the regulator hooked up to
15 hooked up to the pins.
/linux-4.1.27/drivers/staging/iio/meter/
DKconfig63 Say Y here if you have ADE7854/58/68/78 hooked to an I2C bus.
73 Say Y here if you have ADE7854/58/68/78 hooked to a SPI bus.
/linux-4.1.27/Documentation/security/
DLSM.txt5 various security checks to be hooked by new kernel extensions. The name
/linux-4.1.27/Documentation/devicetree/bindings/interrupt-controller/
Dbrcm,bcm7120-l2-intc.txt4 is hooked to a parent interrupt controller: e.g: ARM GIC for ARM-based
/linux-4.1.27/drivers/input/misc/
DKconfig60 Say Y here if you have AD7142/AD7147 hooked to an I2C bus.
70 Say Y here if you have AD7142/AD7147 hooked to a SPI bus.
91 acceleration sensor hooked to an I2C bus.
265 hooked to an I2C bus.
675 Say Y here if you have ADXL345/6 hooked to an I2C bus.
685 Say Y here if you have ADXL345/6 hooked to a SPI bus.
/linux-4.1.27/Documentation/sound/alsa/soc/
Djack.txt68 These are all hooked together by the machine driver depending on the
/linux-4.1.27/arch/arm/boot/dts/
Drk3288-evb.dtsi139 disable-wp; /* wp not hooked up */
Drk3288-popmetal.dts119 disable-wp; /* wp not hooked up */
/linux-4.1.27/drivers/misc/
DKconfig38 Say Y here if you have a digital potentiometers hooked to an I2C bus.
47 Say Y here if you have a digital potentiometers hooked to an SPI bus.
442 sensor hooked to an I2C bus.
454 sensor hooked to an SPI bus.
/linux-4.1.27/Documentation/devicetree/bindings/mmc/
Dsynopsys-dw-mshc.txt33 we'd assume that the write protect is hooked up directly to the
/linux-4.1.27/Documentation/networking/
Dieee802154.txt49 Those types of devices require different approach to be hooked into Linux kernel.
/linux-4.1.27/Documentation/x86/
Dearlyprintk.txt55 wired such that the EHCI debug controller is hooked up to the
/linux-4.1.27/Documentation/hid/
Dhid-transport.txt176 - RESET: Used by I2C-HID, not hooked up in HID core.
177 - SET_POWER: Used by I2C-HID, not hooked up in HID core.
/linux-4.1.27/drivers/iio/light/
DKconfig92 hooked to an I2C bus.
/linux-4.1.27/drivers/usb/phy/
DKconfig89 are hooked to this driver through platform_data structure.
/linux-4.1.27/Documentation/trace/
Dmmiotrace.txt102 calling one of the ioremap_*() functions. Mmiotrace is hooked into the
/linux-4.1.27/Documentation/
Drtc.txt29 same functionality. For example, not every RTC is hooked up to an
/linux-4.1.27/drivers/input/touchscreen/
DKconfig77 Say Y here if you have AD7879-1/AD7889-1 hooked to an I2C bus.
86 Say Y here if you have AD7879-1/AD7889-1 hooked to a SPI bus.
/linux-4.1.27/drivers/net/ethernet/qlogic/qlge/
Dqlge.h1980 u32 hooked; member
Dqlge_dbg.c1634 DUMP_QDEV_ARRAY(qdev, "%d", intr_context, i, hooked); in ql_dump_qdev()
Dqlge_main.c3536 if (intr_context->hooked) { in ql_free_irq()
3600 intr_context->hooked = 1; in ql_request_irq()
/linux-4.1.27/Documentation/blockdev/
Dparide.txt372 clues, then please make sure that only one drive is hooked to your system,
/linux-4.1.27/Documentation/mtd/
Dnand_ecc.txt10 Bad! I was hooked.
/linux-4.1.27/Documentation/vm/
Dnuma_memory_policy.txt117 shmem segments were never "hooked up" to the shared policy support.
/linux-4.1.27/Documentation/spi/
Dspi-summary316 certainly includes SPI devices hooked up through the card connectors!
/linux-4.1.27/Documentation/power/
Ddevices.txt377 GPIO signals hooked up to a switch or other external hardware, and
/linux-4.1.27/Documentation/video4linux/
Dvivid.txt874 as if a cable was hooked up between the output and input connector. So video