From: Saravana Kannan <skannan@codeaurora.org>
To: Tomasz Figa <tomasz.figa@gmail.com>
Cc: Rahul Sharma <rahul.sharma@samsung.com>,
kgene.kim@samsung.com, devicetree-discuss@lists.ozlabs.org,
joshi@samsung.com, inki.dae@samsung.com,
linux-samsung-soc@vger.kernel.org, s.nawrocki@samsung.com,
r.sh.open@gmail.com
Subject: Re: [RFC 2/2] clk: samsung: add exynos5250 composite clock for hdmi
Date: Mon, 20 May 2013 13:02:57 -0700 [thread overview]
Message-ID: <519A8171.3040003@codeaurora.org> (raw)
In-Reply-To: <5956307.B4Gm3xbmhh@flatron>
On 05/20/2013 11:57 AM, Tomasz Figa wrote:
> Hi Rahul,
>
> On Monday 20 of May 2013 19:47:08 Rahul Sharma wrote:
>> HDMI driver needs to change the parent of sclk_hdmi clock to
>> sclk_pixel or to sclk_hdmiphy, depends on the status of hdmiphy.
>> sclk_hdmi which is gate clock doesn't support the set_parent
>> operation.
>
> Wouldn't it be better to simply allow calling clk_set_parent() on gate
> clocks and propagate parent change to nearest mux, just like it is done
> with clk_set_rate()?
>
> It wouldn't require any SoC-specific composite clocks and keep the nice
> property of the clock tree, which is built from basic, generic clock
> blocks that nicely correspond to blocks shown in the documentation.
>
> We had discussed this already at SRPOL and got to the conclusion that it's
> a step backwards, making the clock driver more complex, because each
> composite block would have to be described using a structure with many
> fields. In addition there are many special cases, for which the composite
> scheme wouldn't work anyway and they would end up with simple clocks
> attached after the composite block, defeating the purpose of your patch.
>
+1 to all these comments.
-Saravana
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
hosted by The Linux Foundation
next prev parent reply other threads:[~2013-05-20 20:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-20 14:17 [RFC 0/2] clk: samsung: add composite clocks Rahul Sharma
2013-05-20 14:14 ` Heiko Stübner
2013-05-20 18:19 ` Rahul Sharma
2013-05-20 18:54 ` Heiko Stübner
2013-05-20 14:17 ` [RFC 1/2] clk: samsung: add support for " Rahul Sharma
2013-05-20 14:17 ` [RFC 2/2] clk: samsung: add exynos5250 composite clock for hdmi Rahul Sharma
2013-05-20 18:57 ` Tomasz Figa
2013-05-20 20:02 ` Saravana Kannan [this message]
2013-05-21 4:12 ` Rahul Sharma
2013-05-21 23:15 ` Tomasz Figa
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=519A8171.3040003@codeaurora.org \
--to=skannan@codeaurora.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=inki.dae@samsung.com \
--cc=joshi@samsung.com \
--cc=kgene.kim@samsung.com \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=r.sh.open@gmail.com \
--cc=rahul.sharma@samsung.com \
--cc=s.nawrocki@samsung.com \
--cc=tomasz.figa@gmail.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).