From: Romain Gantois <romain.gantois@bootlin.com>
To: Cosmin Tanislav <demonsingur@gmail.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
Luca Ceresoli <luca.ceresoli@bootlin.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Arnd Bergmann <arnd@arndb.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-media@vger.kernel.org,
Cosmin Tanislav <demonsingur@gmail.com>
Subject: Re: [PATCH v4 9/9] i2c: atr: add passthrough flag
Date: Mon, 05 May 2025 18:13:56 +0200 [thread overview]
Message-ID: <3034821.e9J7NaK4W3@fw-rgant> (raw)
In-Reply-To: <20250428102516.933571-10-demonsingur@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2678 bytes --]
On Monday, 28 April 2025 12:25:14 CEST Cosmin Tanislav wrote:
> Some I2C ATRs can have other I2C ATRs as children. The I2C messages of
> the child ATRs need to be forwarded as-is if the parent I2C ATR can
> only do static mapping.
>
> In the case of GMSL, the deserializer I2C ATR actually doesn't have I2C
> address remapping hardware capabilities, but it is able to select which
> GMSL link to talk to, allowing it to change the address of the
> serializer.
>
> The child ATRs need to have their alias pools defined in such a way to
> prevent overlapping addresses between them, but there's no way around
> this without orchestration between multiple ATR instances.
>
> To allow for this use-case, add a flag that allows unmapped addresses
> to be passed through, since they are already remapped by the child ATRs.
>
> There's no case where an address that has not been remapped by the child
> ATR will hit the parent ATR.
>
> Signed-off-by: Cosmin Tanislav <demonsingur@gmail.com>
> ---
> drivers/i2c/i2c-atr.c | 7 +++++--
> include/linux/i2c-atr.h | 2 ++
> 2 files changed, 7 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/i2c/i2c-atr.c b/drivers/i2c/i2c-atr.c
> index 721dd680f2ac..eccb85c34609 100644
> --- a/drivers/i2c/i2c-atr.c
> +++ b/drivers/i2c/i2c-atr.c
> @@ -394,6 +394,9 @@ static int i2c_atr_map_msgs(struct i2c_atr_chan *chan,
> struct i2c_msg *msgs, c2a = i2c_atr_get_mapping_by_addr(chan,
> msgs[i].addr);
>
> if (!c2a) {
> + if (atr->flags & I2C_ATR_F_PASSTHROUGH)
> + continue;
> +
> dev_err(atr->dev, "client 0x%02x not mapped!\n",
> msgs[i].addr);
>
> @@ -486,13 +489,13 @@ static int i2c_atr_smbus_xfer(struct i2c_adapter
> *adap, u16 addr,
>
> c2a = i2c_atr_get_mapping_by_addr(chan, addr);
>
> - if (!c2a) {
> + if (!c2a && !(atr->flags & I2C_ATR_F_PASSTHROUGH)) {
> dev_err(atr->dev, "client 0x%02x not mapped!\n", addr);
> mutex_unlock(&chan->alias_pairs_lock);
> return -ENXIO;
> }
>
> - alias = c2a->alias;
> + alias = c2a ? c2a->alias : addr;
>
> mutex_unlock(&chan->alias_pairs_lock);
>
> diff --git a/include/linux/i2c-atr.h b/include/linux/i2c-atr.h
> index 7c6a9627191d..f979b931ca05 100644
> --- a/include/linux/i2c-atr.h
> +++ b/include/linux/i2c-atr.h
> @@ -22,9 +22,11 @@ struct i2c_atr;
> * enum i2c_atr_flags - Flags for an I2C ATR driver
> *
> * @I2C_ATR_F_STATIC: ATR does not support dynamic mapping, use static
> mapping + * @I2C_ATR_F_PASSTHROUGH: Allow unmapped incoming addresses to
> pass through */
> enum i2c_atr_flags {
> I2C_ATR_F_STATIC = BIT(0),
> + I2C_ATR_F_PASSTHROUGH = BIT(1),
> };
>
> /**
Reviewed-by: Romain Gantois <romain.gantois@bootlin.com>
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2025-05-05 16:14 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-28 10:25 [PATCH v4 0/9] i2c: atr: allow usage of nested ATRs Cosmin Tanislav
2025-04-28 10:25 ` [PATCH v4 1/9] i2c: atr: Fix lockdep for " Cosmin Tanislav
2025-04-30 14:31 ` Luca Ceresoli
2025-04-28 10:25 ` [PATCH v4 2/9] i2c: atr: find_mapping() -> get_mapping() Cosmin Tanislav
2025-04-30 14:32 ` Luca Ceresoli
2025-04-28 10:25 ` [PATCH v4 3/9] i2c: atr: split up i2c_atr_get_mapping_by_addr() Cosmin Tanislav
2025-04-30 14:33 ` Luca Ceresoli
2025-05-05 10:26 ` Cosmin Tanislav
2025-05-05 11:22 ` Luca Ceresoli
2025-04-28 10:25 ` [PATCH v4 4/9] i2c: atr: do not create mapping in detach_addr() Cosmin Tanislav
2025-04-30 14:33 ` Luca Ceresoli
2025-04-28 10:25 ` [PATCH v4 5/9] i2c: atr: deduplicate logic in attach_addr() Cosmin Tanislav
2025-04-30 14:33 ` Luca Ceresoli
2025-05-05 15:40 ` Romain Gantois
2025-04-28 10:25 ` [PATCH v4 6/9] i2c: atr: allow replacing mappings " Cosmin Tanislav
2025-04-30 14:33 ` Luca Ceresoli
2025-05-05 10:33 ` Cosmin Tanislav
2025-05-05 11:32 ` Luca Ceresoli
2025-04-28 10:25 ` [PATCH v4 7/9] i2c: atr: add flags parameter to i2c_atr_new() Cosmin Tanislav
2025-04-30 14:34 ` Luca Ceresoli
2025-05-05 15:50 ` Romain Gantois
2025-04-28 10:25 ` [PATCH v4 8/9] i2c: atr: add static flag Cosmin Tanislav
2025-04-30 14:36 ` Luca Ceresoli
2025-05-05 15:58 ` Romain Gantois
2025-04-28 10:25 ` [PATCH v4 9/9] i2c: atr: add passthrough flag Cosmin Tanislav
2025-04-30 14:36 ` Luca Ceresoli
2025-05-05 16:13 ` Romain Gantois [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=3034821.e9J7NaK4W3@fw-rgant \
--to=romain.gantois@bootlin.com \
--cc=arnd@arndb.de \
--cc=demonsingur@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=luca.ceresoli@bootlin.com \
--cc=mchehab@kernel.org \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=wsa+renesas@sang-engineering.com \
/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