Hi,
On Fri, Sep 20, 2013 at 9:08 AM, Nishanth Menon n...@ti.com wrote:
An alternative approach may be to (for all SoCs):
1. define every SoC entry - ti,omap3430 ti,omap3630...
2. have a generic omap3_init which uses if
(of_machine_is_compatible(ti,omap3630))
to invoke the appropriate
Add generic machine which can handle inits for omap3630.
Currently beagle-xm would matchup with ti,omap3 which invokes
omap3430_init_early instead of omap3630_init_early
This defeats the purpose of having SoC specific init_early handlers,
example: clock nodes are not the same between 3430 and
Hi,
On Fri, Sep 20, 2013 at 09:19:02AM -0700, Olof Johansson wrote:
On Fri, Sep 20, 2013 at 9:08 AM, Nishanth Menon n...@ti.com wrote:
An alternative approach may be to (for all SoCs):
1. define every SoC entry - ti,omap3430 ti,omap3630...
2. have a generic omap3_init which uses if
On Fri, Sep 20, 2013 at 9:23 AM, Felipe Balbi ba...@ti.com wrote:
Hi,
On Fri, Sep 20, 2013 at 09:19:02AM -0700, Olof Johansson wrote:
On Fri, Sep 20, 2013 at 9:08 AM, Nishanth Menon n...@ti.com wrote:
An alternative approach may be to (for all SoCs):
1. define every SoC entry - ti,omap3430
Hi,
On Fri, Sep 20, 2013 at 10:16:48AM -0700, Olof Johansson wrote:
On Fri, Sep 20, 2013 at 09:19:02AM -0700, Olof Johansson wrote:
On Fri, Sep 20, 2013 at 9:08 AM, Nishanth Menon n...@ti.com wrote:
An alternative approach may be to (for all SoCs):
1. define every SoC entry -
On 09/20/2013 12:42 PM, Felipe Balbi wrote:
Hi,
On Fri, Sep 20, 2013 at 10:16:48AM -0700, Olof Johansson wrote:
On Fri, Sep 20, 2013 at 09:19:02AM -0700, Olof Johansson wrote:
On Fri, Sep 20, 2013 at 9:08 AM, Nishanth Menon n...@ti.com wrote:
An alternative approach may be to (for all
