linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	linux-iio@vger.kernel.org
Subject: Re: [PATCH] iio: accel: bmc150: Add support for BOSC0200 ACPI device id
Date: Tue, 20 Jun 2017 17:15:24 +0100	[thread overview]
Message-ID: <20170620171524.20fd7a70@kernel.org> (raw)
In-Reply-To: <20170619062225.3402-1-hdegoede@redhat.com>

On Mon, 19 Jun 2017 08:22:25 +0200
Hans de Goede <hdegoede@redhat.com> wrote:

> Add support for the BOSC0200 ACPI device id used on some x86 tablets.
> note driver_data is not set to a specific model, driver_data is not
> used anyways (instead detection is done on the chip_id reg) and the
> 2 tablets with a BOSC0200 ACPI device id I've have 2 different chips,
> one has a BMA250E, the other a BMA222E.
> 
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>
Applied to the togreg branch of iio.git. Initially pushed out as testing
for the autobuilders to play with it.

Unfortunately I'm travelling currently so may or may not get another pull
request in to Greg before the next merge window opens.

Jonathan
> ---
>  drivers/iio/accel/bmc150-accel-i2c.c | 1 +
>  1 file changed, 1 insertion(+)
> 
> diff --git a/drivers/iio/accel/bmc150-accel-i2c.c b/drivers/iio/accel/bmc150-accel-i2c.c
> index 8ca8041267ef..f85014fbaa12 100644
> --- a/drivers/iio/accel/bmc150-accel-i2c.c
> +++ b/drivers/iio/accel/bmc150-accel-i2c.c
> @@ -64,6 +64,7 @@ static const struct acpi_device_id bmc150_accel_acpi_match[] = {
>  	{"BMA250E",	bma250e},
>  	{"BMA222E",	bma222e},
>  	{"BMA0280",	bma280},
> +	{"BOSC0200"},
>  	{ },
>  };
>  MODULE_DEVICE_TABLE(acpi, bmc150_accel_acpi_match);


      reply	other threads:[~2017-06-20 16:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19  6:22 [PATCH] iio: accel: bmc150: Add support for BOSC0200 ACPI device id Hans de Goede
2017-06-20 16:15 ` 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=20170620171524.20fd7a70@kernel.org \
    --to=jic23@kernel.org \
    --cc=hdegoede@redhat.com \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.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).