linux-kernel - Re: [PATCH v2] drm/imx: imx-ldb: Accept drm_of_find_panel_or

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <1496831750.28352.62.camel@nxp.com>
Date:   Wed, 7 Jun 2017 13:35:50 +0300
From:   Leonard Crestez <leonard.crestez@....com>
To:     Philipp Zabel <p.zabel@...gutronix.de>
CC:     David Airlie <airlied@...ux.ie>, <dri-devel@...ts.freedesktop.org>,
        <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] drm/imx: imx-ldb: Accept drm_of_find_panel_or_bridge
 failure

On Wed, 2017-05-10 at 15:55 +0200, Philipp Zabel wrote:
> On Wed, 2017-05-10 at 16:17 +0300, Leonard Crestez wrote:
> > 
> > Not having an endpoint bound in DT should not cause a failure here,
> > there are fallbacks. So explicitly accept a missing endpoint.
> > 
> > This behavior change was introduced by refactoring in drm_of parsing
> > code and it should not require dts changes.
> > 
> > In particular this fixes imx6qdl-sabreauto boards.
> > 
> > diff --git a/drivers/gpu/drm/imx/imx-ldb.c b/drivers/gpu/drm/imx/imx-ldb.c
> > index 8fb801f..8b05ecb 100644
> > --- a/drivers/gpu/drm/imx/imx-ldb.c
> > +++ b/drivers/gpu/drm/imx/imx-ldb.c
> > @@ -673,7 +673,7 @@ static int imx_ldb_bind(struct device *dev, struct device *master, void *data)
> >  		ret = drm_of_find_panel_or_bridge(child,
> >  						  imx_ldb->lvds_mux ? 4 : 2, 0,
> >  						  &channel->panel, &channel->bridge);
> > -		if (ret)
> > +		if (ret && ret != -ENODEV)
> >  			return ret;
> >  
> >  		/* panel ddc only if there is no bridge */
> Thank you, applied to imx-drm/fixes.
> 
> regards
> Philipp

How are such fixes going to make their way upstream? It's been almost a
month and this patch did not get into either linux-next or
torvalds/master or anywhere other than pza/imx-drm/fixes.

--
Regards,
Leonard