From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@codeaurora.org>,
DRI mailing list <dri-devel@lists.freedesktop.org>,
Andy Yan <andy.yan@rock-chips.com>,
Vladimir Zapolskiy <vladimir_zapolskiy@mentor.com>
Subject: Re: Question regarding clocks in the DW-HDMI DT bindings
Date: Fri, 25 Nov 2016 15:25 +0200 [thread overview]
Message-ID: <1543509.CFZUmxu4GH@avalon> (raw)
In-Reply-To: <CAOMZO5CgUm39E1hhLrs5SX9ALMj9BGiRKaY874exNWoQhH2AWQ@mail.gmail.com>
Hi Fabio,
On Friday 25 Nov 2016 10:43:04 Fabio Estevam wrote:
> On Thu, Nov 24, 2016 at 9:26 PM, Laurent Pinchart wrote:
> > Another question I have about the bus clock (CC'ing the devicetree mailing
> > list as well as the clock maintainers) is whether it should be made
> > optional. The clock is obviously mandatory from a hardware point of view
> > (given that APB is a synchronous bus and thus requires a clock), but in
> > some SoCs (specifically for the Renesas SoCs) that clock is always on and
> > can't be controlled. We already omit bus clocks in DT for most IP cores
> > when the clock can never be controlled (and we also omit a bunch of other
> > clocks that we don't even know exist), so it could make sense to make the
> > clock optional. Otherwise there would be runtime overhead trying to handle
> > a clock that can't be controlled.
>
> What if you register the clock as a "dummy" clock instead?
In that case I can as well specify the correct clock. My point was that, for
clocks that we know are always on, specifying them in DT will lead to runtime
overhead (registration of the clock, lookup, runtime handling, ...) that we
could as well avoid. I think the question has a broader scope than just the
dw-hdmi driver, hence the widened audience in CC.
--
Regards,
Laurent Pinchart
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-11-25 13:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2778019.JJI4Lz6scm@avalon>
[not found] ` <CAOMZO5CZ-c=1zos=6ovY9Tfkz-UeUq0c1sUQ_Fa8t-TjW6k6hw@mail.gmail.com>
[not found] ` <831329ae-1c16-07ba-3eca-95f6ff8dbae2@mentor.com>
2016-11-24 23:26 ` Question regarding clocks in the DW-HDMI DT bindings Laurent Pinchart
2016-11-25 2:56 ` Andy Yan
2016-11-25 15:22 ` Laurent Pinchart
2016-11-25 15:29 ` Fabio Estevam
2016-11-25 15:56 ` Laurent Pinchart
[not found] ` <CAOMZO5CJTu7jzCb-iVLe2wt8VjyzWq-oYaC2Jw34V8SgaqrGkw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-12-03 17:16 ` Laurent Pinchart
2016-12-03 21:10 ` Vladimir Zapolskiy
2016-12-05 6:52 ` Laurent Pinchart
2016-11-28 21:56 ` Michael Turquette
[not found] ` <CAEG3pNDtMY+Pf1_w6vQEswaMVZ=jOC69R749jSFwB2NiU8r58Q-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-29 6:04 ` Laurent Pinchart
2016-11-29 6:27 ` Michael Turquette
[not found] ` <CAEG3pNCTH5YUjO8m-jd1rfRRKRus7c39W4rYK56c6NdfQsOcyA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-11-29 9:18 ` Laurent Pinchart
2016-11-25 12:43 ` Fabio Estevam
2016-11-25 13:25 ` Laurent Pinchart [this message]
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=1543509.CFZUmxu4GH@avalon \
--to=laurent.pinchart@ideasonboard.com \
--cc=andy.yan@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=festevam@gmail.com \
--cc=mturquette@baylibre.com \
--cc=sboyd@codeaurora.org \
--cc=vladimir_zapolskiy@mentor.com \
/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).