Clock settings

Lars-Peter Clausen lars at metafoo.de
Mon Nov 9 03:17:39 EST 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Florian Fainelli wrote:
> Hi Lars, Bas,
>
> Le dimanche 8 novembre 2009 21:01:42, Lars-Peter Clausen a écrit :
>>> It's probably a good idea to stop everything that isn't used:
>>> IPU (or is it used?), UHC, CIM, SADC, SSI, I2C, UART1.  Not
>>> sure how much power it saves, but it doesn't bring any gain.
>>> :-)
>> Yup. Clock managment is currently less then optimal. The question
>> is whether the kernel or the bootloader should decide which clock
>> to disable? I think the best would be to disable everything non
>> essential in the bootloader and if a kernel driver needs a clock
>> it should enable it.
>
> That's the way to go. You might want to have a look at the Linux
> CLK API to do that along with clk_enable/clk_disable in drivers.
> ARM is a good example of that.
Actually, I already implemented the clock management through the CLK
api some time ago but it's not yet used by any driver yet :/

- - Lars
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkr30CMACgkQBX4mSR26RiNQfACeL8M26J8NXOVfxAwdUidTJghv
eVYAn1iURreYEq6I9/TfoIm1G14VuNu/
=Q8Y3
-----END PGP SIGNATURE-----





More information about the discussion mailing list


interactive