From: Antti Palosaari <crope@iki.fi>
To: Peter Rosin <peda@lysator.liu.se>, Wolfram Sang <wsa@the-dreams.de>
Cc: Peter Rosin <peda@axentia.se>, Rob Herring <robh+dt@kernel.org>,
Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Peter Korsgaard <peter.korsgaard@barco.com>,
Guenter Roeck <linux@roeck-us.net>,
Jonathan Cameron <jic23@kernel.org>,
Hartmut Knaack <knaack.h@gmx.de>,
Lars-Peter Clausen <lars@metafoo.de>,
Peter Meerwald <pmeerw@pmeerw.net>,
Mauro Carvalho Chehab <mchehab@osg.samsung.com>,
Frank Rowand <frowand.list@gmail.com>,
Grant Likely <grant.likely@linaro.org>,
Adriana Reus <adriana.reus@intel.com>,
Srinivas Pandruvada <srinivas.pandruvada@linux.intel.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>,
Hans Verkuil <hans.verkuil@cisco.com>,
Nicholas Mc Guire <hofrat@osadl.org>,
Olli Salonen <olli.salonen@iki.fi>,
linux-i2c@vger.kernel.org, devicetree@vger.kerne
Subject: Re: [PATCH v2 0/8] i2c mux cleanup and locking update
Date: Wed, 6 Jan 2016 19:17:49 +0200 [thread overview]
Message-ID: <568D4C3D.3000906@iki.fi> (raw)
In-Reply-To: <1452009438-27347-1-git-send-email-peda@lysator.liu.se>
On 01/05/2016 05:57 PM, Peter Rosin wrote:
> From: Peter Rosin <peda@axentia.se>
>
> Hi!
>
> I have a pair of boards with this i2c topology:
>
> GPIO ---| ------ BAT1
> | v /
> I2C -----+------B---+---- MUX
> | \
> EEPROM ------ BAT2
>
> (B denotes the boundary between the boards)
Handling of I2C muxes that close channel automatically, after the first
I2C stop (P) is seen?
For example channel is selected to BAT1 => there is EEPROM write => mux
closes channel BAT1 => access to BAT1 will fail. Is it possible to lock
whole adapter, but allow only traffic to i2c mux client?
regards
Antti
>
> The problem with this is that the GPIO controller sits on the same i2c bus
> that it MUXes. For pca954x devices this is worked around by using unlocked
> transfers when updating the MUX. I have no such luck as the GPIO is a general
> purpose IO expander and the MUX is just a random bidirectional MUX, unaware
> of the fact that it is muxing an i2c bus, and extending unlocked transfers
> into the GPIO subsystem is too ugly to even think about. But the general hw
> approach is sane in my opinion, with the number of connections between the
> two boards minimized. To put is plainly, I need support for it.
>
> So, I observe that while it is needed to have the i2c bus locked during the
> actual MUX update in order to avoid random garbage on the slave side, it
> is not strictly a must to have it locked over the whole sequence of a full
> select-transfer-deselect operation. The MUX itself needs to be locked, so
> transfers to clients behind the mux are serialized, and the MUX needs to be
> stable during all i2c traffic (otherwise individual mux slave segments
> might see garbage).
>
> This series accomplishes this by adding a dt property to i2c-mux-gpio and
> i2c-mux-pinctrl that can be used to state that the mux is updated by means
> of the muxed master bus, and that the select-transfer-deselect operations
> should be locked individually. When this holds, the i2c bus *is* locked
> during muxing, since the muxing happens as part of i2c transfers. This
> is true even if the MUX is updated with several transfers to the GPIO (at
> least as long as *all* MUX changes are using the i2s master bus). A lock
> is added to the mux so that transfers through the mux are serialized.
>
> Concerns:
> - The locking is perhaps too complex?
> - I worry about the priority inheritance aspect of the adapter lock. When
> the transfers behind the mux are divided into select-transfer-deselect all
> locked individually, low priority transfers get more chances to interfere
> with high priority transfers.
> - When doing an i2c_transfer() in_atomic() context of with irqs_disabled(),
> there is a higher possibility that the mux is not returned to its idle
> state after a failed (-EAGAIN) transfer due to trylock.
>
> To summarize the series, there's some i2c-mux infrastructure cleanup work
> first (I think that part stands by itself as desireable regardless), the
> locking changes are in the last three patches of the series, with the real
> meat in 8/8.
>
> PS. needs a bunch of testing, I do not have access to all the involved hw
>
> Changes since v1:
> - Allocate mux core and (optional) priv in a combined allocation.
> - Killed dev_err messages triggered by memory allocation failure.
> - Fix the device specific i2c muxes that I had overlooked.
> - Rebased on top of v4.4-rc8 (was based on v4.4-rc6 previously).
>
> Cheers,
> Peter
>
> Peter Rosin (8):
> i2c-mux: add common core data for every mux instance
> i2c-mux: move select and deselect ops to i2c_mux_core
> i2c-mux: move the slave side adapter management to i2c_mux_core
> i2c-mux: remove the mux dev pointer from the mux per channel data
> i2c-mux: pinctrl: get rid of the driver private struct device pointer
> i2c: allow adapter drivers to override the adapter locking
> i2c: muxes always lock the parent adapter
> i2c-mux: relax locking of the top i2c adapter during i2c controlled
> muxing
>
> .../devicetree/bindings/i2c/i2c-mux-gpio.txt | 2 +
> .../devicetree/bindings/i2c/i2c-mux-pinctrl.txt | 4 +
> drivers/i2c/i2c-core.c | 59 ++---
> drivers/i2c/i2c-mux.c | 272 +++++++++++++++++----
> drivers/i2c/muxes/i2c-arb-gpio-challenge.c | 46 ++--
> drivers/i2c/muxes/i2c-mux-gpio.c | 58 ++---
> drivers/i2c/muxes/i2c-mux-pca9541.c | 58 +++--
> drivers/i2c/muxes/i2c-mux-pca954x.c | 66 ++---
> drivers/i2c/muxes/i2c-mux-pinctrl.c | 89 +++----
> drivers/i2c/muxes/i2c-mux-reg.c | 63 ++---
> drivers/iio/imu/inv_mpu6050/inv_mpu_core.c | 33 +--
> drivers/iio/imu/inv_mpu6050/inv_mpu_iio.h | 2 +-
> drivers/media/dvb-frontends/m88ds3103.c | 23 +-
> drivers/media/dvb-frontends/m88ds3103_priv.h | 2 +-
> drivers/media/dvb-frontends/rtl2830.c | 24 +-
> drivers/media/dvb-frontends/rtl2830_priv.h | 2 +-
> drivers/media/dvb-frontends/rtl2832.c | 30 ++-
> drivers/media/dvb-frontends/rtl2832_priv.h | 2 +-
> drivers/media/dvb-frontends/si2168.c | 29 ++-
> drivers/media/dvb-frontends/si2168_priv.h | 2 +-
> drivers/media/usb/cx231xx/cx231xx-core.c | 6 +-
> drivers/media/usb/cx231xx/cx231xx-i2c.c | 48 ++--
> drivers/media/usb/cx231xx/cx231xx.h | 4 +-
> drivers/of/unittest.c | 41 ++--
> include/linux/i2c-mux-gpio.h | 2 +
> include/linux/i2c-mux-pinctrl.h | 2 +
> include/linux/i2c-mux.h | 39 ++-
> include/linux/i2c.h | 28 ++-
> 28 files changed, 612 insertions(+), 424 deletions(-)
>
--
http://palosaari.fi/
next prev parent reply other threads:[~2016-01-06 17:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-05 15:57 [PATCH v2 0/8] i2c mux cleanup and locking update Peter Rosin
[not found] ` <1452009438-27347-1-git-send-email-peda-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org>
2016-01-05 15:57 ` [PATCH v2 1/8] i2c-mux: add common core data for every mux instance Peter Rosin
[not found] ` <1452009438-27347-2-git-send-email-peda-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org>
2016-01-05 16:42 ` Guenter Roeck
2016-01-05 18:55 ` Peter Rosin
2016-03-24 9:50 ` Vladimir Zapolskiy
[not found] ` <56F3B86E.4050002-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2016-03-24 11:05 ` Peter Rosin
[not found] ` <56F3CA0E.60906-SamgB31n2u5IcsJQ0EH25Q@public.gmane.org>
2016-03-24 14:24 ` Vladimir Zapolskiy
[not found] ` <56F3F89F.8000805-nmGgyN9QBj3QT0dZR+AlfA@public.gmane.org>
2016-03-24 18:59 ` Peter Rosin
2016-04-11 20:59 ` Wolfram Sang
2016-01-05 15:57 ` [PATCH v2 4/8] i2c-mux: remove the mux dev pointer from the mux per channel data Peter Rosin
2016-01-05 15:57 ` [PATCH v2 8/8] i2c-mux: relax locking of the top i2c adapter during i2c controlled muxing Peter Rosin
2016-01-06 14:49 ` Rob Herring
2016-01-07 8:21 ` Peter Rosin
2016-01-05 18:48 ` [PATCH v2 0/8] i2c mux cleanup and locking update Wolfram Sang
2016-01-05 19:01 ` Peter Rosin
2016-01-06 13:23 ` Crt Mori
2016-01-05 15:57 ` [PATCH v2 2/8] i2c-mux: move select and deselect ops to i2c_mux_core Peter Rosin
2016-01-05 15:57 ` [PATCH v2 3/8] i2c-mux: move the slave side adapter management " Peter Rosin
2016-01-05 16:49 ` kbuild test robot
2016-01-05 19:16 ` Peter Rosin
2016-01-05 22:17 ` Peter Rosin
2016-01-05 15:57 ` [PATCH v2 5/8] i2c-mux: pinctrl: get rid of the driver private struct device pointer Peter Rosin
2016-01-05 15:57 ` [PATCH v2 6/8] i2c: allow adapter drivers to override the adapter locking Peter Rosin
2016-01-05 15:57 ` [PATCH v2 7/8] i2c: muxes always lock the parent adapter Peter Rosin
2016-01-06 17:17 ` Antti Palosaari [this message]
[not found] ` <568D4C3D.3000906-X3B1VOXEql0@public.gmane.org>
2016-01-07 8:14 ` [PATCH v2 0/8] i2c mux cleanup and locking update Peter Rosin
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=568D4C3D.3000906@iki.fi \
--to=crope@iki.fi \
--cc=adriana.reus@intel.com \
--cc=devicetree@vger.kerne \
--cc=frowand.list@gmail.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=hans.verkuil@cisco.com \
--cc=hofrat@osadl.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=jic23@kernel.org \
--cc=k.kozlowski@samsung.com \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-i2c@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mark.rutland@arm.com \
--cc=mchehab@osg.samsung.com \
--cc=olli.salonen@iki.fi \
--cc=pawel.moll@arm.com \
--cc=peda@axentia.se \
--cc=peda@lysator.liu.se \
--cc=peter.korsgaard@barco.com \
--cc=pmeerw@pmeerw.net \
--cc=robh+dt@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).