From: Jonathan Cameron <jic23@kernel.org>
To: Peter Rosin <peda@axentia.se>, linux-iio@vger.kernel.org
Cc: Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
linux-kernel@vger.kernel.org,
Crestez Dan Leonard <leonard.crestez@intel.com>
Subject: Re: [PATCH] iio: imu: inv_mpu6050: inform the i2c mux core about how it is used
Date: Sat, 12 Nov 2016 14:45:08 +0000 [thread overview]
Message-ID: <b1d2ee83-248f-5603-6086-8ef2153271da@kernel.org> (raw)
In-Reply-To: <4765c3f7-dcdb-bc4c-4812-6542202d2405@axentia.se>
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@axentia.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
>
prev parent reply other threads:[~2016-11-12 14:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-31 8:02 [PATCH] iio: imu: inv_mpu6050: inform the i2c mux core about how it is used Peter Rosin
2016-09-03 16:30 ` Jonathan Cameron
2016-09-13 20:44 ` Linus Walleij
2016-11-10 9:23 ` Peter Rosin
2016-11-12 14:45 ` 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=b1d2ee83-248f-5603-6086-8ef2153271da@kernel.org \
--to=jic23@kernel.org \
--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=peda@axentia.se \
--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