From: Jonathan Cameron <jic23@kernel.org>
To: Wolfram Sang <wsa@the-dreams.de>
Cc: Ge Gao <GGao@invensense.com>,
Manuel Stahl <manuel.stahl@iis.fraunhofer.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
lee.jones@linaro.org
Subject: Re: [PATCH 3/3] iio: imu: inv_mpu6050: Add basic support for mpu9150
Date: Tue, 18 Feb 2014 08:34:31 +0000 [thread overview]
Message-ID: <53031B17.8030608@kernel.org> (raw)
In-Reply-To: <20140215133934.GA2579@katana>
On 15/02/14 13:39, Wolfram Sang wrote:
>
>> Wolfram, what do you think?
>>
>> In short we have a device that sits on an i2c bus and supports its own
>> i2c bus (mainly so that the internal processor can use data from devices
>> on that bus) including support for passing the bus straight through.
>> The issues is the dependencies when the intermediate device is sleeping
>> for example.
>
> Just judging from the paragraph above and not digging into the topic
> deeper, I think the idea of an 1-1 multiplexer is suitable. Would the
> pass-throu device then be a MFD? Are the alternative ideas?
>
Seems like overkill to introduce an MFD for this little addition to a fairly
large (and likely to grow driver). Its a little ugly, but would you mind
if the multiplexer is just handled directly within the main driver?
(perhaps via a config option). It would be 'odd' to say the least if
someone really wanted the pass through and not the complex inertial chip
it is part of.
Might just be simpler to do a very trivial mfd with the two parts hanging of it.
The complexity is that the inertial sensor will often take over the device
hanging off it completely so we will need to have it cleanly blocked as busy.
Lee, what do you think?
Jonathan
next prev parent reply other threads:[~2014-02-18 8:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-05 10:34 [PATCH 1/3] iio: imu: mpu6050: Move config entry into IMU menu Manuel Stahl
2014-02-05 10:34 ` [PATCH 2/3] iio: imu: inv_mpu6050: Fix typo and formatting Manuel Stahl
2014-02-08 12:29 ` Jonathan Cameron
2014-02-05 10:34 ` [PATCH 3/3] iio: imu: inv_mpu6050: Add basic support for mpu9150 Manuel Stahl
2014-02-08 12:31 ` Jonathan Cameron
2014-02-10 18:20 ` Ge Gao
2014-02-10 18:39 ` Manuel Stahl
2014-02-11 19:12 ` Ge Gao
2014-02-15 12:28 ` Jonathan Cameron
2014-02-15 13:39 ` Wolfram Sang
2014-02-18 8:34 ` Jonathan Cameron [this message]
2014-02-24 16:23 ` Lee Jones
2014-02-24 17:04 ` Wolfram Sang
2014-02-08 12:28 ` [PATCH 1/3] iio: imu: mpu6050: Move config entry into IMU menu 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=53031B17.8030608@kernel.org \
--to=jic23@kernel.org \
--cc=GGao@invensense.com \
--cc=lee.jones@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=manuel.stahl@iis.fraunhofer.de \
--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).