linux-iio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>
Cc: wsa@the-dreams.de, lars@metafoo.de, linux-iio@vger.kernel.org
Subject: Re: [PATCH v3] iio: imu: inv_mpu6050: client enumeration
Date: Tue, 03 Feb 2015 19:16:44 +0000	[thread overview]
Message-ID: <54D11E9C.5030701@kernel.org> (raw)
In-Reply-To: <1422656745-13576-1-git-send-email-srinivas.pandruvada@linux.intel.com>

On 30/01/15 22:25, Srinivas Pandruvada wrote:
> Last comment from Jonathan was
> "
> This all looks fine to me, though ideally I'd like some input from
> others, more familiar with the dmi stuff etc and from Wolfram / others
> wrt to the approach.
> "
Given timing, (just missed likely merge this cycle) we now have a reasonable
amount of time.  So lets leave this a little while yet...
> 
> So anybody have a better suggestion, I am still open to take them.
> Otherwise please consider as a merge candidate.
> 
> v3
> Add CONFIG_ACPI protection to avoid compiler warning.
> 
> v2
> Add CONFIG_ACPI to call creation of mux clients, instead of relying
> on ACPI_HANDLE not present for non ACPI platforms
> It is possible that there is no secondary address, this is not an error.
> 
> v1
> This is an option if auto detect is not desired. 
> Here using ACPI magic, by parsing both standard and vendor ACPI
> data.
> 
> v0
> Using autodetect feature.
> Using HWMON class as other places in the system for mux and
> client sensor drivers.
> 
> Srinivas Pandruvada (1):
>   iio: imu: inv_mpu6050: Create mux clients for ACPI
> 
>  drivers/iio/imu/inv_mpu6050/Makefile       |   2 +-
>  drivers/iio/imu/inv_mpu6050/inv_mpu_acpi.c | 211 +++++++++++++++++++++++++++++
>  drivers/iio/imu/inv_mpu6050/inv_mpu_core.c |   7 +
>  drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h  |   3 +
>  4 files changed, 222 insertions(+), 1 deletion(-)
>  create mode 100644 drivers/iio/imu/inv_mpu6050/inv_mpu_acpi.c
> 


  parent reply	other threads:[~2015-02-03 19:16 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-30 22:25 [PATCH v3] iio: imu: inv_mpu6050: client enumeration Srinivas Pandruvada
2015-01-30 22:25 ` [PATCH v3] iio: imu: inv_mpu6050: Create mux clients for ACPI Srinivas Pandruvada
2015-02-03 19:16 ` Jonathan Cameron [this message]
2015-02-21 18:06   ` [PATCH v3] iio: imu: inv_mpu6050: client enumeration Jonathan Cameron
2015-02-25 12:03     ` 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=54D11E9C.5030701@kernel.org \
    --to=jic23@kernel.org \
    --cc=lars@metafoo.de \
    --cc=linux-iio@vger.kernel.org \
    --cc=srinivas.pandruvada@linux.intel.com \
    --cc=wsa@the-dreams.de \
    /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).