linux-kernel - Re: [PATCH v4 1/5] drm/mxsfb: Move axi clk enable/disable to crtc enable/disable

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 for Android: free password hash cracker in your pocket

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

Message-ID: <9924032f27426ec6cc36f645deb70014a674006c.camel@nxp.com>
Date:   Mon, 13 Aug 2018 13:19:06 +0000
From:   Leonard Crestez <leonard.crestez@....com>
To:     "stefan@...er.ch" <stefan@...er.ch>,
        "marex@...x.de" <marex@...x.de>
CC:     dl-linux-imx <linux-imx@....com>,
        "A.s. Dong" <aisheng.dong@....com>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        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>,
        "kernel@...gutronix.de" <kernel@...gutronix.de>
Subject: Re: [PATCH v4 1/5] drm/mxsfb: Move axi clk enable/disable to crtc
 enable/disable

On Wed, 2018-08-08 at 20:57 +0200, Stefan Agner wrote:
> On 08.08.2018 18:08, Leonard Crestez wrote:
> > The main axi clk is disabled at the end of mxsfb_crtc_mode_set_nofb and
> > immediately reenabled in mxsfb_enable_controller.
> > 
> > Avoid this by moving the handling of axi clk one level up to
> > mxsfb_crtc_enable. Do the same for mxsfb_crtc_disable for simmetry
> > 
> > This shouldn't have any functional effect.
> > 
> > Signed-off-by: Leonard Crestez <leonard.crestez@....com>
> 
> Thanks, looks good!
> 
> Reviewed-by: Stefan Agner <stefan@...er.ch>

So what is next now that this entire series was reviewed? My guess is
that somebody needs to push it to drm-misc-next.

However 4.18 was just released and I'm not sure how this interacts with
drm. As far as I can tell drm-misc-next is always open and a patch
accepted now will make it into 4.20, based on this graph:

https://01.org/linuxgraphics/gfx-docs/maintainer-tools/drm-misc.html#merge-timeline

--
Regards,
Leonard