[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b1d2ee83-248f-5603-6086-8ef2153271da@kernel.org>
Date: Sat, 12 Nov 2016 14:45:08 +0000
From: Jonathan Cameron <jic23@...nel.org>
To: Peter Rosin <peda@...ntia.se>, linux-iio@...r.kernel.org
Cc: Hartmut Knaack <knaack.h@....de>,
Lars-Peter Clausen <lars@...afoo.de>,
Peter Meerwald <pmeerw@...erw.net>,
linux-kernel@...r.kernel.org,
Crestez Dan Leonard <leonard.crestez@...el.com>
Subject: Re: [PATCH] iio: imu: inv_mpu6050: inform the i2c mux core about how
it is used
On 10/11/16 09:23, Peter Rosin wrote:
> On 2016-09-03 18:30, Jonathan Cameron wrote:
>> On 31/08/16 09:02, Peter Rosin wrote:
>>> The i2c mux core can then take appropriate action depending on if it is
>>> used for an actual i2c mux, or for an arbitrator or gate. In this case
>>> it is used as a gate.
>>>
>>> This will make devicetree bindings simpler when they are eventually
>>> added.
>>>
>>> Signed-off-by: Peter Rosin <peda@...ntia.se>
>>> ---
>>> drivers/iio/imu/inv_mpu6050/inv_mpu_i2c.c | 2 +-
>>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>>
>>> So, this depends on the i2c-mux-dt-3 branch [1] that Jonathan
>>> pulled to support the new mpu-3050 gyroscope driver. I had
>>> planned to submit this post 4.9-rc1, but since the iio tree
>>> got the prerequisite already, I'm sending it right away.
>> It's not there yet as the mpu-3050 has to go round again
>> for other reasons. As such I haven't yet pulled your branch.
>> This patch isn't going to justify the pull on it's own.
>>
>> I'll try and remember to pick it up when Linus gets back with
>> the final mpu-3050 and I pull your tree in.
>>
>> If not give me a poke!
>
> Friendly *poke* :-)
Applied to the togreg branch of iio.git
Thanks for the reminder!
Jonathan
>
> Cheers,
> Peter
>
Powered by blists - more mailing lists