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