From: Abel Vesa <abel.vesa@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Andrzej Hajda <andrzej.hajda@intel.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Robert Foss <rfoss@kernel.org>,
Laurent Pinchart <Laurent.pinchart@ideasonboard.com>,
Jonas Karlman <jonas@kwiboo.se>,
Jernej Skrabec <jernej.skrabec@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] drm/bridge: Fix assignment of the of_node of the parent to aux bridge
Date: Thu, 31 Oct 2024 18:13:45 +0200 [thread overview]
Message-ID: <ZyOsuTr4XBU3ogRx@linaro.org> (raw)
In-Reply-To: <ZyOOwEPB9NLNtL4N@hovoldconsulting.com>
On 24-10-31 15:05:52, Johan Hovold wrote:
> On Mon, Oct 21, 2024 at 09:23:24AM +0200, Johan Hovold wrote:
> > On Fri, Oct 18, 2024 at 03:49:34PM +0300, Abel Vesa wrote:
> > > The assignment of the of_node to the aux bridge needs to mark the
> > > of_node as reused as well, otherwise resource providers like pinctrl will
> > > report a gpio as already requested by a different device when both pinconf
> > > and gpios property are present.
> >
> > I don't think you need a gpio property for that to happen, right? And
> > this causes probe to fail IIRC?
Yes, I think this is actually because of the pinctrl property in the node,
so no gpio needed.
Yes, probe fails.
> >
> > > Fix that by using the device_set_of_node_from_dev() helper instead.
> > >
> > > Fixes: 6914968a0b52 ("drm/bridge: properly refcount DT nodes in aux bridge drivers")
> >
> > This is not the commit that introduced the issue.
The proper fixes tag here is actually:
Fixes: 2a04739139b2 ("drm/bridge: add transparent bridge helper")
> >
> > > Cc: stable@vger.kernel.org # 6.8
> >
> > I assume there are no existing devicetrees that need this since then we
> > would have heard about it sooner. Do we still need to backport it?
None of the DTs I managed to scan seem to have this problem.
Maybe backporting it is not worth it then.
> >
> > When exactly are you hitting this?
Here is one of the examples.
[ 5.768283] x1e80100-tlmm f100000.pinctrl: error -EINVAL: pin-185 (aux_bridge.aux_bridge.3)
[ 5.768289] x1e80100-tlmm f100000.pinctrl: error -EINVAL: could not request pin 185 (GPIO_185) from group gpio185 on device f100000.pinctrl
[ 5.768293] aux_bridge.aux_bridge aux_bridge.aux_bridge.3: Error applying setting, reverse things back
>
> Abel, even if Neil decided to give me the finger here, please answer the
> above so that it's recorded in the archives at least.
>
> Johan
>
Sorry for not replying in time before the patch was merge.
Abel.
next prev parent reply other threads:[~2024-10-31 16:13 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-18 12:49 [PATCH v2] drm/bridge: Fix assignment of the of_node of the parent to aux bridge Abel Vesa
2024-10-18 15:43 ` Dmitry Baryshkov
2024-10-30 16:45 ` Sui Jingfeng
2024-10-30 19:39 ` Laurent Pinchart
2024-10-31 12:29 ` Neil Armstrong
2024-10-21 7:12 ` Neil Armstrong
2024-10-21 7:23 ` Johan Hovold
2024-10-31 14:05 ` Johan Hovold
2024-10-31 16:13 ` Abel Vesa [this message]
2024-10-31 16:33 ` Johan Hovold
2024-11-01 9:49 ` Abel Vesa
2024-10-31 15:48 ` Dmitry Baryshkov
2024-10-31 16:26 ` Johan Hovold
2024-10-21 13:08 ` Neil Armstrong
2024-10-30 14:49 ` Sui Jingfeng
2024-10-31 12:31 ` Neil Armstrong
2024-10-31 14:02 ` Johan Hovold
2024-10-31 15:31 ` Sui Jingfeng
2024-10-31 15:06 ` Sui Jingfeng
2024-10-31 16:23 ` Johan Hovold
2024-11-01 3:49 ` Sui Jingfeng
2024-11-01 7:27 ` Johan Hovold
2024-11-01 9:20 ` Laurent Pinchart
2024-11-01 10:27 ` Dmitry Baryshkov
2024-11-01 14:43 ` Laurent Pinchart
2024-11-01 6:15 ` Sui Jingfeng
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=ZyOsuTr4XBU3ogRx@linaro.org \
--to=abel.vesa@linaro.org \
--cc=Laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=andrzej.hajda@intel.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=jernej.skrabec@gmail.com \
--cc=johan@kernel.org \
--cc=jonas@kwiboo.se \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=rfoss@kernel.org \
--cc=simona@ffwll.ch \
--cc=stable@vger.kernel.org \
--cc=tzimmermann@suse.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