mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Shrirang Bagul <shrirang.bagul@canonical.com>
Cc: knaack.h@gmx.de, lars@metafoo.de, pmeerw@pmeerw.net,
	lorenzo.bianconi83@gmail.com, linux-iio@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] iio: humidity: Support acpi probe for hts211
Date: Sun, 27 Nov 2016 11:17:35 +0000	[thread overview]
Message-ID: <11630563-1cc3-7411-82e8-ffaaeb9214e2@kernel.org> (raw)
In-Reply-To: <20161124090754.20427-1-shrirang.bagul@canonical.com>

On 24/11/16 09:07, Shrirang Bagul wrote:
> Support driver probe by reading unique HID on systems based on ACPI instead
> of DT compatible strings.
> 
> Signed-off-by: Shrirang Bagul <shrirang.bagul@canonical.com>
Applied to the togreg branch of iio.git and pushed out as testing for the autobuilders
to play with it.

Thanks,

Jonathan
> ---
>  drivers/iio/humidity/hts221_i2c.c | 8 ++++++++
>  1 file changed, 8 insertions(+)
> 
> diff --git a/drivers/iio/humidity/hts221_i2c.c b/drivers/iio/humidity/hts221_i2c.c
> index 367ecd5..8333c02 100644
> --- a/drivers/iio/humidity/hts221_i2c.c
> +++ b/drivers/iio/humidity/hts221_i2c.c
> @@ -10,6 +10,7 @@
>  
>  #include <linux/kernel.h>
>  #include <linux/module.h>
> +#include <linux/acpi.h>
>  #include <linux/i2c.h>
>  #include <linux/slab.h>
>  #include "hts221.h"
> @@ -83,6 +84,12 @@ static int hts221_i2c_probe(struct i2c_client *client,
>  	return hts221_probe(iio_dev);
>  }
>  
> +static const struct acpi_device_id hts221_acpi_match[] = {
> +	{"SMO9100", 0},
> +	{ },
> +};
> +MODULE_DEVICE_TABLE(acpi, hts221_acpi_match);
> +
>  static const struct of_device_id hts221_i2c_of_match[] = {
>  	{ .compatible = "st,hts221", },
>  	{},
> @@ -99,6 +106,7 @@ static struct i2c_driver hts221_driver = {
>  	.driver = {
>  		.name = "hts221_i2c",
>  		.of_match_table = of_match_ptr(hts221_i2c_of_match),
> +		.acpi_match_table = ACPI_PTR(hts221_acpi_match),
>  	},
>  	.probe = hts221_i2c_probe,
>  	.id_table = hts221_i2c_id_table,
> 

      reply	other threads:[~2016-11-27 11:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-24  9:07 Shrirang Bagul
2016-11-27 11:17 ` 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=11630563-1cc3-7411-82e8-ffaaeb9214e2@kernel.org \
    --to=jic23@kernel.org \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo.bianconi83@gmail.com \
    --cc=pmeerw@pmeerw.net \
    --cc=shrirang.bagul@canonical.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

Powered by JetHome