mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Richard Fitzgerald <rf@opensource.cirrus.com>
To: Brian Masney <bmasney@redhat.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org, robh@kernel.org,
	krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-clk@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH v6 2/3] clk: cs2600: Add Fractional-N clock driver
Date: Mon, 20 Jul 2026 10:03:48 +0100	[thread overview]
Message-ID: <49ad7c68-0d5a-4ccb-b769-9bf3af611518@opensource.cirrus.com> (raw)
In-Reply-To: <ak0iEAJsZJOkvkX1@redhat.com>

On 07/07/2026 4:58 pm, Brian Masney wrote:
> Hi Richard,
> 
> Thanks for the patch.
> 
> On Tue, Jun 30, 2026 at 04:55:48PM +0100, Richard Fitzgerald wrote:
>> From: Paul Handrigan <paulha@opensource.cirrus.com>
>>
>> Add driver for the Cirrus Logic CS2600 fractional-N clock synthesizer
>> and multiplier.
>>

<SNIP>

>> +
>> +DEFINE_GUARD(cs2600_unfreeze, struct cs2600 *,
>> +	     cs2600_clear_freeze(_T), cs2600_set_freeze(_T))
> 
> Can you go through the Sashiko output for this series?

I sent an email responding to those, but it was reply-all to the Sashiko
bot email and I didn't notice that Sashiko had stripped a lot of the
original email recipients.

My responses to Sashiko are here:
https://lore.kernel.org/all/dc5a1c0c-8c6b-4f4b-90f1-e9c83a8b91b8@opensource.cirrus.com/


> https://sashiko.dev/#/message/20260630161121.020FB1F000E9%40smtp.kernel.org
> 
> The clear/set inverted looks questionable to me. If this is expected,
> then a comment clarifying why should be added.

I'll add a comment in the next version explaining the order.

> [snip]
> 
>> +static int cs2600_clk_register(struct cs2600 *cs2600)
>> +{
>> +	static const char *parent_names[2];
> 
> I wouldn't worry too about about Sashiko asking about multiple driver
> instances for this section, unless you think it will eventually be used
> in that way.

Trivial to fix though. That 'static' shouldn't be there.

>> +	const struct clk_hw *out_clocks_parent;
>> +	struct clk_init_data init[ARRAY_SIZE(cs2600->hw)] = { };
>> +	int ret, i, n, input_num = 0;
>> +	const char *names[ARRAY_SIZE(cs2600_clks)];
> 
> Reverse Christmas tree order.

Will do.

> I can do a more thorough review once you go through the Sashiko results.
> 
> Brian
> 


  reply	other threads:[~2026-07-20  9:04 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-30 15:55 [PATCH v6 0/3] Cirrus Logic CS2600 clock device Richard Fitzgerald
2026-06-30 15:55 ` [PATCH v6 1/3] dt-bindings: clock: cs2600: Add support for the CS2600 Richard Fitzgerald
2026-07-01  6:48   ` Krzysztof Kozlowski
2026-07-01  8:59     ` Richard Fitzgerald
2026-06-30 15:55 ` [PATCH v6 2/3] clk: cs2600: Add Fractional-N clock driver Richard Fitzgerald
2026-06-30 16:59   ` Uwe Kleine-König
2026-07-07 15:58   ` Brian Masney
2026-07-20  9:03     ` Richard Fitzgerald [this message]
2026-06-30 15:55 ` [PATCH v6 3/3] clk: cs2600: Add KUnit test for CS2600 driver Richard Fitzgerald
2026-07-02 19:24   ` Julian Braha

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=49ad7c68-0d5a-4ccb-b769-9bf3af611518@opensource.cirrus.com \
    --to=rf@opensource.cirrus.com \
    --cc=bmasney@redhat.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mturquette@baylibre.com \
    --cc=patches@opensource.cirrus.com \
    --cc=robh@kernel.org \
    --cc=sboyd@kernel.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

all inboxes | Powered by JetHome®