[PATCH] ARM: shmobile: compile drivers/sh for CONFIG_ARCH_SHMOBILE_MULTI
Geert Uytterhoeven
geert at linux-m68k.org
Tue Mar 11 15:15:04 EDT 2014
Hi Laurent,
On Mon, Jan 20, 2014 at 11:52 PM, Laurent Pinchart
<laurent.pinchart at ideasonboard.com> wrote:
> On Monday 20 January 2014 15:56:43 Mark Brown wrote:
>> On Mon, Jan 20, 2014 at 04:48:10PM +0100, Laurent Pinchart wrote:
>> > The problem isn't as simple as it seems, and more advanced implementations
>> > that would allow listing clocks that should be managed automatically (or
>> > the other way around) would also add another level of complexity. The
>> > required information is platform-dependent, but we currently don't
>> > express it as such in DT.
>>
>> Well, the set of clocks an IP requires will tend to be the same - it's
>> normally just that integrators may have done things like tie them together
>> or decide to spread confusion by renaming them.
>
> That's the problem :-) How should the runtime PM core be given the list of
> clocks it needs to manage ? That information needs to come from somewhere.
Stirring the pot again...
Which clocks a device needs is expressed in DT with CCF.
In the simple case, the runtime PM core can just control them based on
device use.
In the complex case, the driver can regain control using its own pm
callbacks, right?
Probably I'm still missing something, as I haven't had enough exposure to
runtime PM and CCF ;-)
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org
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
More information about the linux-arm-kernel
mailing list