From: "Uwe Kleine-König" <u.kleine-koenig@baylibre.com>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: bmasney@redhat.com, sboyd@kernel.org, mturquette@baylibre.com,
robh@kernel.org, krzk+dt@kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH v7 2/3] clk: cs2600: Add Fractional-N clock driver
Date: Fri, 7 Aug 2026 22:55:08 +0200 [thread overview]
Message-ID: <anZEtfI1tFz8Xc00@monoceros> (raw)
In-Reply-To: <20260807155406.752721-3-rf@opensource.cirrus.com>
[-- Attachment #1: Type: text/plain, Size: 1830 bytes --]
On Fri, Aug 07, 2026 at 04:54:05PM +0100, Richard Fitzgerald wrote:
> +#include <dt-bindings/clock/cirrus,cs2600-clock.h>
> +#include <linux/bitfield.h>
> +#include <linux/clk.h>
> +#include <linux/clk-provider.h>
> +#include <linux/container_of.h>
> +#include <linux/delay.h>
> +#include <linux/i2c.h>
> +#include <linux/math.h>
> +#include <linux/math64.h>
> +#include <linux/mod_devicetable.h>
Please drop <linux/mod_devicetable.h>. You can rely on <linux/i2c.h> to
provide struct i2c_device_id and of_device_id.
(Background of this request is that <linux/mod_devicetable.h> should go
away soon.)
> +#include <linux/module.h>
> +#include <linux/of.h>
> +#include <linux/regmap.h>
> +#include <linux/string.h>
> +
> [...]
> +static const struct of_device_id cs2600_of_match[] = {
> + { .compatible = "cirrus,cs2600", },
No comma before a closing } in the same line please.
> + {}
{ } is the most common way to write the terminator.
> +};
> +MODULE_DEVICE_TABLE(of, cs2600_of_match);
> +
> +static const struct i2c_device_id cs2600_id[] = {
> + { .name = "cs2600", },
> + {}
> +};
Here the same please.
> +MODULE_DEVICE_TABLE(i2c, cs2600_id);
> +
> +static struct i2c_driver cs2600_driver = {
> + .driver = {
> + .name = "cs2600",
> + .of_match_table = cs2600_of_match,
> + },
> + .probe = cs2600_i2c_probe,
> + .id_table = cs2600_id,
I'm not a fan of aligning `=`s as it gets inconsistent over time. Here
it's wrong already from the start. Only 2 out of 3 members of the
i2c_driver use alignment and .driver doesn't. If you ask me, just use a
single space before each `=`.
> +};
> +
> +module_i2c_driver(cs2600_driver);
No empty line before module_i2c_driver() please.
> +
> +MODULE_DESCRIPTION("CS2600 clock driver");
> +MODULE_AUTHOR("Paul Handrigan <paulha@opensource.cirrus.com>");
> +MODULE_LICENSE("GPL");
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-08-07 20:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-07 15:54 [PATCH v7 0/3] Cirrus Logic CS2600 clock device Richard Fitzgerald
2026-08-07 15:54 ` [PATCH v7 1/3] dt-bindings: clock: cs2600: Add support for the CS2600 Richard Fitzgerald
2026-08-07 15:54 ` [PATCH v7 2/3] clk: cs2600: Add Fractional-N clock driver Richard Fitzgerald
2026-08-07 16:07 ` sashiko-bot
2026-08-07 20:55 ` Uwe Kleine-König [this message]
2026-08-07 15:54 ` [PATCH v7 3/3] clk: cs2600: Add KUnit test for CS2600 driver Richard Fitzgerald
2026-08-07 16:10 ` sashiko-bot
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=anZEtfI1tFz8Xc00@monoceros \
--to=u.kleine-koenig@baylibre.com \
--cc=bmasney@redhat.com \
--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=rf@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