| /linux-4.4.14/drivers/i2c/busses/ |
| D | i2c-acorn.c | 24 #define SCL 0x02 macro
37 u_int ioc_control = ioc_readb(IOC_CONTROL) & ~(SCL | SDA); in ioc_setscl()
41 ones |= SCL; in ioc_setscl()
43 ones &= ~SCL; in ioc_setscl()
52 u_int ioc_control = ioc_readb(IOC_CONTROL) & ~(SCL | SDA); in ioc_setsda()
67 return (ioc_readb(IOC_CONTROL) & SCL) != 0; in ioc_getscl()
91 force_ones = FORCE_ONES | SCL | SDA; in i2c_ioc_init()
|
| D | i2c-versatile.c | 23 #define SCL (1 << 0) macro
43 writel(SCL, i2c->base + (state ? I2C_CONTROLS : I2C_CONTROLC)); in i2c_versatile_setscl()
55 return !!(readl(i2c->base + I2C_CONTROL) & SCL); in i2c_versatile_getscl()
96 writel(SCL | SDA, i2c->base + I2C_CONTROLS); in i2c_versatile_probe()
|
| D | Kconfig | 552 arch-neutral GPIO API to control the SCL and SDA lines.
|
| /linux-4.4.14/drivers/rtc/ |
| D | rtc-rs5c313.c | 74 #define SCL SCSPTR1_SPB0DT macro
96 scsptr1_data = __raw_readb(SCSPTR1) | SCL; /* SCL:H */ in rs5c313_init_port()
117 scsptr1_data &= ~SCL; /* SCL:L */ in rs5c313_write_data()
120 scsptr1_data |= SCL; /* SCL:H */ in rs5c313_write_data()
137 scsptr1_data &= ~SCL; /* SCL:L */ in rs5c313_read_data()
140 scsptr1_data |= SCL; /* SCL:H */ in rs5c313_read_data()
|
| /linux-4.4.14/Documentation/devicetree/bindings/i2c/ |
| D | i2c-rk3x.txt | 23 - clock-frequency : SCL frequency to use (in Hz). If omitted, 100kHz is used.
24 - i2c-scl-rising-time-ns : Number of nanoseconds the SCL signal takes to rise
28 - i2c-scl-falling-time-ns : Number of nanoseconds the SCL signal takes to fall
33 (t(f) in the I2C specification). If not specified we'll use the SCL
|
| D | i2c-s3c2410.txt | 22 - gpios: The order of the gpios should be the following: <SDA, SCL>.
47 &gpd1 3 0 /* SCL */>;
|
| D | i2c-designware.txt | 17 - i2c-scl-falling-time-ns : should contain the SCL falling time in nanoseconds.
|
| D | i2c-st.txt | 17 - st,i2c-min-scl-pulse-width-us : The minimum valid SCL pulse width that is
|
| D | i2c-imx.txt | 17 - scl-gpios: specify the gpio related to SCL pin
|
| /linux-4.4.14/arch/arm/boot/dts/ |
| D | ste-href-family-pinctrl.dtsi | 121 pins = "GPIO147_C15", "GPIO148_B16"; /* SDA/SCL */
128 pins = "GPIO147_C15", "GPIO148_B16"; /* SDA/SCL */
141 pins = "GPIO16_AD3", "GPIO17_AD4"; /* SDA/SCL */
148 pins = "GPIO16_AD3", "GPIO17_AD4"; /* SDA/SCL */
161 pins = "GPIO10_AF5", "GPIO11_AG4"; /* SDA/SCL */
168 pins = "GPIO10_AF5", "GPIO11_AG4"; /* SDA/SCL */
181 pins = "GPIO229_AG7", "GPIO230_AF7"; /* SDA/SCL */
188 pins = "GPIO229_AG7", "GPIO230_AF7"; /* SDA/SCL */
205 pins = "GPIO4_AH6", "GPIO5_AG6"; /* SDA/SCL */
212 pins = "GPIO4_AH6", "GPIO5_AG6"; /* SDA/SCL */
|
| D | tegra30-apalis-eval.dts | 72 * GEN1_I2C: I2C1_SDA/SCL on MXM3 pin 209/211 (e.g. RTC on carrier
94 * CAM_I2C: I2C3_SDA/SCL on MXM3 pin 201/203 (e.g. camera sensor on
102 /* DDC: I2C2_SDA/SCL on MXM3 pin 205/207 (e.g. display EDID) */
|
| D | omap4-sdp-es23plus.dts | 10 /* SDP boards with 4430 ES2.3+ or 4460 have external pullups on SCL & SDA */
|
| D | omap4-panda-a4.dts | 13 /* Pandaboard Rev A4+ have external pullups on SCL & SDA */
|
| D | omap5-igep0050.dts | 51 <&gpio7 2 0>, /* 194, SCL */
|
| D | omap4-panda-es.dts | 34 /* PandaboardES has external pullups on SCL & SDA */
|
| D | at91-foxg20.dts | 121 AT91_PIOA 24 AT91_PERIPH_A AT91_PINCTRL_MULTI_DRIVE>; /* TWCK (SCL), open drain */
|
| D | tegra30-colibri-eval-v3.dts | 49 * GEN1_I2C: I2C_SDA/SCL on SODIMM pin 194/196 (e.g. RTC on carrier
|
| D | ste-href-ab8505.dtsi | 144 /* Modem I2C setup (SCL and SDA pins) */
|
| D | ste-href-ab8500.dtsi | 358 /* Modem I2C setup (SCL and SDA pins) */
|
| /linux-4.4.14/Documentation/i2c/muxes/ |
| D | i2c-mux-gpio | 14 | | SCL/SDA | |-------------- | |
23 SCL/SDA of the master I2C bus is multiplexed to bus segment 1..M
|
| /linux-4.4.14/Documentation/devicetree/bindings/iio/temperature/ |
| D | mlx90614.txt | 15 is no need for a GPIO driving the SCL line. If no GPIO is given, power
|
| /linux-4.4.14/Documentation/i2c/busses/ |
| D | i2c-parport | 53 SCL ----------x--------o |-----------x------------------- pin 2
89 - Obviously you cannot read SCL (so it's not really standard-compliant).
104 SCL ----------x--------x--| o---x------------------------ pin 15
|
| /linux-4.4.14/drivers/staging/panel/ |
| D | Kconfig | 160 (SDA/SCL), while parallel ones use 2 or 3 wires for the control signals
211 int "Parallel port pin number & polarity connected to the LCD SCL signal (-17...17) "
216 LCD 'SCL' signal has been connected. It can be :
222 Default for the 'SCL' pin in custom profile is '1' (STROBE).
|
| /linux-4.4.14/drivers/scsi/ |
| D | nsp32.c | 3257 nsp32_prom_set(data, SCL, 1); in nsp32_prom_start()
3262 nsp32_prom_set(data, SCL, 0); in nsp32_prom_start()
3268 nsp32_prom_set(data, SCL, 1); in nsp32_prom_stop()
3272 nsp32_prom_set(data, SCL, 0); in nsp32_prom_stop()
3279 nsp32_prom_set(data, SCL, 1 ); in nsp32_prom_write_bit()
3280 nsp32_prom_set(data, SCL, 0 ); in nsp32_prom_write_bit()
3289 nsp32_prom_set(data, SCL, 1); in nsp32_prom_read_bit()
3293 nsp32_prom_set(data, SCL, 0); in nsp32_prom_read_bit()
|
| D | nsp32.h | 401 # define SCL BIT(0) macro
|
| /linux-4.4.14/Documentation/devicetree/bindings/pinctrl/ |
| D | fsl,imx7d-pinctrl.txt | 58 any of the iomux controllers. For example the I2C1 IP can use SCL pad from
|
| /linux-4.4.14/Documentation/i2c/ |
| D | i2c-protocol | 60 These messages may still fail to SCL lo->hi timeout.
|
| /linux-4.4.14/Documentation/gpio/ |
| D | drivers-on-gpio.txt | 52 (two wires, SDA and SCL lines) by hammering (bitbang) two GPIO lines. It will
|
| /linux-4.4.14/arch/cris/arch-v10/drivers/ |
| D | Kconfig | 462 int "I2C SCL bit number"
|
| /linux-4.4.14/Documentation/ |
| D | pinctrl.txt | 439 be used as an I2C port (these are just two pins: SCL, SDA). Needless to say,
|