i2c-bus@0 twice?
johannes@quad:/proc/device-tree/ht@0,f2000000/pci@8/mac-io@7/i2c@18000$ ls AAPL,address built-in i2c-bus@0 linux,phandle AAPL,address-step compatible interrupt-parent name AAPL,i2c-rate device_type interrupts reg #address-cells i2c-bus@0 linux,device #size-cells
Somewhat odd that i2c-bus@0 exists twice :) Anyone have an explanation?
johannes
Quoted 7 lines · Johannes Berg
johannes@quad:/proc/device-tree/ht@0,f2000000/pci@8/mac-io@7/i2c@18000$ ls AAPL,address built-in i2c-bus@0 linux,phandle AAPL,address-step compatible interrupt-parent name AAPL,i2c-rate device_type interrupts reg #address-cells i2c-bus@0 linux,device #size-cellsSomewhat odd that i2c-bus@0 exists twice :) Anyone have an explanation?
Do you see it twice in OF also?
cheers
Signature · 8 lines
Michael Ellerman IBM OzLabs wwweb: http://michael.ellerman.id.au phone: +61 2 6212 1183 (tie line 70 21183) We do not inherit the earth from our ancestors, we borrow it from our children. - S.M.A.R.T Person
Quoted 7 lines · Johannes Berg
johannes@quad:/proc/device-tree/ht@0,f2000000/pci@8/mac-io@7/i2c@18000$ ls AAPL,address built-in i2c-bus@0 linux,phandle AAPL,address-step compatible interrupt-parent name AAPL,i2c-rate device_type interrupts reg #address-cells i2c-bus@0 linux,device #size-cellsSomewhat odd that i2c-bus@0 exists twice :) Anyone have an explanation?
It's a bug in OF on these machines. We need to workaround that, especially since only one of them contains all the useful infos
Ben