From: <Victor.Duicu@microchip.com>
To: <jic23@kernel.org>
Cc: <Marius.Cristea@microchip.com>, <matteomartelli3@gmail.com>,
<lars@metafoo.de>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v1] iio: adc: pac1921: add ACPI support for pac1921
Date: Wed, 2 Oct 2024 12:44:16 +0000 [thread overview]
Message-ID: <b459b62eed7418d4eadb60b4f1e4816448176e20.camel@microchip.com> (raw)
In-Reply-To: <20240928174253.15e1fe7a@jic23-huawei>
On Sat, 2024-09-28 at 17:42 +0100, Jonathan Cameron wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Wed, 25 Sep 2024 18:08:56 +0300
> <victor.duicu@microchip.com> wrote:
>
> > From: Victor Duicu <victor.duicu@microchip.com>
> >
> >
> > MODULE_DEVICE_TABLE(of, pac1921_of_match);
> >
> > +static const struct acpi_device_id pac1921_acpi_match[] = {
> > + { "MCHP1921" },
>
> That's a valid ID for once which is good. I'll assume Microchip
> has a process for tracking these and avoiding clashes.
>
MCHP id is registered with UEFI and MCHP1921 is tracked internally.
> > + { }
> > +};
> > +MODULE_DEVICE_TABLE(acpi, pac1921_acpi_match);
> > static struct i2c_driver pac1921_driver = {
> > .driver = {
> > .name = "pac1921",
> > .pm = pm_sleep_ptr(&pac1921_pm_ops),
> > .of_match_table = pac1921_of_match,
> > + .acpi_match_table = pac1921_acpi_match
> > },
> > .probe = pac1921_probe,
> > .id_table = pac1921_id,
> >
> > base-commit: fec496684388685647652ab4213454fbabdab099
>
prev parent reply other threads:[~2024-10-02 12:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-25 15:08 [PATCH v1] iio: adc: pac1921: add ACPI support for pac1921 victor.duicu
2024-09-27 9:07 ` Matteo Martelli
2024-09-28 16:42 ` Jonathan Cameron
2024-10-02 12:44 ` Victor.Duicu [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=b459b62eed7418d4eadb60b4f1e4816448176e20.camel@microchip.com \
--to=victor.duicu@microchip.com \
--cc=Marius.Cristea@microchip.com \
--cc=jic23@kernel.org \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matteomartelli3@gmail.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