From: r.sh.open@gmail.com (Rahul Sharma)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 5/5] clk/exynos5420: assign sclk_pixel id to pixel clock divider
Date: Sat, 24 Aug 2013 12:09:40 +0530 [thread overview]
Message-ID: <CAPdUM4O75Qcv6DD7NNRUG2vf+hs7bs0sFX+MAReS6JH_9B7rhQ@mail.gmail.com> (raw)
In-Reply-To: <3550203.JkdqaguvYB@flatron>
On 24 August 2013 01:32, Tomasz Figa <tomasz.figa@gmail.com> wrote:
> Hi Rahul,
>
> On Friday 23 of August 2013 12:27:58 Rahul Sharma wrote:
>> sclk_pixel is used to represent pixel clock divider on all exynos
>> SoCs not as a gate clock. It is queried in driver to pass as the
>> parent to hdmi clock while switching between parents. A new ID can
>> be asssigned Pixel gate clock which is currently not in use. Pixel
>> clock gate is default 'on'.
>
> This doesn't sound like a correct assumption, especially if you recall how
> common clock framework works - it disables any unclaimed clock
> automatically. Also we might want to support gating from power management
> reasons.
>
> IMHO you should simply export the dout_hdmi_pixel clock, keeping the
> original sclk_pixel exported as well.
>
Hi Tomasz,
Yea correct. I will export the divider clock and let hdmi driver use that
to pass as parent opf mout_pixel.
Regards,
Rahul Sharma.
> Best regards,
> Tomasz
>
prev parent reply other threads:[~2013-08-24 6:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-23 6:57 [PATCH v2 0/5] clk/exynos5420: add clocks for hdmi subsystem Rahul Sharma
2013-08-23 6:57 ` [PATCH v2 1/5] clk/exynos5420: add sclk_hdmiphy to the list of special clocks Rahul Sharma
2013-08-23 6:57 ` [PATCH v2 2/5] clk/exynos5420: add gate clock for mixer sysmmu Rahul Sharma
2013-08-23 6:57 ` [PATCH v2 3/5] clk/exynos5420: fix the order of parents of hdmi mux Rahul Sharma
2013-08-23 6:57 ` [PATCH v2 4/5] clk/exynos5420: add hdmi mux to change parents in hdmi driver Rahul Sharma
2013-08-23 6:57 ` [PATCH v2 5/5] clk/exynos5420: assign sclk_pixel id to pixel clock divider Rahul Sharma
2013-08-23 20:02 ` Tomasz Figa
2013-08-24 6:39 ` Rahul Sharma [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=CAPdUM4O75Qcv6DD7NNRUG2vf+hs7bs0sFX+MAReS6JH_9B7rhQ@mail.gmail.com \
--to=r.sh.open@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).