From: dirk.behme@gmail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: clock framework: Don't disable a clock already enabled by boot loader?
Date: Sat, 25 May 2013 09:16:44 +0200 [thread overview]
Message-ID: <51A0655C.4020309@gmail.com> (raw)
In-Reply-To: <20130525065434.GA7782@S2101-09.ap.freescale.net>
Am 25.05.2013 08:54, schrieb Shawn Guo:
> On Sat, May 25, 2013 at 07:59:45AM +0200, Dirk Behme wrote:
>> Hmm, but what's the best way to set a flag in
>>
>> https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/mach-imx/clk-imx6q.c
>>
>> ?
>>
>> In mx6q_clocks_init() there doesn't seem to be an explicit interface
>> to set the flags?
>>
>> I'm not sure if
>>
>> clk[xxx]->flags |= CLK_IGNORE_UNUSED;
>>
>> is the way to go?
>>
> Commit 1e43525 (clk: add clk_ignore_unused option to keep boot clocks
> on) introduced an option "clk_ignore_unused" for bypassing
> clk_disable_unused() call.
Yes, I know ;) But this is slightly different: In the end it disables
the complete clk_disable_unused() call, i.e. for all unused clocks.
I'd like to set the flag CLK_IGNORE_UNUSED for just one clock. I.e. I
want to set a flag for an i.MX6 clock, and I want to set it only for
one clock.
What's the preferred way to do this?
Best regards
Dirk
next prev parent reply other threads:[~2013-05-25 7:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 12:44 clock framework: Don't disable a clock already enabled by boot loader? Dirk Behme
2013-05-24 23:00 ` Sascha Hauer
2013-05-25 5:59 ` Dirk Behme
2013-05-25 6:54 ` Shawn Guo
2013-05-25 7:16 ` Dirk Behme [this message]
2013-05-25 11:17 ` Shawn Guo
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=51A0655C.4020309@gmail.com \
--to=dirk.behme@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).