[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAK4VdL0jph-LzkRai=6nLahgrvG0cFNt5N3GNGjKAE-G0jc38A@mail.gmail.com>
Date: Tue, 11 Jun 2019 14:05:55 +0200
From: Erico Nunes <nunes.erico@...il.com>
To: Sean Paul <sean@...rly.run>
Cc: Douglas Anderson <dianders@...omium.org>,
Sean Paul <seanpaul@...omium.org>,
"open list:ARM/Rockchip SoC..." <linux-rockchip@...ts.infradead.org>,
Heiko Stuebner <heiko@...ech.de>,
David Airlie <airlied@...ux.ie>,
Andrzej Hajda <a.hajda@...sung.com>,
Jonas Karlman <jonas@...boo.se>,
LKML <linux-kernel@...r.kernel.org>,
dri-devel <dri-devel@...ts.freedesktop.org>,
Sam Ravnborg <sam@...nborg.org>,
Neil Armstrong <narmstrong@...libre.com>,
Ville Syrjälä <ville.syrjala@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Laurent Pinchart <Laurent.pinchart@...asonboard.com>,
Daniel Vetter <daniel@...ll.ch>
Subject: Re: [PATCH] drm/bridge/synopsys: dw-hdmi: Fix unwedge crash when no
pinctrl entries
On Mon, Jun 10, 2019 at 10:51 PM Sean Paul <sean@...rly.run> wrote:
>
> On Mon, Jun 10, 2019 at 1:52 PM Douglas Anderson <dianders@...omium.org> wrote:
> >
> > In commit 50f9495efe30 ("drm/bridge/synopsys: dw-hdmi: Add "unwedge"
> > for ddc bus") I stupidly used IS_ERR() to check for whether we have an
> > "unwedge" pinctrl state even though on most flows through the driver
> > the unwedge state will just be NULL.
> >
> > Fix it so that we consistently use NULL for no unwedge state.
> >
> > Fixes: 50f9495efe30 ("drm/bridge/synopsys: dw-hdmi: Add "unwedge" for ddc bus")
> > Reported-by: Erico Nunes <nunes.erico@...il.com>
> > Signed-off-by: Douglas Anderson <dianders@...omium.org>
>
> Thanks Erico for the report, and Doug for fixing this up quickly, I've applied
> the patch to drm-misc-next
It does fix the issue. Thank you for the quick fix.
Erico
Powered by blists - more mailing lists