* Ilya Yanok <ya...@emcraft.com> [111121 15:46]:
> Hi Tony,
> 
> On 19.11.2011 04:36, Tony Lindgren wrote:
> >> Well, it already boots with DT actually. Did you mean booting with DT
> >> and board-generic? I have to admit I don't know how to proceed here:
> > 
> > Good to hear you're already playing with it. Yes, let's work on making
> > all the boards work with DT and board-generic..
> 
> Hm, do you think it's absolutely necessary to make everybody work with
> board-generic? It will require a lot of additional bindings to get rid
> of all machine-specific code. I've just thought that on PowerPC we don't
> have such strict rules: if some boards are really similar they share
> common machine file but if we need something specific for the new board
> we can create it's own machine file.

Well ideally yes we would remove the board files completely eventually.

But that will take a while, so I can carry your board file in testing-board
branch.
 
> >> board-generic initialize twl4030 which we don't have on our board...
> >> Could you give me some pointer how I'm supposed to handle this?
> > 
> > .. we should only initialize twl4030/twl6030 if the DT compatible flag
> > for it is set. But we're still missing the DT bindings for those :(
> > 
> > For now, maybe try to fix the twl4030 probe so it won't do anything
> > unless the I2C device is found?
> 
> That turned to be not such a big problem. Device is not present so we
> have tons of error messages but somehow it works.
> 
> The bigger problem is that we have different regulator chip attached.
> How am I supposed to register supplies/consumers data with it? Does
> anybody working on DT bindings for the regulator framework?

Rajendra has posted some regulator DT patches. I believe they have
a dependency to the deferred probe patches in many cases though.

Regards,

Tony
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to