Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Miotsuki Mizuno" <founder@crepuse.com>
Cc: robh@kernel.org, linux-input@vger.kernel.org,
	conor+dt@kernel.org, dmitry.torokhov@gmail.com,
	devicetree@vger.kernel.org
Subject: Re: [PATCH v3 3/3] Input: add Nsiway NS2009 resistive touchscreen driver
Date: Mon, 12 Oct 2026 12:23:25 +0000	[thread overview]
Message-ID: <sashiko-outbox-168090@kernel.org> (raw)
In-Reply-To: <20261012121705.53396-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 lacks named initializer
--

commit 1329443f9d0fcc43d7767e5dcaca297c790eca05
Author: Mizuno Miotsuki <founder@crepuse.com>

Input: add Nsiway NS2009 resistive touchscreen driver

This commit adds polling support for the Nsiway NS2009 I2C touchscreen
controller. It uses the input polling API, managed input allocation, and
applies coordinate transforms through common touchscreen helpers.

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]
The I2C subsystem guidelines state that initialized arrays of type
struct i2c_device_id must use named initializers. Should the ns2009_id array
use a named initializer, such as { .name = "ns2009" }, instead of a
positional initializer?

> +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/20261012121705.53396-1-founder@crepuse.com?part=3

      reply	other threads:[~2026-10-12 12:23 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-12 12:17 [PATCH v3 0/3] Add Nsiway NS2009 touchscreen support Miotsuki Mizuno
2026-10-12 12:17 ` [PATCH v3 1/3] dt-bindings: vendor-prefixes: add Nsiway Miotsuki Mizuno
2026-10-12 18:55   ` Conor Dooley
2026-10-12 12:17 ` [PATCH v3 2/3] dt-bindings: input: touchscreen: add Nsiway NS2009 Miotsuki Mizuno
2026-10-12 18:56   ` Conor Dooley
2026-10-12 12:17 ` [PATCH v3 3/3] Input: add Nsiway NS2009 resistive touchscreen driver Miotsuki Mizuno
2026-10-12 12:23   ` 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-168090@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