From: Ying.Liu@freescale.com (Liu Ying)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/3] refactor some ldb related clocks
Date: Wed, 21 Aug 2013 12:12:19 +0800 [thread overview]
Message-ID: <52143E23.9080203@freescale.com> (raw)
In-Reply-To: <20130821015939.GD30533@S2101-09.ap.freescale.net>
On 08/21/2013 09:59 AM, Shawn Guo wrote:
> Hi Ying,
>
> On Tue, Aug 20, 2013 at 06:08:48PM +0800, Liu Ying wrote:
>>> While I admit to having introduced the combination of 1/3.5 fixed
>>> divider and configurable 1/1,1/2 divder clocks to describe this
>>> fractional divider for the reasons you state, I think the correct
>>> solution would be to improve the table divider to support fractional
>>> values and get rid of the virtual ldb_di<n>_div_3_5 clocks, not
>>> introduce more virtual clocks.
>>
>> Yes, it's good to support fractional values for the table divider(not sure if there is any plan for this).
>> I see there is something similar in 'include/linux/sh_clk.h'.
>
> Yeah, I agree with Philipp on improving table divider to support
> fractional values. Would you like to work on that?
>
> Shawn
>
I don't have a plan to work on that now.
Liu Ying
prev parent reply other threads:[~2013-08-21 4:12 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-20 8:38 [PATCH 0/3] refactor some ldb related clocks Liu Ying
2013-08-20 8:38 ` [PATCH 1/3] ARM: imx6q: " Liu Ying
2013-08-20 15:40 ` Fabio Estevam
2013-08-20 21:18 ` Mike Turquette
2013-08-21 1:40 ` Shawn Guo
2013-08-21 4:20 ` Liu Ying
2013-08-20 8:38 ` [PATCH 2/3] ARM: dts: imx6q/imx6dl: add necessary clocks for ldb node Liu Ying
2013-08-20 8:38 ` [PATCH 3/3] staging: drm/imx: ldb: correct the ldb di clock trees Liu Ying
2013-08-20 9:43 ` [PATCH 0/3] refactor some ldb related clocks Philipp Zabel
2013-08-20 10:08 ` Liu Ying
2013-08-21 1:59 ` Shawn Guo
2013-08-21 4:12 ` Liu Ying [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=52143E23.9080203@freescale.com \
--to=ying.liu@freescale.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).