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