1*c66ec88fSEmmanuel VadotI2C for OMAP platforms 2*c66ec88fSEmmanuel Vadot 3*c66ec88fSEmmanuel VadotRequired properties : 4*c66ec88fSEmmanuel Vadot- compatible : Must be 5*c66ec88fSEmmanuel Vadot "ti,omap2420-i2c" for OMAP2420 SoCs 6*c66ec88fSEmmanuel Vadot "ti,omap2430-i2c" for OMAP2430 SoCs 7*c66ec88fSEmmanuel Vadot "ti,omap3-i2c" for OMAP3 SoCs 8*c66ec88fSEmmanuel Vadot "ti,omap4-i2c" for OMAP4+ SoCs 9*c66ec88fSEmmanuel Vadot "ti,am654-i2c", "ti,omap4-i2c" for AM654 SoCs 10*c66ec88fSEmmanuel Vadot "ti,j721e-i2c", "ti,omap4-i2c" for J721E SoCs 11*c66ec88fSEmmanuel Vadot- ti,hwmods : Must be "i2c<n>", n being the instance number (1-based) 12*c66ec88fSEmmanuel Vadot- #address-cells = <1>; 13*c66ec88fSEmmanuel Vadot- #size-cells = <0>; 14*c66ec88fSEmmanuel Vadot 15*c66ec88fSEmmanuel VadotRecommended properties : 16*c66ec88fSEmmanuel Vadot- clock-frequency : Desired I2C bus clock frequency in Hz. Otherwise 17*c66ec88fSEmmanuel Vadot the default 100 kHz frequency will be used. 18*c66ec88fSEmmanuel Vadot 19*c66ec88fSEmmanuel VadotOptional properties: 20*c66ec88fSEmmanuel Vadot- Child nodes conforming to i2c bus binding 21*c66ec88fSEmmanuel Vadot 22*c66ec88fSEmmanuel VadotNote: Current implementation will fetch base address, irq and dma 23*c66ec88fSEmmanuel Vadotfrom omap hwmod data base during device registration. 24*c66ec88fSEmmanuel VadotFuture plan is to migrate hwmod data base contents into device tree 25*c66ec88fSEmmanuel Vadotblob so that, all the required data will be used from device tree dts 26*c66ec88fSEmmanuel Vadotfile. 27*c66ec88fSEmmanuel Vadot 28*c66ec88fSEmmanuel VadotExamples : 29*c66ec88fSEmmanuel Vadot 30*c66ec88fSEmmanuel Vadoti2c1: i2c@0 { 31*c66ec88fSEmmanuel Vadot compatible = "ti,omap3-i2c"; 32*c66ec88fSEmmanuel Vadot #address-cells = <1>; 33*c66ec88fSEmmanuel Vadot #size-cells = <0>; 34*c66ec88fSEmmanuel Vadot ti,hwmods = "i2c1"; 35*c66ec88fSEmmanuel Vadot clock-frequency = <400000>; 36*c66ec88fSEmmanuel Vadot}; 37