From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Kitt <steve@sk2.org>
Cc: David Airlie <airlied@linux.ie>,
Thierry Reding <thierry.reding@gmail.com>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] drm/panel: panel-dsi-cm: Use backlight helpers
Date: Fri, 10 Jun 2022 22:15:01 +0200 [thread overview]
Message-ID: <YqOmRTVGQMXy2HVM@ravnborg.org> (raw)
In-Reply-To: <20220610215606.5c7a97b9@heffalump.sk2.org>
Hi Stephen,
> > > >
> > > > Thanks, I’ll wait a little more to see if there are any other reviews of
> > > > the patches and then push a v2 with that fix.
> > > It would be very nice if you could kill all uses of FB_BLANK in the
> > > drivers/gpu/drm/panel/* drivers, and post them as one series.
> > > This is long overdue to introduce the backlight helpers.
> > >
> > > The three you posted is already a nice step forward, and there may be
> > > more panel drivers I have missed.
> >
> > With this series on top of 5.19-rc1, the only remaining .fb_blank reference
> > is in acx565akm_backlight_init() in panel-sony-acx565akm.c; I was planning
> > on nuking that along with the other .fb_blank initialisers in a series
> > removing .fb_blank entirely from backlight_properties. I’ll add it as a
> > fourth patch for drm/panel if that makes things easier!
>
> That’s in drivers/gpu/drm/panel of course, there are a few others elsewhere
> (I’ve got patches in flight for most of them, I’ve got the rest ready for
> submission).
>
> > There will still be references to FB_BLANK constants since they’re used for
> > backlight_properties.power values. Would it make sense to rename those?
>
> Just to make sure — I’m cleaning up backlight_properties.fb_blank, not
> fb_ops.fb_blank. I wasn’t planning on touching the latter...
Nuking props.fb_blank - that a fine goal - so keep focus there.
We can then later revisit the other clean-up possibilities.
Since you do this tree-wide do not do the mistake and try to cover too
much at the same time, because then you never finish.
So forget my comment for now and keep up the good work on removing
props.fb_blank.
Sam
WARNING: multiple messages have this Message-ID (diff)
From: Sam Ravnborg <sam@ravnborg.org>
To: Stephen Kitt <steve@sk2.org>
Cc: Sebastian Reichel <sebastian.reichel@collabora.com>,
David Airlie <airlied@linux.ie>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Thierry Reding <thierry.reding@gmail.com>
Subject: Re: [PATCH 2/3] drm/panel: panel-dsi-cm: Use backlight helpers
Date: Fri, 10 Jun 2022 22:15:01 +0200 [thread overview]
Message-ID: <YqOmRTVGQMXy2HVM@ravnborg.org> (raw)
In-Reply-To: <20220610215606.5c7a97b9@heffalump.sk2.org>
Hi Stephen,
> > > >
> > > > Thanks, I’ll wait a little more to see if there are any other reviews of
> > > > the patches and then push a v2 with that fix.
> > > It would be very nice if you could kill all uses of FB_BLANK in the
> > > drivers/gpu/drm/panel/* drivers, and post them as one series.
> > > This is long overdue to introduce the backlight helpers.
> > >
> > > The three you posted is already a nice step forward, and there may be
> > > more panel drivers I have missed.
> >
> > With this series on top of 5.19-rc1, the only remaining .fb_blank reference
> > is in acx565akm_backlight_init() in panel-sony-acx565akm.c; I was planning
> > on nuking that along with the other .fb_blank initialisers in a series
> > removing .fb_blank entirely from backlight_properties. I’ll add it as a
> > fourth patch for drm/panel if that makes things easier!
>
> That’s in drivers/gpu/drm/panel of course, there are a few others elsewhere
> (I’ve got patches in flight for most of them, I’ve got the rest ready for
> submission).
>
> > There will still be references to FB_BLANK constants since they’re used for
> > backlight_properties.power values. Would it make sense to rename those?
>
> Just to make sure — I’m cleaning up backlight_properties.fb_blank, not
> fb_ops.fb_blank. I wasn’t planning on touching the latter...
Nuking props.fb_blank - that a fine goal - so keep focus there.
We can then later revisit the other clean-up possibilities.
Since you do this tree-wide do not do the mistake and try to cover too
much at the same time, because then you never finish.
So forget my comment for now and keep up the good work on removing
props.fb_blank.
Sam
next prev parent reply other threads:[~2022-06-10 20:15 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-07 18:20 [PATCH 0/3] drm/panel: Use backlight helpers Stephen Kitt
2022-06-07 18:20 ` Stephen Kitt
2022-06-07 18:20 ` [PATCH 1/3] drm/panel: Use backlight helper Stephen Kitt
2022-06-07 18:20 ` Stephen Kitt
2022-06-07 18:20 ` [PATCH 2/3] drm/panel: panel-dsi-cm: Use backlight helpers Stephen Kitt
2022-06-07 18:20 ` Stephen Kitt
2022-06-09 21:52 ` Sebastian Reichel
2022-06-09 21:52 ` Sebastian Reichel
2022-06-10 17:47 ` Stephen Kitt
2022-06-10 17:47 ` Stephen Kitt
2022-06-10 19:28 ` Sam Ravnborg
2022-06-10 19:28 ` Sam Ravnborg
2022-06-10 19:52 ` Stephen Kitt
2022-06-10 19:52 ` Stephen Kitt
2022-06-10 19:56 ` Stephen Kitt
2022-06-10 19:56 ` Stephen Kitt
2022-06-10 20:15 ` Sam Ravnborg [this message]
2022-06-10 20:15 ` Sam Ravnborg
2022-06-07 18:20 ` [PATCH 3/3] drm/panel: sony-acx565akm: " Stephen Kitt
2022-06-07 18:20 ` Stephen Kitt
2022-06-09 21:54 ` Sebastian Reichel
2022-06-09 21:54 ` Sebastian Reichel
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=YqOmRTVGQMXy2HVM@ravnborg.org \
--to=sam@ravnborg.org \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=steve@sk2.org \
--cc=thierry.reding@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.