-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'i2c-embedded/for-next' of git://git.pengutronix.de/git/…
…wsa/linux Pull i2c-embedded changes from Wolfram Sang: - CBUS driver (an I2C variant) - continued rework of the omap driver - s3c2410 gets lots of fixes and gains pinctrl support - at91 gains DMA support - the GPIO muxer gains devicetree probing - typical fixes and additions all over * 'i2c-embedded/for-next' of git://git.pengutronix.de/git/wsa/linux: (45 commits) i2c: omap: Remove the OMAP_I2C_FLAG_RESET_REGS_POSTIDLE flag i2c: at91: add dma support i2c: at91: change struct members indentation i2c: at91: fix compilation warning i2c: mxs: Do not disable the I2C SMBus quick mode i2c: mxs: Handle i2c DMA failure properly i2c: s3c2410: Remove recently introduced performance overheads i2c: ocores: Move grlib set/get functions into #ifdef CONFIG_OF block i2c: s3c2410: Add fix for i2c suspend/resume i2c: s3c2410: Fix code to free gpios i2c: i2c-cbus-gpio: introduce driver i2c: ocores: Add support for the GRLIB port of the controller and use function pointers for getreg and setreg functions i2c: ocores: Add irq support for sparc i2c: omap: Move the remove constraint ARM: dts: cfa10049: Add the i2c muxer buses to the CFA-10049 i2c: s3c2410: do not special case HDMIPHY stuck bus detection i2c: s3c2410: use exponential back off while polling for bus idle i2c: s3c2410: do not generate STOP for QUIRK_HDMIPHY i2c: s3c2410: grab adapter lock while changing i2c clock i2c: s3c2410: Add support for pinctrl ...
- Loading branch information
Showing
27 changed files
with
1,480 additions
and
359 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,27 @@ | ||
Device tree bindings for i2c-cbus-gpio driver | ||
|
||
Required properties: | ||
- compatible = "i2c-cbus-gpio"; | ||
- gpios: clk, dat, sel | ||
- #address-cells = <1>; | ||
- #size-cells = <0>; | ||
|
||
Optional properties: | ||
- child nodes conforming to i2c bus binding | ||
|
||
Example: | ||
|
||
i2c@0 { | ||
compatible = "i2c-cbus-gpio"; | ||
gpios = <&gpio 66 0 /* clk */ | ||
&gpio 65 0 /* dat */ | ||
&gpio 64 0 /* sel */ | ||
>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
retu-mfd: retu@1 { | ||
compatible = "retu-mfd"; | ||
reg = <0x1>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,81 @@ | ||
GPIO-based I2C Bus Mux | ||
|
||
This binding describes an I2C bus multiplexer that uses GPIOs to | ||
route the I2C signals. | ||
|
||
+-----+ +-----+ | ||
| dev | | dev | | ||
+------------+ +-----+ +-----+ | ||
| SoC | | | | ||
| | /--------+--------+ | ||
| +------+ | +------+ child bus A, on GPIO value set to 0 | ||
| | I2C |-|--| Mux | | ||
| +------+ | +--+---+ child bus B, on GPIO value set to 1 | ||
| | | \----------+--------+--------+ | ||
| +------+ | | | | | | ||
| | GPIO |-|-----+ +-----+ +-----+ +-----+ | ||
| +------+ | | dev | | dev | | dev | | ||
+------------+ +-----+ +-----+ +-----+ | ||
|
||
Required properties: | ||
- compatible: i2c-mux-gpio | ||
- i2c-parent: The phandle of the I2C bus that this multiplexer's master-side | ||
port is connected to. | ||
- mux-gpios: list of gpios used to control the muxer | ||
* Standard I2C mux properties. See mux.txt in this directory. | ||
* I2C child bus nodes. See mux.txt in this directory. | ||
|
||
Optional properties: | ||
- idle-state: value to set the muxer to when idle. When no value is | ||
given, it defaults to the last value used. | ||
|
||
For each i2c child node, an I2C child bus will be created. They will | ||
be numbered based on their order in the device tree. | ||
|
||
Whenever an access is made to a device on a child bus, the value set | ||
in the revelant node's reg property will be output using the list of | ||
GPIOs, the first in the list holding the least-significant value. | ||
|
||
If an idle state is defined, using the idle-state (optional) property, | ||
whenever an access is not being made to a device on a child bus, the | ||
GPIOs will be set according to the idle value. | ||
|
||
If an idle state is not defined, the most recently used value will be | ||
left programmed into hardware whenever no access is being made to a | ||
device on a child bus. | ||
|
||
Example: | ||
i2cmux { | ||
compatible = "i2c-mux-gpio"; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
mux-gpios = <&gpio1 22 0 &gpio1 23 0>; | ||
i2c-parent = <&i2c1>; | ||
|
||
i2c@1 { | ||
reg = <1>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
ssd1307: oled@3c { | ||
compatible = "solomon,ssd1307fb-i2c"; | ||
reg = <0x3c>; | ||
pwms = <&pwm 4 3000>; | ||
reset-gpios = <&gpio2 7 1>; | ||
reset-active-low; | ||
}; | ||
}; | ||
|
||
i2c@3 { | ||
reg = <3>; | ||
#address-cells = <1>; | ||
#size-cells = <0>; | ||
|
||
pca9555: pca9555@20 { | ||
compatible = "nxp,pca9555"; | ||
gpio-controller; | ||
#gpio-cells = <2>; | ||
reg = <0x20>; | ||
}; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.