Thread (24 messages) 24 messages, 9 authors, 2014-10-22

use IORESOURCE_REG resource type for non-translatable addresses in DT

From: Bjorn Andersson <hidden>
Date: 2014-08-27 18:24:55
Also in: linux-arm-msm, linux-devicetree, lkml

On Tue, Jul 29, 2014 at 11:06 PM, Stephen Boyd [off-list ref] wrote:
On 07/29, Rob Herring wrote:
[..]
quoted
You might as well do of_property_read_u32 in the below example.
Fair enough. The example is probably too simple. Things are
sometimes slightly more complicated and a simple
of_property_read_u32() isn't going to work in the case of
multiple reg values or when reg-names is in play.
But do we have such cases in the Qualcomm PMICs?

The only case I've hit so far is for gpios and mpps, where it feels
like reg should be base, size and not simply base reg of first gpio -
but that's a different thing.

Also, so far it seems like most drivers just code the base address in
the driver, as we have very specific compatibles.


How about we stop trying so hard to make this "perfect" and just merge
something close to Josh's original proposal and ignore this problem?
Currently all we're doing is delaying any possibility of getting
drivers for the individual blocks merged.
If we have the dt bindings require the reg to be there, we can discuss
and change this all we want later!

Regards,
Bjorn
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help