From: sashiko-bot@kernel.org
To: "Kevin Jia" <kjia@nexthop.ai>
Cc: devicetree@vger.kernel.org, linux-hwmon@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/3] hwmon: (fs1603) Add driver for TDK FS160x and FS1006 uPOL converters
Date: Mon, 19 Oct 2026 18:52:35 +0000 [thread overview]
Message-ID: <sashiko-outbox-178111@kernel.org> (raw)
In-Reply-To: <20261019-fs1603-v1-3-8adf972386c1@nexthop.ai>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] hwmon: (fs1603) positional initializers in struct i2c_device_id fs1603_id
--
commit d32400df72d7884af500586426d84640110c0f0e
Author: Kevin Jia <kjia@nexthop.ai>
hwmon: (fs1603) Add driver for TDK FS160x and FS1006 uPOL converters
This commit adds a read-only hwmon driver for the TDK FS1603, FS1604,
FS1606, and FS1006 uPOL DC-DC converters, reporting input and output
voltages, output current, temperature, and protection thresholds over a
proprietary I2C register map.
> diff --git a/drivers/hwmon/fs1603.c b/drivers/hwmon/fs1603.c
> new file mode 100644
> index 0000000000000..ae22964d22b2c
> --- /dev/null
> +++ b/drivers/hwmon/fs1603.c
> @@ -0,0 +1,480 @@
[ ... ]
> +static const struct i2c_device_id fs1603_id[] = {
> + { "fs1603", (kernel_ulong_t)&fs1603_models[fs1603] },
> + { "fs1604", (kernel_ulong_t)&fs1603_models[fs1604] },
> + { "fs1606", (kernel_ulong_t)&fs1603_models[fs1606] },
> + { "fs1606_0600", (kernel_ulong_t)&fs1603_models[fs1606_0600] },
> + { "fs1606_2500", (kernel_ulong_t)&fs1603_models[fs1606_2500] },
> + { "fs1006_5000", (kernel_ulong_t)&fs1603_models[fs1006] },
> + { "fs1006_3300", (kernel_ulong_t)&fs1603_models[fs1006] },
> + {}
> +};
> +MODULE_DEVICE_TABLE(i2c, fs1603_id);
[Severity: Low]
This isn't a bug, but should the entries in fs1603_id[] in
drivers/hwmon/fs1603.c use named initializers (.name and .driver_data)
rather than positional initializers, matching the convention for new
struct i2c_device_id tables and the style used in fs1603_of_match[] right
below?
[ ... ]
────
Touestas, feedback, or questions about this review? Email
linux-kernel-bot@google.com.
────
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261019-fs1603-v1-0-8adf972386c1@nexthop.ai?part=3
prev parent reply other threads:[~2026-10-19 18:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 18:45 [PATCH 0/3] hwmon: (fs1603) Add driver for TDK FS160x and FS1006 uPOL converters Kevin Jia
2026-10-19 18:45 ` [PATCH 1/3] dt-bindings: vendor-prefixes: Add TDK Kevin Jia
2026-10-19 18:47 ` sashiko-bot
2026-10-19 18:45 ` [PATCH 2/3] dt-bindings: trivial-devices: Add TDK FS160x and FS1006 Kevin Jia
2026-10-19 18:47 ` sashiko-bot
2026-10-19 18:45 ` [PATCH 3/3] hwmon: (fs1603) Add driver for TDK FS160x and FS1006 uPOL converters Kevin Jia
2026-10-19 18:52 ` sashiko-bot [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=sashiko-outbox-178111@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kjia@nexthop.ai \
--cc=linux-hwmon@vger.kernel.org \
--cc=robh@kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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.