On Wed, 2014-11-19 at 10:31 +0000, Grant Likely wrote: > was my explanation being full of crap. It's my i2c > > _controller_ which is a platform device, and is on the xscom bus > which > > isn't directly MMIO translatable. > > Okay, that makes more sense, but if xscom is a different bus with > different access methods, then why is it using platform_bus_type? I > would expect it to have it's own bus_type and container for struct > device. There is no point really. It's not really a bus we expose as such to Linux (mostly the FW uses it) though we use the xscom nodes as chip nodes. We do expose selected devices we pick from underneath xscom such as the LPC bus and the i2c controllers as platform devices which then use FW interfaces to perform the actual LPC or i2c accesses. Creating a dedicated bus type would be completely pointless. The FW itself uses what's there more intensively. > > The patch still stands :) > > Indeed, I merged it yesterday. :) Thanks! Cheers, Ben. -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
