All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Cameron <jic23@kernel.org>
To: Ge Gao <GGao@invensense.com>,
	Crestez Dan Leonard <leonard.crestez@intel.com>,
	"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	Hartmut Knaack <knaack.h@gmx.de>,
	Lars-Peter Clausen <lars@metafoo.de>,
	Peter Meerwald-Stadler <pmeerw@pmeerw.net>,
	Daniel Baluta <daniel.baluta@intel.com>
Subject: Re: [PATCH 5/5] iio: inv_mpu6050: Add explicit support for MPU9150
Date: Mon, 25 Apr 2016 20:20:56 +0100	[thread overview]
Message-ID: <11e6a547-38d6-e817-5875-63781fca770d@kernel.org> (raw)
In-Reply-To: <DM3PR1201MB107242867FAACB76EF80ED45AF620@DM3PR1201MB1072.namprd12.prod.outlook.com>

On 25/04/16 18:56, Ge Gao wrote:
> This looks good to me.
> 
> Acked-by: Ge Gao <ggao@invensense.com >
Applied - I wasn't entirely certain whether you meant it as such,
but I've added the ack to all the patches in this series.

Thanks,

Jonathan
> 
> 
> 
> -----Original Message-----
> From: Jonathan Cameron [mailto:jic23@kernel.org] 
> Sent: Sunday, April 24, 2016 4:16 AM
> To: Crestez Dan Leonard; linux-iio@vger.kernel.org
> Cc: linux-kernel@vger.kernel.org; Hartmut Knaack; Lars-Peter Clausen; Peter Meerwald-Stadler; Daniel Baluta; Ge Gao
> Subject: Re: [PATCH 5/5] iio: inv_mpu6050: Add explicit support for MPU9150
> 
> On 20/04/16 14:15, Crestez Dan Leonard wrote:
>> This device is a package containing a MPU6050-like sensor and an 
>> AK8975 magnetometer. The magnetometer component is supported by the 
>> existing
>> ak8975 driver.
>>
>> This patch also rephrases the Kconfig descriptions.
>>
>> Signed-off-by: Crestez Dan Leonard <leonard.crestez@intel.com>
> Looks good.  Will just wait for Ge to hopefully have time to take a look at the whole series.  For future reference, it's always worth making sure you have cc'd the original author of a driver unless you know someone else is definitely maintaining it.
> 
> Ge was reply to emails recently so I guess he is still very much active!
> 
> Jonathan
>> ---
>>  drivers/iio/imu/inv_mpu6050/Kconfig        | 10 ++++------
>>  drivers/iio/imu/inv_mpu6050/inv_mpu_core.c |  6 ++++++  
>> drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c  |  1 +  
>> drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h  |  2 ++  
>> drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c  |  1 +
>>  5 files changed, 14 insertions(+), 6 deletions(-)
>>
>> diff --git a/drivers/iio/imu/inv_mpu6050/Kconfig 
>> b/drivers/iio/imu/inv_mpu6050/Kconfig
>> index a7f557a..c05d474 100644
>> --- a/drivers/iio/imu/inv_mpu6050/Kconfig
>> +++ b/drivers/iio/imu/inv_mpu6050/Kconfig
>> @@ -14,10 +14,8 @@ config INV_MPU6050_I2C
>>  	select I2C_MUX
>>  	select REGMAP_I2C
>>  	help
>> -	  This driver supports the Invensense MPU6050 devices.
>> -	  This driver can also support MPU6500 in MPU6050 compatibility mode
>> -	  and also in MPU6500 mode with some limitations.
>> -	  It is a gyroscope/accelerometer combo device.
>> +	  This driver supports the Invensense MPU6050/6500/9150 motion tracking
>> +	  devices over I2C.
>>  	  This driver can be built as a module. The module will be called
>>  	  inv-mpu6050-i2c.
>>  
>> @@ -27,7 +25,7 @@ config INV_MPU6050_SPI
>>  	select INV_MPU6050_IIO
>>  	select REGMAP_SPI
>>  	help
>> -	  This driver supports the Invensense MPU6050 devices.
>> -	  It is a gyroscope/accelerometer combo device.
>> +	  This driver supports the Invensense MPU6000/6500/9150 motion tracking
>> +	  devices over SPI.
>>  	  This driver can be built as a module. The module will be called
>>  	  inv-mpu6050-spi.
>> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c 
>> b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
>> index 273b7fa7..3a82a49 100644
>> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
>> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_core.c
>> @@ -108,6 +108,12 @@ static const struct inv_mpu6050_hw hw_info[] = {
>>  		.reg = &reg_set_6050,
>>  		.config = &chip_config_6050,
>>  	},
>> +	{
>> +		.whoami = INV_MPU9150_WHOAMI_VALUE,
>> +		.name = "MPU9150",
>> +		.reg = &reg_set_6050,
>> +		.config = &chip_config_6050,
>> +	},
>>  };
>>  
>>  int inv_mpu6050_switch_engine(struct inv_mpu6050_state *st, bool en, 
>> u32 mask) diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c 
>> b/drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c
>> index bb1a7b1..1a424a6 100644
>> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c
>> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c
>> @@ -202,6 +202,7 @@ static int inv_mpu_remove(struct i2c_client 
>> *client)  static const struct i2c_device_id inv_mpu_id[] = {
>>  	{"mpu6050", INV_MPU6050},
>>  	{"mpu6500", INV_MPU6500},
>> +	{"mpu9150", INV_MPU9150},
>>  	{}
>>  };
>>  
>> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h 
>> b/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h
>> index 564cabd..38d6a09 100644
>> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h
>> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h
>> @@ -68,6 +68,7 @@ enum inv_devices {
>>  	INV_MPU6050,
>>  	INV_MPU6500,
>>  	INV_MPU6000,
>> +	INV_MPU9150,
>>  	INV_NUM_PARTS
>>  };
>>  
>> @@ -220,6 +221,7 @@ struct inv_mpu6050_state {
>>  #define INV_MPU6000_WHOAMI_VALUE		0x68
>>  #define INV_MPU6050_WHOAMI_VALUE		0x68
>>  #define INV_MPU6500_WHOAMI_VALUE		0x70
>> +#define INV_MPU9150_WHOAMI_VALUE		0x68
>>  
>>  /* scan element definition */
>>  enum inv_mpu6050_scan {
>> diff --git a/drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c 
>> b/drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c
>> index a0f8df2..190a4a5 100644
>> --- a/drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c
>> +++ b/drivers/iio/imu/inv_mpu6050/inv_mpu_spi.c
>> @@ -81,6 +81,7 @@ static int inv_mpu_remove(struct spi_device *spi)  
>> static const struct spi_device_id inv_mpu_id[] = {
>>  	{"mpu6000", INV_MPU6000},
>>  	{"mpu6500", INV_MPU6500},
>> +	{"mpu9150", INV_MPU9150},
>>  	{}
>>  };
>>  
>>
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-iio" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

      reply	other threads:[~2016-04-25 19:21 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-20 13:15 [PATCH 0/5] iio: inv_mpu6050: Cleanup chip types and add mpu9150 Crestez Dan Leonard
2016-04-20 13:15 ` [PATCH 1/5] iio: inv_mpu6050: Cleanup hw_info mapping Crestez Dan Leonard
2016-04-24 11:10   ` Jonathan Cameron
2016-04-25 18:41     ` Jonathan Cameron
2016-04-20 13:15 ` [PATCH 2/5] iio: inv_mpu6050: Remove inv_mpu6050_hw.num_reg Crestez Dan Leonard
2016-04-24 11:12   ` Jonathan Cameron
2016-04-25 18:43     ` Jonathan Cameron
2016-04-20 13:15 ` [PATCH 3/5] iio: inv_mpu6050: Check WHO_AM_I register on probe Crestez Dan Leonard
2016-04-24 11:14   ` Jonathan Cameron
2016-04-25 11:17     ` Crestez Dan Leonard
2016-04-25 18:09       ` Jonathan Cameron
2016-04-20 13:15 ` [PATCH 4/5] iio: inv_mpu6050: Add spi_device_id for INV_MPU6500 Crestez Dan Leonard
2016-04-20 13:15 ` [PATCH 5/5] iio: inv_mpu6050: Add explicit support for MPU9150 Crestez Dan Leonard
2016-04-24 11:16   ` Jonathan Cameron
2016-04-25 17:56     ` Ge Gao
2016-04-25 17:56       ` Ge Gao
2016-04-25 19:20       ` 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=11e6a547-38d6-e817-5875-63781fca770d@kernel.org \
    --to=jic23@kernel.org \
    --cc=GGao@invensense.com \
    --cc=daniel.baluta@intel.com \
    --cc=knaack.h@gmx.de \
    --cc=lars@metafoo.de \
    --cc=leonard.crestez@intel.com \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.