All of lore.kernel.org
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Miotsuki Mizuno" <founder@crepuse.com>
Cc: conor+dt@kernel.org, devicetree@vger.kernel.org,
	dmitry.torokhov@gmail.com, robh@kernel.org,
	linux-input@vger.kernel.org
Subject: Re: [PATCH v2 3/3] Input: add Nsiway NS2009 resistive touchscreen driver
Date: Sun, 11 Oct 2026 05:48:19 +0000	[thread overview]
Message-ID: <sashiko-outbox-167045@kernel.org> (raw)
In-Reply-To: <20261011054223.93396-4-founder@crepuse.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Low] i2c: i2c_device_id array is missing named initializers
--

commit 0ef31ef1051f1f4d0d958b8c5e57e36de085c191
Author: Miotsuki Mizuno <founder@crepuse.com>
Subject: Input: add Nsiway NS2009 resistive touchscreen driver

This commit introduces a new polling driver for the Nsiway NS2009 I2C
touchscreen controller. It supports reading 12-bit X/Y ADC values and reports
touch events using 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 int ns2009_probe(struct i2c_client *client)
> +{

[ ... ]

> +	error = input_register_device(input);
> +	if (error)
> +		return dev_err_probe(dev, error,
> +				     "failed to register input device\n");
> +
> +	return 0;
> +}
> +
> +static const struct i2c_device_id ns2009_id[] = {
> +	{ "ns2009" },

[Severity: Low]
This isn't a runtime bug, but I2C subsystem guidelines require initialized
arrays of type struct i2c_device_id to use named initializers. Should this
element be initialized as { .name = "ns2009" } instead of positionally?

> +	{ }
> +};
> +MODULE_DEVICE_TABLE(i2c, ns2009_id);

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261011054223.93396-1-founder@crepuse.com?part=3

      reply	other threads:[~2026-10-11  5:48 UTC|newest]

Thread overview: 14+ 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-12  9:00   ` Krzysztof Kozlowski
2026-10-09 14:47 ` [PATCH 2/3] dt-bindings: input: touchscreen: add Nsiway NS2009 Miotsuki Mizuno
2026-10-11  5:13   ` Dmitry Torokhov
2026-10-09 14:47 ` [PATCH 3/3] Input: add Nsiway NS2009 resistive touchscreen driver Miotsuki Mizuno
2026-10-09 14:53   ` sashiko-bot
2026-10-11  5:42 ` [PATCH v2 0/3] Add Nsiway NS2009 touchscreen support Miotsuki Mizuno
2026-10-11  5:42   ` [PATCH v2 1/3] dt-bindings: vendor-prefixes: add Nsiway Miotsuki Mizuno
2026-10-12  9:00     ` Krzysztof Kozlowski
2026-10-11  5:42   ` [PATCH v2 2/3] dt-bindings: input: touchscreen: add Nsiway NS2009 Miotsuki Mizuno
2026-10-12  9:02     ` Krzysztof Kozlowski
2026-10-11  5:42   ` [PATCH v2 3/3] Input: add Nsiway NS2009 resistive touchscreen driver Miotsuki Mizuno
2026-10-11  5:48     ` 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-167045@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 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.