linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: "João Victor Marques de Oliveira" <joao.marques.oliveira@usp.br>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Michael Hennerich <Michael.Hennerich@analog.com>,
	Stefan Popa <stefan.popa@analog.com>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-iio@vger.kernel.org, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org, kernel-usp@googlegroups.com,
	"Thiago L . A . Miller" <tmiller@mochsl.org.br>,
	"Osvaldo M . Yasuda" <omyasuda@yahoo.com.br>
Subject: Re: [PATCH] staging: iio: ad9834: add of_device_id table
Date: Sun, 19 May 2019 11:39:49 +0100	[thread overview]
Message-ID: <20190519113949.2eb0cd3a@archlinux> (raw)
In-Reply-To: <20190518224720.30404-1-joao.marques.oliveira@usp.br>

On Sat, 18 May 2019 19:47:20 -0300
João Victor Marques de Oliveira         <joao.marques.oliveira@usp.br> wrote:

> Add a of_device_id struct array of_match_table variable and subsequent
> call to MODULE_DEVICE_TABLE macro to device tree support.
> 
> Co-developed-by: Thiago L. A. Miller <tmiller@mochsl.org.br>
> Signed-off-by: Thiago L. A. Miller <tmiller@mochsl.org.br>
> Co-developed-by: Osvaldo M. Yasuda <omyasuda@yahoo.com.br>
> Signed-off-by: Osvaldo M. Yasuda <omyasuda@yahoo.com.br>
> Signed-off-by: João Victor Marques de Oliveira <joao.marques.oliveira@usp.br>
Nice patch.

Applied to the togreg branch of iio.git and pushed out as testing for the
autobuilders to play with it.

Thanks,

j
> ---
>  drivers/staging/iio/frequency/ad9834.c | 11 +++++++++++
>  1 file changed, 11 insertions(+)
> 
> diff --git a/drivers/staging/iio/frequency/ad9834.c b/drivers/staging/iio/frequency/ad9834.c
> index 6de3cd7363d7..038d6732c3fd 100644
> --- a/drivers/staging/iio/frequency/ad9834.c
> +++ b/drivers/staging/iio/frequency/ad9834.c
> @@ -521,9 +521,20 @@ static const struct spi_device_id ad9834_id[] = {
>  };
>  MODULE_DEVICE_TABLE(spi, ad9834_id);
>  
> +static const struct of_device_id ad9834_of_match[] = {
> +	{.compatible = "adi,ad9833"},
> +	{.compatible = "adi,ad9834"},
> +	{.compatible = "adi,ad9837"},
> +	{.compatible = "adi,ad9838"},
> +	{}
> +};
> +
> +MODULE_DEVICE_TABLE(of, ad9834_of_match);
> +
>  static struct spi_driver ad9834_driver = {
>  	.driver = {
>  		.name	= "ad9834",
> +		.of_match_table = ad9834_of_match
>  	},
>  	.probe		= ad9834_probe,
>  	.remove		= ad9834_remove,


      reply	other threads:[~2019-05-19 17:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-18 22:47 [PATCH] staging: iio: ad9834: add of_device_id table João Victor Marques de Oliveira
2019-05-19 10:39 ` 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=20190519113949.2eb0cd3a@archlinux \
    --to=jic23@kernel.org \
    --cc=Michael.Hennerich@analog.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=joao.marques.oliveira@usp.br \
    --cc=kernel-usp@googlegroups.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=omyasuda@yahoo.com.br \
    --cc=pmeerw@pmeerw.net \
    --cc=stefan.popa@analog.com \
    --cc=tmiller@mochsl.org.br \
    /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).