From: Dirk Behme <dirk.behme@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] mx6sl: Add initial support for mx6slevk board
Date: Sat, 06 Apr 2013 18:48:24 +0200 [thread overview]
Message-ID: <516051D8.4040508@gmail.com> (raw)
In-Reply-To: <CAOMZO5DQhT9vDcof4T3SuJXumr4Yy8+YSrC+BbvPS03rZz_Vvw@mail.gmail.com>
Am 06.04.2013 18:40, schrieb Fabio Estevam:
> Hi Dirk,
>
> On Sat, Apr 6, 2013 at 1:30 PM, Dirk Behme <dirk.behme@gmail.com> wrote:
>
>> ... but saving power over the whole (kernel) runtime. I might be wrong, but
>> to my understanding the kernel doesn't *disable* unneeded clocks?
>>
>> So it's up to the bootloader to enable only the peripherals (clocks) really
>> needed for booting. And then it's up to the kernel's driver init functions
>> to enable the needed clocks for the subsystem once it's needed.
>>
>> But as I won't use this board I won't care about the power consumption here.
>> If you think it's fine for the use cases of this board to enable all clocks
>> by default, then this shouldn't stop applying this patch.
>
> Ok, understood. I will go through each one of the CCM registers and
> check what clocks can be turned off.
>
> This may take some time though as it needs proper testing.
>
> I suggest that we keep the current clock settings as is, so that the
> board support can reach U-boot, then later I can submit a patch for
> turning off the unneeded clocks.
Sounds like a good plan :)
Thanks
Dirk
P.S.: I would think that the clock settings of the other boards should
be a good starting point to minimize the work. At least if the
SoloLite clocks are not completely different ;)
next prev parent reply other threads:[~2013-04-06 16:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-06 0:55 [U-Boot] [PATCH 1/3] iomux-v3: Place pad control definitions into common file Fabio Estevam
2013-04-06 0:55 ` [U-Boot] [PATCH 2/3] mx6: Add solo-lite variant support Fabio Estevam
2013-04-06 0:55 ` [U-Boot] [PATCH 3/3] mx6sl: Add initial support for mx6slevk board Fabio Estevam
2013-04-06 7:27 ` Dirk Behme
2013-04-06 12:47 ` Fabio Estevam
2013-04-06 13:52 ` Dirk Behme
2013-04-06 14:15 ` Fabio Estevam
2013-04-06 16:30 ` Dirk Behme
2013-04-06 16:40 ` Fabio Estevam
2013-04-06 16:48 ` Dirk Behme [this message]
2013-04-10 6:01 ` Stefano Babic
2013-04-17 8:48 ` Stefano Babic
2013-04-21 17:00 ` Fabio Estevam
2013-04-22 7:51 ` Stefano Babic
2013-04-09 18:20 ` [U-Boot] [PATCH 1/3] iomux-v3: Place pad control definitions into common file Otavio Salvador
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=516051D8.4040508@gmail.com \
--to=dirk.behme@gmail.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox