From: mturquette@linaro.org (Michael Turquette)
To: linux-arm-kernel@lists.infradead.org
Subject: Question about DC-DC frequency handling
Date: Sun, 26 Apr 2015 12:07:29 -0700 [thread overview]
Message-ID: <20150426190729.16410.58019@quantum> (raw)
In-Reply-To: <604104768.496325.1430058690855.JavaMail.open-xchange@oxbaltgw00.schlund.de>
Quoting Stefan Wahren (2015-04-26 07:31:30)
> Hi,
>
> i'm current working on a regulator driver which should be able to change DC-DC
> clock frequency.
>
> Now here is my question. What is the prefered way to implement the clock
> handling?
Fun question. I have a question for you: who are the consumers of this
DC-DC? Do the downstream, consuming devices care about "clock rate" of
your regulator?
I'll hazard a guess that they do not care. DC-DC switching frequency is
an important aspect of power supply design, but switching frequency of a
power supply is not controlled by the clock framework in any example
that I am aware of.
>
> Option A):
>
> The regulator driver handles all internally (select clock source, set
> frequency).
Mark should weigh in on this, but I think option A is correct. Maybe
something like regulator_set_mode could program your switching
frequency?
>
> Option B):
>
> The DC-DC clock domain is implemented in the clock driver and the regulator
> driver uses the clock framework.
The only reason to use the clock framework is if downstream devices will
call clk_get and do something with the rate (e.g. clk_get_rate,
clk_set_rate, clk_enable, clk_disable, etc).
It sounds like your downstream devices will want to enable & disable the
regulator, but probably that's it?
Of course I could be wrong about the DC-DC switching frequency stuff
above, but that's my guess for now.
Regards,
Mike
>
> Best regards
> Stefan
next prev parent reply other threads:[~2015-04-26 19:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 14:31 Question about DC-DC frequency handling Stefan Wahren
2015-04-26 14:31 ` Stefan Wahren
2015-04-26 19:07 ` Michael Turquette [this message]
2015-04-27 20:44 ` Stefan Wahren
2015-04-27 20:44 ` Stefan Wahren
2015-04-27 20:57 ` Mark Brown
2015-04-27 11:01 ` Mark Brown
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=20150426190729.16410.58019@quantum \
--to=mturquette@linaro.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.