linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Lorenzo Bianconi <lorenzo@kernel.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: linux-i2c@vger.kernel.org, sr@denx.de, andi.shyti@kernel.org,
	matthias.bgg@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org, lorenzo.bianconi83@gmail.com,
	upstream@airoha.com, benjamin.larsson@genexis.eu
Subject: Re: [PATCH 2/2] i2c: mt7621: make device_reset optional
Date: Fri, 5 Jul 2024 10:30:39 +0200	[thread overview]
Message-ID: <ZoevL9XaIWn2AvFm@lore-desk> (raw)
In-Reply-To: <b402896c-6b91-4973-9e4f-8d1f7128afdc@collabora.com>

[-- Attachment #1: Type: text/plain, Size: 2519 bytes --]

> Il 05/07/24 00:16, Lorenzo Bianconi ha scritto:
> > Rely on device_reset_optional() instead of device_reset() in
> > mtk_i2c_reset routine since Airoha EN7581 reset controller does not
> > implement the reset callback and device reset is not mandatory on this
> 
> Not mandatory means that the reset line for I2C exists, but you don't want
> to use it? If so, that's not right.

ack, it was not so clear, sorry for that. What I mean with "not mandatory" is
the mt7621 i2c controller works on EN7581 SoC even w/o this reset configuration.

> 
> On the other hand, if there is an issue with using that reset line and you
> want to avoid using it for a good reason, please describe it into the commit
> description and - in that case, you'll have to add a EN7581 compatible and
> code to avoid calling device_reset() on that SoC.

what I mean is device_reset() will call .reset() callback of reset APIs. EN7581
reset driver does not implemetn this callback, just .assert() and .deassert()
(I think the hw does not support the reset line automatic re-arm) so the call to
device_reset() will always fails. Maybe a possible approach would be adding
in the reset driver something like:

en7581_reset() {
    en7581_assert();
    msleep(x);
    en7581_deassert();
    msleep(x);
}

What do you think? It seems a bit hacky to me and I am not sure what would be the
right delay in this case.

Regards,
Lorenzo

> 
> What you're doing here is removing an error log on SoCs that do *need* that
> reset line to be in place, so, hiding a problem that could be causing other
> issues on peripherals connected to the I2C bus of those other SoCs.
> 
> Cheers,
> Angelo
> 
> > SoC. This will remove the following log:
> > 
> > i2c-mt7621 1fbf8000.i2c0: I2C reset failed!
> > 
> > Tested-by: Ray Liu <ray.liu@airoha.com>
> > Signed-off-by: Lorenzo Bianconi <lorenzo@kernel.org>
> > ---
> >   drivers/i2c/busses/i2c-mt7621.c | 2 +-
> >   1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/drivers/i2c/busses/i2c-mt7621.c b/drivers/i2c/busses/i2c-mt7621.c
> > index 81d46169bc1f..8cd89a2f59df 100644
> > --- a/drivers/i2c/busses/i2c-mt7621.c
> > +++ b/drivers/i2c/busses/i2c-mt7621.c
> > @@ -85,7 +85,7 @@ static void mtk_i2c_reset(struct mtk_i2c *i2c)
> >   {
> >   	int ret;
> > -	ret = device_reset(i2c->adap.dev.parent);
> > +	ret = device_reset_optional(i2c->adap.dev.parent);
> >   	if (ret)
> >   		dev_err(i2c->dev, "I2C reset failed!\n");
> 
> 

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

      reply	other threads:[~2024-07-05  8:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-04 22:16 [PATCH 0/2] Introduce Airoha EN7581 i2c support Lorenzo Bianconi
2024-07-04 22:16 ` [PATCH 1/2] i2c: mt7621: Add " Lorenzo Bianconi
2024-07-05  8:15   ` AngeloGioacchino Del Regno
2024-07-04 22:16 ` [PATCH 2/2] i2c: mt7621: make device_reset optional Lorenzo Bianconi
2024-07-05  8:15   ` AngeloGioacchino Del Regno
2024-07-05  8:30     ` Lorenzo Bianconi [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=ZoevL9XaIWn2AvFm@lore-desk \
    --to=lorenzo@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=benjamin.larsson@genexis.eu \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=lorenzo.bianconi83@gmail.com \
    --cc=matthias.bgg@gmail.com \
    --cc=sr@denx.de \
    --cc=upstream@airoha.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;
as well as URLs for NNTP newsgroup(s).