Searched full:i2c4 (Results 1 – 25 of 353) sorted by relevance
12345678910>>...15
| /kernel/linux/linux-5.10/arch/arm/boot/dts/ |
| D | uniphier-pinctrl.dtsi | 104 pinctrl_i2c4: i2c4 {
105 groups = "i2c4";
106 function = "i2c4";
|
| D | r8a7794-alt.dts | 190 * I2C4 is routed to EXIO connector B, pins 73 (SCL) + 74 (SDA).
195 i2c-parent = <&i2c4>, <&gpioi2c4>;
274 i2c4_pins: i2c4 {
275 groups = "i2c4";
276 function = "i2c4";
402 &i2c4 {
|
| D | twl4030_omap3.dtsi | 25 * If your board is not using the I2C4 pins with twl4030, then don't include
27 * pins we need to configure I2C4, or else use the legacy sys_nvmode1 and
|
| D | uniphier-pxs2-vodka.dts | 24 i2c4 = &i2c4;
|
| D | uniphier-pxs2-gentil.dts | 26 i2c4 = &i2c4;
|
| D | uniphier-ld6b-ref.dts | 30 i2c4 = &i2c4;
|
| D | r8a77470-iwg23s-sbc.dts | 142 &i2c4 {
191 i2c4_pins: i2c4 {
193 function = "i2c4";
|
| D | ste-dbx5x0-pinctrl.dtsi | 206 * Activating I2C4 will conflict with UART1 about the same pins so do not
207 * enable I2C4 and UART1 at the same time.
209 i2c4 {
212 function = "i2c4";
|
| D | r8a7793-gose.dts | 427 * I2C4 is routed to EXIO connector E, pins 37 (SCL) + 39 (SDA).
432 i2c-parent = <&i2c4>, <&gpioi2c4>;
479 i2c4_pins: i2c4 {
481 function = "i2c4";
751 &i2c4 {
|
| D | imx6sx-udoo-neo-extended.dts | 20 &i2c4 { /* Onboard Motion sensors */
|
| D | r8a7791-koelsch.dts | 448 * I2C4 is routed to EXIO connector E, pins 37 (SCL) + 39 (SDA).
453 i2c-parent = <&i2c4>, <&gpioi2c4>;
505 i2c4_pins: i2c4 {
507 function = "i2c4";
776 &i2c4 {
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/socionext/ |
| D | uniphier-ld11-ref.dts | 30 i2c4 = &i2c4;
|
| D | uniphier-ld20-ref.dts | 30 i2c4 = &i2c4;
|
| D | uniphier-ld20-global.dts | 31 i2c4 = &i2c4;
|
| D | uniphier-ld20-akebi96.dts | 32 i2c4 = &i2c4;
|
| D | uniphier-ld11-global.dts | 31 i2c4 = &i2c4;
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/toshiba/ |
| D | tmpv7708_pins.dtsi | 68 i2c4_pins: i2c4-pins {
69 function = "i2c4";
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/pinctrl/ |
| D | cirrus,lochnagar.yaml | 117 i2c2-sda, i2c3-scl, i2c3-sda, i2c4-scl, i2c4-sda,
145 i2c2-scl, i2c2-sda, i2c3-scl, i2c3-sda, i2c4-scl,
146 i2c4-sda, spdif-aif, psia1, psia1-bclk, psia1-lrclk,
|
| /kernel/linux/linux-5.10/arch/mips/boot/dts/ingenic/ |
| D | ci20.dts | 282 &i2c4 {
454 pins_i2c4: i2c4 {
455 function = "i2c4";
456 groups = "i2c4-data-e";
|
| /kernel/linux/linux-5.10/arch/arm/mach-omap2/ |
| D | vc.c | 353 * By default let's use I2C4 signaling for retention idle in omap3_vc_init_pmic_signaling()
399 * retention signaled over I2C4, so we can keep voltsetup2 as 0.
400 * And the oscillator is not shut off over I2C4, so no need to
407 /* Configure PRWDM_POWER_OFF over I2C4 */ in omap3_set_i2c_timings()
410 /* Configure PRWDM_POWER_RET over I2C4 */ in omap3_set_i2c_timings()
762 * Mode Is Enabled on I2C Interface Dedicated for Smart Reflex (I2C4)". in omap_vc_i2c_init()
763 * Otherwise I2C4 eventually leads into about 23mW extra power being in omap_vc_i2c_init()
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/freescale/ |
| D | imx8mq-zii-ultra-zest.dts | 15 &i2c4 {
|
| /kernel/linux/linux-5.10/drivers/pinctrl/visconti/ |
| D | pinctrl-tmpv7700.c | 119 VISCONTI_PINS(i2c4, 16, 17);
168 VISCONTI_PIN_GROUP(i2c4, REG_PINMUX4, GENMASK(7, 0), 0x00000077),
218 VISCONTI_GROUPS(i2c4, "i2c4_grp");
251 VISCONTI_PIN_FUNCTION(i2c4),
|
| /kernel/linux/linux-5.10/arch/arm64/boot/dts/renesas/ |
| D | salvator-x.dtsi | 19 &i2c4 {
|
| D | salvator-xs.dtsi | 19 &i2c4 {
|
| /kernel/linux/linux-5.10/Documentation/devicetree/bindings/gpio/ |
| D | gpio-lp3943.txt | 12 &i2c4 {
|
12345678910>>...15