From: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
To: Michael Turquette <mturquette@linaro.org>,
Sergej Sawazki <ce3a@gmx.de>,
sboyd@codeaurora.org, mwelling@ieee.org, moinejf@free.fr
Cc: linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] clk: si5351: Multisynth 6-7 fixes
Date: Fri, 15 May 2015 11:25:19 +0200 [thread overview]
Message-ID: <5555BB7F.2090602@gmail.com> (raw)
In-Reply-To: <20150512233834.16410.23856@quantum>
On 13.05.2015 01:38, Michael Turquette wrote:
> Quoting Sergej Sawazki (2015-05-11 01:44:19)
>> The second synthesis stage in the Si5351 clock generator consists of six
>> *fractional* multisynth dividers (MS0 .. MS5) and two *even-integer*
>> dividers (MS6 and MS7). The current si5351 driver implementation does
>> not handle MS6 and MS7 correctly, this leads to wrong rates on output 6
>> and 7. This patch series fixes that.
>>
>> Patch 1 fixes the divider calculation for multisynth 6 and 7.
>>
>> Patch 2 fixes the divider re-calculation for multisynth 6 and 7.
>>
>> Info: Base on branch 'clk-fixes'.
>>
>> Sergej Sawazki (2):
>> clk: si5351: fix .round_rate for multisynth 6-7
>> clk: si5351: fix .recalc_rate for multisynth 6-7
>
> Applied both patches to clk-next.
Sergei,
next time please _always_ keep the version numbering on your patches,
IIRC it should be v3 and it should include the changelog history.
Also, I sent a Reviewed-by for at least the .round_rate callback
patch. It would be nice if you'd include that into resends of your
patch to help Mike keeping track of those.
Sebastian
next prev parent reply other threads:[~2015-05-15 9:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-11 8:44 [PATCH 0/2] clk: si5351: Multisynth 6-7 fixes Sergej Sawazki
2015-05-12 23:38 ` Michael Turquette
2015-05-12 23:38 ` Michael Turquette
2015-05-15 9:25 ` Sebastian Hesselbarth [this message]
2015-05-16 10:13 ` Sergej Sawazki
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=5555BB7F.2090602@gmail.com \
--to=sebastian.hesselbarth@gmail.com \
--cc=ce3a@gmx.de \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=moinejf@free.fr \
--cc=mturquette@linaro.org \
--cc=mwelling@ieee.org \
--cc=sboyd@codeaurora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.