From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Andrzej Hajda <a.hajda@samsung.com>,
Antonio Borneo <antonio.borneo@foss.st.com>,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Jonas Karlman <jonas@kwiboo.se>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Robert Foss <robert.foss@linaro.org>,
dri-devel@lists.freedesktop.org
Cc: linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] drm: adv7511: override i2c address of cec before accessing it
Date: Tue, 21 Dec 2021 11:39:51 +0000 [thread overview]
Message-ID: <164008679146.2512616.5965783147922289011@Monstersaurus> (raw)
In-Reply-To: <210c1e7c333b42702ac0c3ba0da639e82327d035.camel@foss.st.com>
Quoting Antonio Borneo (2021-12-20 15:53:12)
> On Mon, 2021-12-20 at 14:54 +0000, Kieran Bingham wrote:
> > Hi Antonio,
> >
> > Quoting Antonio Borneo (2021-12-18 18:28:04)
> > > Commit 680532c50bca ("drm: adv7511: Add support for
> > > i2c_new_secondary_device") allows a device tree node to override
> > > the default addresses of the secondary i2c devices. This is useful
> > > for solving address conflicts on the i2c bus.
> > >
> > > In adv7511_init_cec_regmap() the new i2c address of cec device is
> > > read from device tree and immediately accessed, well before it is
> > > written in the proper register to override the default address.
> > > This can cause an i2c error during probe and a consequent probe
> > > failure.
> >
> > Ouch, it does seem that way. I guess no one has used the CEC for
> > quite
> > some time, as it must have been like this for a while?
>
> Using the default i2c address for cec works without problem; apparently
> everyone is happy with such default. The issue appears only when you
> have to override the default cec address.
> The commit 680532c50bca landed in v4.18.
Ok, phew - so the 'normal' case still worked. That makes sense.
Sorry for getting it wrong, and I hope it didn't take too long to find
and fix. I'm sure we'll see it percolate down the stable trees once
integrated.
--
Kieran
> > > Once the new i2c address is read from the device tree, override
> > > the default address before any attempt to access the cec.
> >
> > Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
>
> Thanks!
> Antonio
>
> > > Tested with adv7533 and stm32mp157f.
> > >
> > > Signed-off-by: Antonio Borneo <antonio.borneo@foss.st.com>
> > > Fixes: 680532c50bca ("drm: adv7511: Add support for
> > > i2c_new_secondary_device")
> > > ---
> > > To: Andrzej Hajda <a.hajda@samsung.com>
> > > To: Neil Armstrong <narmstrong@baylibre.com>
> > > To: Robert Foss <robert.foss@linaro.org>
> > > To: Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
> > > To: Jonas Karlman <jonas@kwiboo.se>
> > > To: Jernej Skrabec <jernej.skrabec@gmail.com>
> > > To: David Airlie <airlied@linux.ie>
> > > To: Daniel Vetter <daniel@ffwll.ch>
> > > To: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
> > > To: dri-devel@lists.freedesktop.org
> > > Cc: linux-kernel@vger.kernel.org
> > > Cc: linux-stm32@st-md-mailman.stormreply.com
> > > ---
> > > drivers/gpu/drm/bridge/adv7511/adv7511_drv.c | 7 ++++---
> > > 1 file changed, 4 insertions(+), 3 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> > > b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> > > index 76555ae64e9c..629e05286fd9 100644
> > > --- a/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> > > +++ b/drivers/gpu/drm/bridge/adv7511/adv7511_drv.c
> > > @@ -1048,6 +1048,10 @@ static int adv7511_init_cec_regmap(struct
> > > adv7511 *adv)
> > >
> > > ADV7511_CEC_I2C_ADDR_DEFAULT);
> > > if (IS_ERR(adv->i2c_cec))
> > > return PTR_ERR(adv->i2c_cec);
> > > +
> > > + regmap_write(adv->regmap, ADV7511_REG_CEC_I2C_ADDR,
> > > + adv->i2c_cec->addr << 1);
> > > +
> > > i2c_set_clientdata(adv->i2c_cec, adv);
> > >
> > > adv->regmap_cec = devm_regmap_init_i2c(adv->i2c_cec,
> > > @@ -1252,9 +1256,6 @@ static int adv7511_probe(struct i2c_client
> > > *i2c, const struct i2c_device_id *id)
> > > if (ret)
> > > goto err_i2c_unregister_packet;
> > >
> > > - regmap_write(adv7511->regmap, ADV7511_REG_CEC_I2C_ADDR,
> > > - adv7511->i2c_cec->addr << 1);
> > > -
> > > INIT_WORK(&adv7511->hpd_work, adv7511_hpd_work);
> > >
> > > if (i2c->irq) {
> > >
> > > base-commit: fc74881c28d314b10efac016ef49df4ff40b8b97
> > > --
> > > 2.34.1
> > >
>
next prev parent reply other threads:[~2021-12-21 11:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-18 18:28 [PATCH] drm: adv7511: override i2c address of cec before accessing it Antonio Borneo
2021-12-20 14:54 ` Kieran Bingham
2021-12-20 15:53 ` Antonio Borneo
2021-12-21 11:39 ` Kieran Bingham [this message]
2022-06-07 21:31 ` [PATCH RESEND] " Antonio Borneo
2022-06-10 8:17 ` Robert Foss
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=164008679146.2512616.5965783147922289011@Monstersaurus \
--to=kieran.bingham+renesas@ideasonboard.com \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=a.hajda@samsung.com \
--cc=airlied@linux.ie \
--cc=antonio.borneo@foss.st.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=narmstrong@baylibre.com \
--cc=robert.foss@linaro.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).