From: tomeu@tomeuvizoso.net (Tomeu Vizoso)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/5] clk: rockchip: add full support for HDMI clock on rk3288
Date: Fri, 22 Jan 2016 15:00:27 +0100 [thread overview]
Message-ID: <CAAObsKCMh3Bk_oNJdLbU2F9b7jrnFZOp2uFR_oPqUoJ3W1gfaQ@mail.gmail.com> (raw)
In-Reply-To: <CAD=FV=VB93wYigRJ8wa8YL6P+Q+-fRokPiCB-Fo1pC_zAdh2oA@mail.gmail.com>
On 21 January 2016 at 21:11, Doug Anderson <dianders@chromium.org> wrote:
> Hi,
>
> On Thu, Jan 21, 2016 at 1:03 AM, Tomeu Vizoso <tomeu@tomeuvizoso.net> wrote:
>> So we have a mechanism for detecting a conflict in the clock
>> hierarchy, and a mechanism to solve it, but we are missing a way for
>> userspace to communicate policy regarding which clocks should be given
>> priority when solving such a conflict?
>
> Hrmmm, I guess it could be userspace that makes the decision. It does
> seem a little odd to force it to userspace in all cases, though. For
> a particular laptop that is designed with a specific panel connected
> up eDP it seems less than ideal to push this into userspace. If the
> kernel could just work in the expected sane way (or at least work that
> way by default) it would be ideal.
Ah, I was wrongly assuming that the kernel didn't have enough
information to make an informed decision in this case, sorry.
Guess the per-user rate limits don't help here because the consumer
with higher priority could work with frequencies other than the ideal.
And we cannot have a consumer listening for PRE_RATE_CHANGE and
aborting unwanted changes or rerouting the ancestors of the clocks of
other consumers because that would be a massive violation of
separation of concerns.
If we were to rearrange the clock topology from within the CCF, then
consumers need to have a way to communicate to the core that they are
more important than other consumers. clk_set_important(clk, true)
could be enough in this case, but would be insufficient in more
complex cases where more than two clocks could use the same PLL.
> If the kernel doesn't try to do anything sane by default then you're
> creating a requirement for everyone's userspace to somehow figure this
> out. Do you expect there to be UI here, or that this would be
> something that would be figured out by the Linux distribution?
> Certainly exposing UI on something like a laptop with a builtin panel
> wouldn't make any sense to me, but it might make sense if you had an
> eval board with different display connectors on it. If there's no UI,
> would the Linux distribution need to somehow identify which board we
> were on and then have a big lookup table about how to configure
> things?
If we don't actually need input from userspace for this use case, I
wouldn't go this way right now, because it seems to me like it could
be a really big timesink for little gain.
Once someone comes with a situation in which feedback from userspace
is really needed, that person can propose such an interface ;)
Regards,
Tomeu
next prev parent reply other threads:[~2016-01-22 14:00 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-04 7:52 [PATCH 0/5] clk: rockchip: add full support for HDMI clock on rk3288 Kever Yang
2014-11-04 7:52 ` [PATCH 1/5] clk: rockchip: add some clock rate into rate table for rk3288 Kever Yang
2014-11-04 7:52 ` [PATCH 3/5] clk: rockchip: introduce the div_ops handling for composite branches Kever Yang
2014-11-04 7:52 ` [PATCH 4/5] clk: rockchip: add the vop_determine_rate for vop dclock Kever Yang
2014-11-04 7:52 ` [PATCH 5/5] clk: rockchip: change DCLK_VOP0 to use new COMPOSITE_DIVOPS Kever Yang
2014-11-06 21:06 ` [PATCH 0/5] clk: rockchip: add full support for HDMI clock on rk3288 Heiko Stübner
2014-11-13 8:52 ` Kever Yang
2014-11-13 22:59 ` Doug Anderson
[not found] ` <20141114014605.25314.49766@quantum>
2014-11-14 8:58 ` Kever Yang
2016-01-19 12:02 ` Tomeu Vizoso
2016-01-20 16:50 ` Doug Anderson
2016-01-21 9:03 ` Tomeu Vizoso
2016-01-21 20:11 ` Doug Anderson
2016-01-22 14:00 ` Tomeu Vizoso [this message]
2016-01-22 17:07 ` Doug Anderson
2016-01-26 8:28 ` Tomeu Vizoso
2016-01-26 16:32 ` Doug Anderson
2016-01-27 10:20 ` Tomeu Vizoso
2016-01-27 16:46 ` Doug Anderson
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=CAAObsKCMh3Bk_oNJdLbU2F9b7jrnFZOp2uFR_oPqUoJ3W1gfaQ@mail.gmail.com \
--to=tomeu@tomeuvizoso.net \
--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).