From: Luca Ceresoli <luca.ceresoli@bootlin.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: zzam@gentoo.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-i2c@vger.kernel.org, "Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Wolfram Sang" <wsa@kernel.org>,
"Andy Shevchenko" <andriy.shevchenko@intel.com>,
"Matti Vaittinen" <Matti.Vaittinen@fi.rohmeurope.com>,
"Laurent Pinchart" <laurent.pinchart+renesas@ideasonboard.com>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Peter Rosin" <peda@axentia.se>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Sakari Ailus" <sakari.ailus@linux.intel.com>,
"Michael Tretter" <m.tretter@pengutronix.de>,
"Hans Verkuil" <hverkuil@xs4all.nl>,
"Mike Pagano" <mpagano@gentoo.org>,
"Krzysztof Hałasa" <khalasa@piap.pl>,
"Marek Vasut" <marex@denx.de>,
"Satish Nagireddy" <satish.nagireddy@getcruise.com>,
"Luca Ceresoli" <luca@lucaceresoli.net>
Subject: Re: [PATCH v10 1/8] i2c: add I2C Address Translator (ATR) support
Date: Tue, 21 Mar 2023 11:56:15 +0100 [thread overview]
Message-ID: <20230321115615.0145124b@booty> (raw)
In-Reply-To: <a21fcab7-aa80-0228-7bd3-236fb4203d36@ideasonboard.com>
Hi Tomi,
On Mon, 20 Mar 2023 14:12:32 +0200
Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> wrote:
> On 20/03/2023 10:28, Luca Ceresoli wrote:
> > Hello Matthias,
> >
> > thanks for the in-depth review!
> >
> > On Mon, 20 Mar 2023 07:34:34 +0100
> > zzam@gentoo.org wrote:
> >
> >> Some inline comments below.
> >>
> >> Regards
> >> Matthias
> >>
> >> Am 22.02.23 um 14:29 schrieb Tomi Valkeinen:
> >>> From: Luca Ceresoli <luca@lucaceresoli.net>
> >>>
> >>> An ATR is a device that looks similar to an i2c-mux: it has an I2C
> >>> slave "upstream" port and N master "downstream" ports, and forwards
> >>> transactions from upstream to the appropriate downstream port. But it
> >>> is different in that the forwarded transaction has a different slave
> >>> address. The address used on the upstream bus is called the "alias"
> >>> and is (potentially) different from the physical slave address of the
> >>> downstream chip.
> >>>
> >>> Add a helper file (just like i2c-mux.c for a mux or switch) to allow
> >>> implementing ATR features in a device driver. The helper takes care or
> >>> adapter creation/destruction and translates addresses at each transaction.
> >>>
> >>> Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net>
> >>> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
> >>> ---
> >>> Documentation/i2c/index.rst | 1 +
> >>> Documentation/i2c/muxes/i2c-atr.rst | 97 +++++
> >>> MAINTAINERS | 8 +
> >>> drivers/i2c/Kconfig | 9 +
> >>> drivers/i2c/Makefile | 1 +
> >>> drivers/i2c/i2c-atr.c | 548 ++++++++++++++++++++++++++++
> >>> include/linux/i2c-atr.h | 116 ++++++
> >>> 7 files changed, 780 insertions(+)
> >>> create mode 100644 Documentation/i2c/muxes/i2c-atr.rst
> >>> create mode 100644 drivers/i2c/i2c-atr.c
> >>> create mode 100644 include/linux/i2c-atr.h
> >>>
> >> [...]
> >>> diff --git a/drivers/i2c/i2c-atr.c b/drivers/i2c/i2c-atr.c
> >>> new file mode 100644
> >>> index 000000000000..5ab890b83670
> >>> --- /dev/null
> >>> +++ b/drivers/i2c/i2c-atr.c
> >>> @@ -0,0 +1,548 @@
> >> [...]
> >>> +
> >>> +/*
> >>> + * Replace all message addresses with their aliases, saving the original
> >>> + * addresses.
> >>> + *
> >>> + * This function is internal for use in i2c_atr_master_xfer(). It must be
> >>> + * followed by i2c_atr_unmap_msgs() to restore the original addresses.
> >>> + */
> >>> +static int i2c_atr_map_msgs(struct i2c_atr_chan *chan, struct i2c_msg *msgs,
> >>> + int num)
> >>> +{
> >>> + struct i2c_atr *atr = chan->atr;
> >>> + static struct i2c_atr_cli2alias_pair *c2a;
> >>> + int i;
> >>> +
> >>> + /* Ensure we have enough room to save the original addresses */
> >>> + if (unlikely(chan->orig_addrs_size < num)) {
> >>> + u16 *new_buf;
> >>> +
> >>> + /* We don't care about old data, hence no realloc() */
> >>> + new_buf = kmalloc_array(num, sizeof(*new_buf), GFP_KERNEL);
> >>> + if (!new_buf)
> >>> + return -ENOMEM;
> >>> +
> >>> + kfree(chan->orig_addrs);
> >>> + chan->orig_addrs = new_buf;
> >>> + chan->orig_addrs_size = num;
> >>> + }
> >>> +
> >>> + for (i = 0; i < num; i++) {
> >>> + chan->orig_addrs[i] = msgs[i].addr;
> >>> +
> >>> + c2a = i2c_atr_find_mapping_by_addr(&chan->alias_list,
> >>> + msgs[i].addr);
> >>> + if (!c2a) {
> >>> + dev_err(atr->dev, "client 0x%02x not mapped!\n",
> >>> + msgs[i].addr);
> >>> + return -ENXIO;
> >> I miss the roll-back of previously modified msgs[].addr values.
> >
> > Indeed you have a point. There is a subtle error in case all of the
> > following happen in a single i2c_atr_master_xfer() call:
> >
> > * there are 2+ messages, having different addresses
> > * msg[0] is mapped correctly
> > * msg[n] (n > 0) fails mapping
> >
> > It's very unlikely, but in this case we'd get back to the caller with
> > an error and modified addresses for the first n messages. Which in turn
> > is unlikely to create any problems, but it could.
> >
> > Tomi, do you agree?
> >
> > This looks like a simple solution:
> >
> > if (!c2a) {
> > + i2c_atr_unmap_msgs(chan, msgs, i);
> > ...
> > }
>
> Wouldn't that possibly restore the address from orig_addrs[x] also for
> messages we haven't handled yet?
No, because there is 'i' as the 3rd argument, not 'num'. But...
>
> I think a simple
>
> while (i--)
> msgs[i].addr = chan->orig_addrs[i];
>
> should do here. It is also, perhaps, a bit more clear this way, as you
> can see the assignments to msgs[i].addr nearby, and the rollback here
> with the above code. Instead of seeing a call to an unmap function,
> having to go and see what exactly it will do.
...sure, this would work. If I had connected my brain at the
appropriate time I would have realized it's two lines only. And
definitely less spaghetti-coded that what I had suggested.
Luca
--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-03-21 10:56 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 13:28 [PATCH v10 0/8] i2c-atr and FPDLink Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 1/8] i2c: add I2C Address Translator (ATR) support Tomi Valkeinen
2023-03-08 12:20 ` Tomi Valkeinen
2023-03-20 17:00 ` Wolfram Sang
2023-03-20 17:15 ` Tomi Valkeinen
2023-03-17 9:16 ` Luca Ceresoli
2023-03-17 12:11 ` Andy Shevchenko
2023-03-17 12:36 ` Tomi Valkeinen
2023-03-17 13:43 ` Andy Shevchenko
2023-03-20 6:34 ` zzam
2023-03-20 8:28 ` Luca Ceresoli
2023-03-20 12:12 ` Tomi Valkeinen
2023-03-21 10:56 ` Luca Ceresoli [this message]
2023-04-18 14:25 ` Wolfram Sang
2023-04-19 7:13 ` Luca Ceresoli
2023-02-22 13:29 ` [PATCH v10 2/8] media: subdev: Split V4L2_SUBDEV_ROUTING_NO_STREAM_MIX Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 3/8] dt-bindings: media: add TI DS90UB913 FPD-Link III Serializer Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 4/8] dt-bindings: media: add TI DS90UB953 " Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 5/8] dt-bindings: media: add TI DS90UB960 FPD-Link III Deserializer Tomi Valkeinen
2023-04-18 13:06 ` Wolfram Sang
2023-04-19 7:13 ` Luca Ceresoli
2023-04-19 8:05 ` Wolfram Sang
2023-04-19 16:13 ` Luca Ceresoli
2023-04-19 18:09 ` Wolfram Sang
2023-04-20 7:30 ` Tomi Valkeinen
2023-04-20 18:47 ` Wolfram Sang
2023-04-21 6:18 ` Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 6/8] media: i2c: add DS90UB960 driver Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 7/8] media: i2c: add DS90UB913 driver Tomi Valkeinen
2023-02-22 13:29 ` [PATCH v10 8/8] media: i2c: add DS90UB953 driver Tomi Valkeinen
2023-02-22 14:15 ` [PATCH v10 0/8] i2c-atr and FPDLink Andy Shevchenko
2023-02-22 14:17 ` Andy Shevchenko
2023-02-23 8:19 ` Tomi Valkeinen
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=20230321115615.0145124b@booty \
--to=luca.ceresoli@bootlin.com \
--cc=Matti.Vaittinen@fi.rohmeurope.com \
--cc=andriy.shevchenko@intel.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hverkuil@xs4all.nl \
--cc=khalasa@piap.pl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=lgirdwood@gmail.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca@lucaceresoli.net \
--cc=m.tretter@pengutronix.de \
--cc=marex@denx.de \
--cc=mchehab@kernel.org \
--cc=mpagano@gentoo.org \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=satish.nagireddy@getcruise.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wsa@kernel.org \
--cc=zzam@gentoo.org \
/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).