Re: [PATCH] of/address: Don't throw errors on absent ranges properties

2014-11-20 Thread Benjamin Herrenschmidt
On Wed, 2014-11-19 at 10:31 +, 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 > dif

Re: [PATCH] of/address: Don't throw errors on absent ranges properties

2014-11-19 Thread Grant Likely
On Wed, 19 Nov 2014 13:32:31 +1100 , Benjamin Herrenschmidt wrote: > On Tue, 2014-11-18 at 16:57 +, Grant Likely wrote: > > On Fri, 14 Nov 2014 17:58:23 +1100 > > , Benjamin Herrenschmidt > > wrote: > > > The core always tries to translate any "reg" property to construct the > > > platform

Re: [PATCH] of/address: Don't throw errors on absent ranges properties

2014-11-18 Thread Benjamin Herrenschmidt
On Tue, 2014-11-18 at 16:57 +, Grant Likely wrote: > On Fri, 14 Nov 2014 17:58:23 +1100 > , Benjamin Herrenschmidt > wrote: > > The core always tries to translate any "reg" property to construct the > > platform > > device names. This results in a pile of "OF: no ranges; cannot translate" >

Re: [PATCH] of/address: Don't throw errors on absent ranges properties

2014-11-18 Thread Grant Likely
On Fri, 14 Nov 2014 17:58:23 +1100 , Benjamin Herrenschmidt wrote: > The core always tries to translate any "reg" property to construct the > platform > device names. This results in a pile of "OF: no ranges; cannot translate" > errors > in dmesg whenever we expose things like i2c devices that

[PATCH] of/address: Don't throw errors on absent ranges properties

2014-11-13 Thread Benjamin Herrenschmidt
The core always tries to translate any "reg" property to construct the platform device names. This results in a pile of "OF: no ranges; cannot translate" errors in dmesg whenever we expose things like i2c devices that cannot directly translate to the MMIO space. Turn this into a pr_debug instead