mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Leonard Crestez <leonard.crestez@nxp.com>
To: "stefan@agner.ch" <stefan@agner.ch>,
	"gustavo@padovan.org" <gustavo@padovan.org>,
	"marex@denx.de" <marex@denx.de>,
	"sean@poorly.run" <sean@poorly.run>,
	"maarten.lankhorst@linux.intel.com" 
	<maarten.lankhorst@linux.intel.com>
Cc: dl-linux-imx <linux-imx@nxp.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"daniel.vetter@ffwll.ch" <daniel.vetter@ffwll.ch>,
	Robert Chiras <robert.chiras@nxp.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"dri-devel@lists.freedesktop.org"
	<dri-devel@lists.freedesktop.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	Anson Huang <anson.huang@nxp.com>,
	"airlied@linux.ie" <airlied@linux.ie>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [RESEND 0/5] drm/mxsfb: Fix runtime PM for unpowering lcdif block
Date: Thu, 20 Sep 2018 15:59:12 +0000	[thread overview]
Message-ID: <74b9b382ea6f9ec47573955d5b64a597b950cb5b.camel@nxp.com> (raw)
In-Reply-To: <80da134658da77f0d3f8fda6894ab756@agner.ch>

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

  reply	other threads:[~2018-09-20 15:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-17 13:42 Leonard Crestez
2018-09-17 13:42 ` [RESEND 1/5] drm/mxsfb: Move axi clk enable/disable to crtc enable/disable Leonard Crestez
2018-09-17 13:42 ` [RESEND 2/5] drm/mxsfb: Fix initial corrupt frame when activating display Leonard Crestez
2018-09-17 13:42 ` [RESEND 3/5] drm/mxsfb: Add pm_runtime calls to pipe_enable/disable Leonard Crestez
2018-09-17 13:42 ` [RESEND 4/5] drm/mxsfb: Add PM_SLEEP support Leonard Crestez
2018-09-17 13:42 ` [RESEND 5/5] drm/mxsfb: Switch to drm_atomic_helper_commit_tail_rpm Leonard Crestez
2018-09-17 19:16 ` [RESEND 0/5] drm/mxsfb: Fix runtime PM for unpowering lcdif block Sean Paul
2018-09-17 19:34   ` Leonard Crestez
2018-09-17 23:37   ` Stefan Agner
2018-09-20 15:59     ` Leonard Crestez [this message]
2018-09-20 16:39       ` Sean Paul
2018-09-26 20:12         ` Stefan Agner
2018-09-26  8:13 ` Sean Paul
  -- strict thread matches above, loose matches on Subject: below --
2018-08-27 11:10 Leonard Crestez
2018-08-27 12:02 ` Philipp Zabel
2018-09-03 13:51   ` Leonard Crestez

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=74b9b382ea6f9ec47573955d5b64a597b950cb5b.camel@nxp.com \
    --to=leonard.crestez@nxp.com \
    --cc=airlied@linux.ie \
    --cc=anson.huang@nxp.com \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fabio.estevam@nxp.com \
    --cc=gustavo@padovan.org \
    --cc=kernel@pengutronix.de \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maarten.lankhorst@linux.intel.com \
    --cc=marex@denx.de \
    --cc=p.zabel@pengutronix.de \
    --cc=robert.chiras@nxp.com \
    --cc=sean@poorly.run \
    --cc=shawnguo@kernel.org \
    --cc=stefan@agner.ch \
    /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

all inboxes | Powered by JetHome®