Re: [PATCH 2/2] [RFC] base: soc: Allow early registration of a single SoC device

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Arnd,

On Mon, Mar 13, 2017 at 2:06 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote:
> On Mon, Mar 13, 2017 at 1:46 PM, Geert Uytterhoeven
> <geert@xxxxxxxxxxxxxx> wrote:
>> On Mon, Mar 13, 2017 at 1:41 PM, Arnd Bergmann <arnd@xxxxxxxx> wrote:
>>> On Thu, Mar 9, 2017 at 7:18 PM, Geert Uytterhoeven
>>> I'd prefer to not have to do the early registration at all and have fewer
>>> special cases. Can you list a specific example that requires this?
>>
>> The specific example is the Renesas R-Car SYSC driver, which manages PM
>> Domains and thus needs to be initialized from an early_initcall.
>
> Ok, and what prevents us from using information in DT to detect which
> variant we have? Is this a case of absolutely having to know the exact
> hardware revision at the time of initialization, or is it just to simplify the
> implementation of the SYSC driver?

The former.
Preproduction versions of R-Car H3 have an additional power area, which no
longer exists on H3 ES2.0.

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@xxxxxxxxxxxxxx

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds



[Index of Archives]     [Linux Samsung SOC]     [Linux Wireless]     [Linux Kernel]     [ATH6KL]     [Linux Bluetooth]     [Linux Netdev]     [Kernel Newbies]     [IDE]     [Security]     [Git]     [Netfilter]     [Bugtraq]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux ATA RAID]     [Samba]     [Device Mapper]

  Powered by Linux