From: Jonathan Cameron <jic23@kernel.org>
To: "Ardelean, Alexandru" <alexandru.Ardelean@analog.com>
Cc: "lkcamp@lists.libreplanetbr.org" <lkcamp@lists.libreplanetbr.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"djunho@gmail.com" <djunho@gmail.com>,
"lars@metafoo.de" <lars@metafoo.de>,
"pmeerw@pmeerw.net" <pmeerw@pmeerw.net>,
"knaack.h@gmx.de" <knaack.h@gmx.de>,
"Hennerich, Michael" <Michael.Hennerich@analog.com>,
"Popa, Stefan Serban" <StefanSerban.Popa@analog.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 3/4] iio: adc: ad7923: Add of_device_id table
Date: Mon, 23 Dec 2019 15:36:18 +0000 [thread overview]
Message-ID: <20191223153618.234c29cd@archlinux> (raw)
In-Reply-To: <daf1148cb29129023ebd1c11f2b0fba86c9446f3.camel@analog.com>
On Tue, 17 Dec 2019 11:30:56 +0000
"Ardelean, Alexandru" <alexandru.Ardelean@analog.com> wrote:
> On Tue, 2019-12-17 at 08:11 -0300, Daniel Junho wrote:
> > Accomplish device tree compatibility to driver AD7923
> > by adding of_device_id table and making a subsequent call to
> > MODULE_DEVICE_TABLE.
> >
>
> Reviewed-by: Alexandru Ardelean <alexandru.ardelean@analog.com>
Applied to the togreg branch of iio.git and pushed out as testing
for the autobuilders to play with it.
Thanks,
Jonathan
>
> > Signed-off-by: Daniel Junho <djunho@gmail.com>
> > ---
> > drivers/iio/adc/ad7923.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/iio/adc/ad7923.c b/drivers/iio/adc/ad7923.c
> > index e535cec9fc02..6d56fa0b9e30 100644
> > --- a/drivers/iio/adc/ad7923.c
> > +++ b/drivers/iio/adc/ad7923.c
> > @@ -348,9 +348,19 @@ static const struct spi_device_id ad7923_id[] = {
> > };
> > MODULE_DEVICE_TABLE(spi, ad7923_id);
> >
> > +static const struct of_device_id ad7923_of_match[] = {
> > + { .compatible = "adi,ad7904", },
> > + { .compatible = "adi,ad7914", },
> > + { .compatible = "adi,ad7923", },
> > + { .compatible = "adi,ad7924", },
> > + { },
> > +};
> > +MODULE_DEVICE_TABLE(of, ad7923_of_match);
> > +
> > static struct spi_driver ad7923_driver = {
> > .driver = {
> > .name = "ad7923",
> > + .of_match_table = ad7923_of_match,
> > },
> > .probe = ad7923_probe,
> > .remove = ad7923_remove,
next prev parent reply other threads:[~2019-12-23 15:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 11:11 [PATCH v3 0/4] Add support for the ad7908/ad7918/ad7928 Daniel Junho
2019-12-17 11:11 ` [PATCH v3 1/4] iio: adc: ad7923: Remove the unused defines Daniel Junho
2019-12-17 11:29 ` Ardelean, Alexandru
2019-12-23 15:34 ` Jonathan Cameron
2019-12-17 11:11 ` [PATCH v3 2/4] iio: adc: ad7923: Fix checkpatch warning Daniel Junho
2019-12-17 11:30 ` Ardelean, Alexandru
2019-12-23 15:35 ` Jonathan Cameron
2019-12-17 11:11 ` [PATCH v3 3/4] iio: adc: ad7923: Add of_device_id table Daniel Junho
2019-12-17 11:30 ` Ardelean, Alexandru
2019-12-23 15:36 ` Jonathan Cameron [this message]
2019-12-17 11:11 ` [PATCH v3 4/4] iio: adc: ad7923: Add support for the ad7908/ad7918/ad7928 Daniel Junho
2019-12-17 11:35 ` Ardelean, Alexandru
2019-12-23 15:34 ` Jonathan Cameron
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=20191223153618.234c29cd@archlinux \
--to=jic23@kernel.org \
--cc=Michael.Hennerich@analog.com \
--cc=StefanSerban.Popa@analog.com \
--cc=alexandru.Ardelean@analog.com \
--cc=djunho@gmail.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkcamp@lists.libreplanetbr.org \
--cc=pmeerw@pmeerw.net \
/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;
as well as URLs for NNTP newsgroup(s).