From: Jonathan Cameron <jic23@kernel.org>
To: <victor.duicu@microchip.com>
Cc: <dlechner@baylibre.com>, <nuno.sa@analog.com>, <andy@kernel.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<marius.cristea@microchip.com>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] iio: temperature: add support for MCP998X
Date: Sat, 14 Jun 2025 14:27:04 +0100 [thread overview]
Message-ID: <20250614142704.3c07e453@jic23-huawei> (raw)
In-Reply-To: <20250614141837.06d6e82f@jic23-huawei>
>
> > +
> > +static const struct i2c_device_id mcp9982_id[] = {
> > + { .name = "mcp9933", .driver_data = (kernel_ulong_t)&mcp9933_chip_config },
> > + { .name = "mcp9933d", .driver_data = (kernel_ulong_t)&mcp9933d_chip_config },
> > + { .name = "mcp9982", .driver_data = (kernel_ulong_t)&mcp9982_chip_config },
> > + { .name = "mcp9982d", .driver_data = (kernel_ulong_t)&mcp9982d_chip_config },
> > + { .name = "mcp9983", .driver_data = (kernel_ulong_t)&mcp9983_chip_config },
> > + { .name = "mcp9983d", .driver_data = (kernel_ulong_t)&mcp9983d_chip_config },
> > + { .name = "mcp9984", .driver_data = (kernel_ulong_t)&mcp9984_chip_config },
> > + { .name = "mcp9984d", .driver_data = (kernel_ulong_t)&mcp9984d_chip_config },
> > + { .name = "mcp9985", .driver_data = (kernel_ulong_t)&mcp9985_chip_config },
> > + { .name = "mcp9985d", .driver_data = (kernel_ulong_t)&mcp9985d_chip_config },
> > + { }
> David mentioned the other day that there is an effort to remove the need for
> the kernel_ulong_t here but it relies on
> { "mcp9985d", &mcp9984d_chip_config },
> style entries.
Oops. Still need the cast.
>
> https://lore.kernel.org/all/1c7946f1-d712-4baa-8243-be6a55eec528@baylibre.com/
>
> I wasn't aware of that effort but seems sensible to me!
>
>
> > +};
> > +MODULE_DEVICE_TABLE(i2c, mcp9982_id);
>
>
prev parent reply other threads:[~2025-06-14 13:27 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-13 13:02 [PATCH v3 0/2] add support for MCP998X victor.duicu
2025-06-13 13:02 ` [PATCH v3 1/2] dt-bindings: iio: temperature: " victor.duicu
2025-06-13 14:40 ` Conor Dooley
2025-06-23 13:07 ` Victor.Duicu
2025-07-28 13:01 ` Victor.Duicu
2025-07-29 16:27 ` David Lechner
2025-06-13 13:02 ` [PATCH v3 2/2] " victor.duicu
2025-06-13 21:50 ` Andy Shevchenko
2025-06-19 7:22 ` Victor.Duicu
2025-06-19 8:29 ` Andy Shevchenko
2025-06-21 17:19 ` Jonathan Cameron
2025-06-23 6:45 ` Andy Shevchenko
2025-06-14 13:18 ` Jonathan Cameron
2025-06-14 13:27 ` Jonathan Cameron [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=20250614142704.3c07e453@jic23-huawei \
--to=jic23@kernel.org \
--cc=andy@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dlechner@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marius.cristea@microchip.com \
--cc=nuno.sa@analog.com \
--cc=robh@kernel.org \
--cc=victor.duicu@microchip.com \
/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