linux-kernel - Re: [RESEND 0/5] drm/mxsfb: Fix runtime PM for unpowering lcdif block

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 20 Sep 2018 15:59:12 +0000
From:   Leonard Crestez <leonard.crestez@....com>
To:     "stefan@...er.ch" <stefan@...er.ch>,
        "gustavo@...ovan.org" <gustavo@...ovan.org>,
        "marex@...x.de" <marex@...x.de>,
        "sean@...rly.run" <sean@...rly.run>,
        "maarten.lankhorst@...ux.intel.com" 
        <maarten.lankhorst@...ux.intel.com>
CC:     dl-linux-imx <linux-imx@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "daniel.vetter@...ll.ch" <daniel.vetter@...ll.ch>,
        Robert Chiras <robert.chiras@....com>,
        Fabio Estevam <fabio.estevam@....com>,
        "p.zabel@...gutronix.de" <p.zabel@...gutronix.de>,
        "dri-devel@...ts.freedesktop.org" <dri-devel@...ts.freedesktop.org>,
        "shawnguo@...nel.org" <shawnguo@...nel.org>,
        Anson Huang <anson.huang@....com>,
        "airlied@...ux.ie" <airlied@...ux.ie>,
        "kernel@...gutronix.de" <kernel@...gutronix.de>
Subject: Re: [RESEND 0/5] drm/mxsfb: Fix runtime PM for unpowering lcdif block

On Mon, 2018-09-17 at 16:37 -0700, Stefan Agner wrote:
> On 17.09.2018 12:16, Sean Paul wrote:
> > On Mon, Sep 17, 2018 at 04:42:10PM +0300, Leonard Crestez wrote:
> > > Adding lcdif nodes to a power domain currently doesn't work, it results
> > > in black/corrupted screens or hangs. While the driver does enable
> > > runtime pm it does not deal correctly with the block being unpowered.
> > > 
> > > All patches in this series have review tags from a while ago and I
> > > tested them again on top of next-20180913. No changes
> > > 
> > > This series stalled so I reached out to Marek on IRC and he was
> > > surprised to be listed as maintainer
> > 
> > Hopefully not too surprised since Marek added themself to MAINTAINERS when
> > adding the driver :-)
> 
> There have been some confusion about the DRM development processes
> around the mxsfb already in the past.
>
> > I suppose we should probably move this to drm-misc since it qualifies as a
> > "small driver" and needs a home. Looking through git history shows the last
> > mxsfb-specific change was back in 02/17. Everything else has been drm-wide
> > refactors. Thoughts?
> > 
> > Marek/Leonard: Care to sign up to be listed as a reviewers?
> 
> drm-misc seems to make sense. I volunteer to be listed as reviewer or co-maintainer.

This gets +1 from me, you were very helpful during review.

Next would be for one of the drm-misc maintainers to post a change for
the MAINTAINER file and also merge my series?

--
Regards,
Leonard