From: Stephen Boyd <sboyd@kernel.org>
To: Frank Oltmanns <frank@oltmanns.dev>,
Michael Turquette <mturquette@baylibre.com>
Cc: A.s. Dong <aisheng.dong@nxp.com>, Abel Vesa <abelvesa@kernel.org>,
Fabio Estevam <festevam@gmail.com>,
linux-arm-kernel@lists.infradead.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, NXP Linux Team <linux-imx@nxp.com>,
Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Sascha Hauer <s.hauer@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Elaine Zhang <zhangqing@rock-chips.com>
Subject: Re: [PATCH v5 0/2] clk: fractional-divider: Improve approximation when zero based and export
Date: Wed, 19 Jul 2023 15:12:47 -0700 [thread overview]
Message-ID: <0aeac8a80da719c2c3b7301668e0c59e.sboyd@kernel.org> (raw)
In-Reply-To: <874jm3lzce.fsf@oltmanns.dev>
Quoting Frank Oltmanns (2023-07-17 01:24:49)
> Hi,
>
> On 2023-06-17 at 15:10:39 +0200, Frank Oltmanns <frank@oltmanns.dev> wrote:
> > The fractional divider approximation does not utilize the full available
> > range for clocks that are flagged CLK_FRAC_DIVIDER_ZERO_BASED. This
> > patchset aims to fix that.
> >
> > It also adds test cases for the edge cases of fractional divider clocks
> > with and without the CLK_FRAC_DIVIDER_ZERO_BASED flag to highlight the
> > changes.
> >
> > Finally, it also exports clk_fractional_divider_general_approximation so
> > that the test cases (but also other users like rockchip clk driver) can
> > be compiled as a module.
> >
> > Unfortunately, I have no boards to test this patch. So all we have are
> > the unit tests. It seems the only user of this flag in mainline is
> > drivers/clk/imx/clk-composite-7ulp.c, therefore I'm cc-ing
> > get_maintainers.pl --git-blame -f drivers/clk/imx/clk-composite-7ulp.c
> > in the hopes of a wider audience.
>
> Are there remarks or questions on this patchset? Anything that needs to
> be improved?
>
I haven't taken a look yet. You sent this almost exactly when I started
a weeks long trip with minimal network access.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-07-19 22:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-17 13:10 [PATCH v5 0/2] clk: fractional-divider: Improve approximation when zero based and export Frank Oltmanns
2023-06-17 13:10 ` Frank Oltmanns
2023-06-17 13:10 ` [PATCH v5 1/2] " Frank Oltmanns
2023-06-17 13:10 ` Frank Oltmanns
2023-10-12 22:40 ` Stephen Boyd
2023-06-17 13:10 ` [PATCH v5 2/2] clk: fractional-divider: tests: Add test suite for edge cases Frank Oltmanns
2023-06-17 13:10 ` Frank Oltmanns
2023-10-12 22:40 ` Stephen Boyd
2023-07-17 8:24 ` [PATCH v5 0/2] clk: fractional-divider: Improve approximation when zero based and export Frank Oltmanns
2023-07-17 8:24 ` Frank Oltmanns
2023-07-19 22:12 ` Stephen Boyd [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=0aeac8a80da719c2c3b7301668e0c59e.sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=abelvesa@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=festevam@gmail.com \
--cc=frank@oltmanns.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=zhangqing@rock-chips.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 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.