From: sashiko-bot@kernel.org
To: "Miotsuki Mizuno" <founder@crepuse.com>
Cc: dmitry.torokhov@gmail.com, devicetree@vger.kernel.org,
robh@kernel.org, conor+dt@kernel.org,
linux-input@vger.kernel.org
Subject: Re: [PATCH 3/3] Input: add Nsiway NS2009 resistive touchscreen driver
Date: Fri, 09 Oct 2026 14:53:13 +0000 [thread overview]
Message-ID: <sashiko-outbox-165743@kernel.org> (raw)
In-Reply-To: <20261009144729.85832-4-founder@crepuse.com>
Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] i2c: missing named initializer in i2c_device_id array
--
commit 22cbbc5b42325e09804bb86ec6c548c4fefefb81
Author: Miotsuki Mizuno <founder@crepuse.com>
Input: add Nsiway NS2009 resistive touchscreen driver
Add polling support for the Nsiway NS2009 I2C touchscreen controller using
the input polling API and managed input allocation. Read 12-bit X/Y ADC
values and report BTN_TOUCH from the raw Z1 contact threshold.
Link: https://lore.kernel.org/all/20170315155140.54518-4-icenowy@aosc.xyz/
> diff --git a/drivers/input/touchscreen/ns2009.c b/drivers/input/touchscreen/ns2009.c
> new file mode 100644
> index 0000000000000..d5c1f9f96bb6b
> --- /dev/null
> +++ b/drivers/input/touchscreen/ns2009.c
[ ... ]
> +static const struct i2c_device_id ns2009_id[] = {
> + { "ns2009" },
[Severity: Low]
Should this array element use a named initializer?
The I2C subsystem guidelines specify that initialized arrays of type
struct i2c_device_id must be declared const and use named initializers
(e.g., { .name = "ns2009" }).
> + { }
> +};
> +MODULE_DEVICE_TABLE(i2c, ns2009_id);
> +
> +static const struct of_device_id ns2009_of_match[] = {
> + { .compatible = "nsiway,ns2009" },
--
Sashiko AI review · https://sashiko.dev/#/patchset/20261009144729.85832-1-founder@crepuse.com?part=3
prev parent reply other threads:[~2026-10-09 14:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-09 14:47 [PATCH 0/3] Add Nsiway NS2009 touchscreen support Miotsuki Mizuno
2026-10-09 14:47 ` [PATCH 1/3] dt-bindings: vendor-prefixes: add Nsiway Miotsuki Mizuno
2026-10-09 14:47 ` [PATCH 2/3] dt-bindings: input: touchscreen: add Nsiway NS2009 Miotsuki Mizuno
2026-10-09 14:47 ` [PATCH 3/3] Input: add Nsiway NS2009 resistive touchscreen driver Miotsuki Mizuno
2026-10-09 14:53 ` 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-165743@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=founder@crepuse.com \
--cc=linux-input@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox