summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/i2c/i2c-omap.txt
blob: a425b91af48fb72196ac8ee1c90fba47dde069ec (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
I2C for OMAP platforms

Required properties :
- compatible : Must be
	"ti,omap2420-i2c" for OMAP2420 SoCs
	"ti,omap2430-i2c" for OMAP2430 SoCs
	"ti,omap3-i2c" for OMAP3 SoCs
	"ti,omap4-i2c" for OMAP4+ SoCs
	"ti,am654-i2c", "ti,omap4-i2c" for AM654 SoCs
	"ti,j721e-i2c", "ti,omap4-i2c" for J721E SoCs
	"ti,am64-i2c", "ti,omap4-i2c" for AM64 SoCs
- ti,hwmods : Must be "i2c<n>", n being the instance number (1-based)
- #address-cells = <1>;
- #size-cells = <0>;

Recommended properties :
- clock-frequency : Desired I2C bus clock frequency in Hz. Otherwise
  the default 100 kHz frequency will be used.

Optional properties:
- Child nodes conforming to i2c bus binding

Note: Current implementation will fetch base address, irq and dma
from omap hwmod data base during device registration.
Future plan is to migrate hwmod data base contents into device tree
blob so that, all the required data will be used from device tree dts
file.

Examples :

i2c1: i2c@0 {
    compatible = "ti,omap3-i2c";
    #address-cells = <1>;
    #size-cells = <0>;
    ti,hwmods = "i2c1";
    clock-frequency = <400000>;
};