[PATCH] clkdev: add support to lookup for early platform device

[Magnus Damm]

On Thu, Apr 28, 2011 at 12:20 PM, Jean-Christophe PLAGNIOL-VILLARD
<plagnioj at jcrosoft.com> wrote:
>> > > > >
>> > > > Are you willfully ignoring the init_name handling in
>> > > > early_platform_driver_probe_id() or something?
>> > > >
>> > > > See a636ee7fb35b731ba2b331f6294e809bb6be09c8 for example.
>> > > excatly but the issue is that the slab is not availlable yet
>> > > see 06fe53beb636294587d8e94ef83c06cef07c21fd
>> > > so init_name is still NULL :(
>> > >
>> > This is a non-argument until you demonstrate a use case where we have a
>> > reasonable expectation for the clock framework to be available and the
>> > slab allocator not.
>> >
>> > If you're thinking about the SH earlyprintk case then I suggest you look
>> > at the sh-sci driver to see how we presently deal with the situation
>> > there.
>> the sh-sci driver expect the clock will enable for him
>> which did IIRC Magnus on sh-mobile
>> I do not want to do so
>>
>> I've unfortunatly on at91 I use the early device during the map_io

But so do we on SH-Mobile ARM.

>> so the slab is available and bootmem either
> sorry none of theem is available yet

Sounds like you are aiming to use earlyprintk a little bit too early,
or perhaps your idea of using clocks that early on is what is causing
you trouble?

Why don't you move down your earlyprintk setup to a time when you have
slabs available? Or for clocks, in the sh-sci driver we don't deal
with clocks in the earlyprintk case.

I understand you want output as early as possible, but there is always
going to be a time when you need to hack up some static serial output
code.

/ magnus