From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Mike Turquette <mturquette@linaro.org>
Cc: Michal Bachraty <michal.bachraty@streamunlimited.com>,
grant.likely@secretlab.ca, rob.herring@calxeda.com,
rob@landley.net, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] clk: si5351: Add gapless tuning for SI5351 PLL
Date: Fri, 12 Apr 2013 21:24:16 +0200 [thread overview]
Message-ID: <51685F60.9010802@gmail.com> (raw)
In-Reply-To: <20130412183809.6507.27844@quantum>
On 04/12/2013 08:38 PM, Mike Turquette wrote:
> Quoting Michal Bachraty (2013-04-09 01:26:15)
>> For gapless tuning, there is no need for PLL reset and clkout power-down
>> when tuning output. "silabs,gapless-tuning" parameter enables gapless tuning
>> for specific clock output.
>>
>> Signed-off-by: Michal Bachraty<michal.bachraty@streamunlimited.com>
>
> Hi Michal,
>
> This did not apply cleanly on the latest (v8) si5351 clk driver. Can
> you refresh it? I do not plan on taking any more patches for 3.10 after
> 3.9-rc7 drops (likely on Sunday or Monday). So this patch may need to
> wait until after the merge window.
Mike,
I have integrated the above function into clk-si5351 during development
(see clk-si5351 changelog from v6->v7). I think we can drop this patch,
as Michal added his Tested-by to clk-si5351.
Regards,
Sebastian
next prev parent reply other threads:[~2013-04-12 19:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 8:26 [PATCH] clk: si5351: Add gapless tuning for SI5351 PLL Michal Bachraty
2013-04-09 9:25 ` Sebastian Hesselbarth
[not found] ` <CABJ1b_RW=UUxmTrYOsx2wsDm1egs9DL3dWtat0--5kqec9-rQA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2013-04-09 13:49 ` Michal Bachraty
2013-04-12 18:38 ` Mike Turquette
2013-04-12 19:24 ` Sebastian Hesselbarth [this message]
[not found] ` <51685F60.9010802-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-04-14 7:00 ` Mike Turquette
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=51685F60.9010802@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=michal.bachraty@streamunlimited.com \
--cc=mturquette@linaro.org \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
/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).