Am Donnerstag, 11. September 2014, 16:12:58 schrieb Wolfram Sang: > On Thu, Sep 11, 2014 at 02:17:16PM +0200, Marc Dietrich wrote: > > > + reg = <0x64>; > > > > we had some discussions in the past how to represent i2c master devices in > > device tree. The outcome was to use to a special representation to > > distinguish them from slave devices, e.g. something like reg = <0x1 > > 0x64>, where the 0x1 would mean "master" device (0x0 -> slave). If > > nothing is added, then it's also slave. The adapter address cell would > > also need to be changed if this extension is used. > > Please don't change the reg-layout which is around since forever. > It will break all existing devicetrees. NAK.
it won't break existing device trees. It would only need to be extended for systems where the adapter uses master and slave modes (or if you add a master device to the i2c client list). So you need to change the device tree anyway. All other setups can continue to use a single reg. Thinking more about it, are there any i2c clients parsing the reg property directly? In this case I would agree, otherwise, only i2c core needs some update - right? Marc > > An alternative would be to use a special property (e.g. slave address), > > but > > that would encode the same value twice (or even three times). > > As said, if all breaks we handle it at runtime. > > Thanks, > > Wolfram
signature.asc
Description: This is a digitally signed message part.
