From: Sean Paul <sean@poorly.run>
To: Sam Ravnborg <sam@ravnborg.org>
Cc: Thierry Reding <thierry.reding@gmail.com>,
dri-devel@lists.freedesktop.org, Daniel Vetter <daniel@ffwll.ch>,
David Airlie <airlied@linux.ie>,
Linus Walleij <linus.walleij@linaro.org>,
Stefan Mavrodiev <stefan@olimex.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1 0/19] drm/panel: drmP.h removal and DRM_DEV*
Date: Thu, 31 Jan 2019 15:07:23 -0500 [thread overview]
Message-ID: <20190131200723.GZ114153@art_vandelay> (raw)
In-Reply-To: <20190131192619.9763-1-sam@ravnborg.org>
On Thu, Jan 31, 2019 at 08:26:00PM +0100, Sam Ravnborg wrote:
> Hi Thierry et al.
>
> While reviewing a number of new panel drivers there was a
> certain pattern in the feedback:
> - the now deprecated drmP.h file was used
> - dev_err() and friends was used
>
> This patch-set address the above items in the panel
> drivers in drm/panel/
> The hope is that new panel drivers will no longer inherit bad
> patterns from the existing drivers.
>
> The use of DRM_DEV* is not accepted by everyone, so this conversion
> was split up in smaller bits.
> If some drivers do not want to use DRM_DEV* then just drop the relevant patch.
>
> All patches are build tested on x86/arm.
>
> The DRM_DEV* patches depends on the drmP.h removal.
>
> One extra patch sneaked in "panel-innolux: drop unused variable"
> This is a fix for an unused variable and was added to flush my panel patches.
>
> Note: Waiting for key storage (for gpg key) before I start the process getting
> commit rights, so I rely on someone else (Thierry?) to commit this.
>
> Patches are made on top of drm-misc-next as of a few days ago.
>
> Comments welcome!
Hey Sam,
Thanks for the patchset, this will make dmesg grepping easier! One comment, and
you're going to hate me for it: Why use DRM_DEV* instead of DRM_*?
When I introduced DRM_DEV, it was to cover the case where there are multiple
instances of the same driver (ie: dual-channel mipi, multiple crtcs, etc). I
suppose that _could_ happen in the panel space, but it seems more unlikely than
not.
It's quite possible I'm overthinking this, but just something I figured I would
point out. Either way, I think this is an improvement over dev_*.
Sean
>
> Sam
>
> Sam Ravnborg (19):
> drm/panel: drop drmP.h usage
> drm/panel: panel-innolux: drop unused variable
> drm/panel: samsung: use DRM_DEV*
> drm/panel: arm-versatile: use DRM_DEV*
> drm/panel: truly: use DRM_DEV*
> drm/panel: sitronix: use DRM_DEV*
> drm/panel: ilitek: use DRM_DEV*
> drm/panel: innolux: use DRM_DEV*
> drm/panel: jdi: use DRM_DEV*
> drm/panel: lg: use DRM_DEV*
> drm/panel: lvds: use DRM_DEV*
> drm/panel: olimex: use DRM_DEV*
> drm/panel: orisetech: use DRM_DEV*
> drm/panel: panasonic: use DRM_DEV*
> drm/panel: raspberrypi: use DRM_DEV*
> drm/panel: raydium: use DRM_DEV*
> drm/panel: seiko: use DRM_DEV*
> drm/panel: sharp: use DRM_DEV*
> drm/panel: simple: use DRM_DEV*
>
> drivers/gpu/drm/panel/panel-arm-versatile.c | 21 +++--
> drivers/gpu/drm/panel/panel-ilitek-ili9322.c | 97 ++++++++++++----------
> drivers/gpu/drm/panel/panel-ilitek-ili9881c.c | 14 ++--
> drivers/gpu/drm/panel/panel-innolux-p079zca.c | 17 ++--
> drivers/gpu/drm/panel/panel-jdi-lt070me05000.c | 66 ++++++++-------
> drivers/gpu/drm/panel/panel-kingdisplay-kd097d04.c | 4 +-
> drivers/gpu/drm/panel/panel-lg-lg4573.c | 25 +++---
> drivers/gpu/drm/panel/panel-lvds.c | 39 +++++----
> drivers/gpu/drm/panel/panel-olimex-lcd-olinuxino.c | 28 ++++---
> drivers/gpu/drm/panel/panel-orisetech-otm8009a.c | 15 ++--
> .../gpu/drm/panel/panel-panasonic-vvx10f034n00.c | 19 +++--
> .../gpu/drm/panel/panel-raspberrypi-touchscreen.c | 25 +++---
> drivers/gpu/drm/panel/panel-raydium-rm68200.c | 11 ++-
> drivers/gpu/drm/panel/panel-samsung-ld9040.c | 18 ++--
> drivers/gpu/drm/panel/panel-samsung-s6e3ha2.c | 21 +++--
> drivers/gpu/drm/panel/panel-samsung-s6e63j0x03.c | 15 ++--
> drivers/gpu/drm/panel/panel-samsung-s6e8aa0.c | 32 ++++---
> drivers/gpu/drm/panel/panel-seiko-43wvf1g.c | 18 ++--
> drivers/gpu/drm/panel/panel-sharp-lq101r1sx01.c | 66 ++++++++++-----
> drivers/gpu/drm/panel/panel-sharp-ls043t1le01.c | 27 +++---
> drivers/gpu/drm/panel/panel-simple.c | 22 +++--
> drivers/gpu/drm/panel/panel-sitronix-st7789v.c | 16 ++--
> drivers/gpu/drm/panel/panel-truly-nt35597.c | 10 ++-
> 23 files changed, 375 insertions(+), 251 deletions(-)
--
Sean Paul, Software Engineer, Google / Chromium OS
next prev parent reply other threads:[~2019-01-31 20:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-31 19:26 [PATCH v1 0/19] drm/panel: drmP.h removal and DRM_DEV* Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 01/19] drm/panel: drop drmP.h usage Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 02/19] drm/panel: panel-innolux: drop unused variable Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 03/19] drm/panel: samsung: use DRM_DEV* Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 04/19] drm/panel: arm-versatile: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 05/19] drm/panel: truly: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 06/19] drm/panel: sitronix: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 07/19] drm/panel: ilitek: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 08/19] drm/panel: innolux: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 09/19] drm/panel: jdi: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 10/19] drm/panel: lg: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 11/19] drm/panel: lvds: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 12/19] drm/panel: olimex: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 13/19] drm/panel: orisetech: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 14/19] drm/panel: panasonic: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 15/19] drm/panel: raspberrypi: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 16/19] drm/panel: raydium: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 17/19] drm/panel: seiko: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 18/19] drm/panel: sharp: " Sam Ravnborg
2019-01-31 19:26 ` [PATCH v1 19/19] drm/panel: simple: " Sam Ravnborg
2019-01-31 19:33 ` [PATCH v1 0/19] drm/panel: drmP.h removal and DRM_DEV* Sam Ravnborg
2019-01-31 20:07 ` Sean Paul [this message]
2019-01-31 21:03 ` Sam Ravnborg
2019-01-31 21:54 ` Thierry Reding
2019-02-01 9:20 ` Sam Ravnborg
2019-02-01 10:30 ` Jani Nikula
2019-02-01 10:52 ` Andrzej Hajda
2019-02-01 11:13 ` Jani Nikula
2019-02-01 13:37 ` Sam Ravnborg
2019-02-02 1:31 ` Joe Perches
2019-02-04 18:42 ` Sam Ravnborg
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=20190131200723.GZ114153@art_vandelay \
--to=sean@poorly.run \
--cc=airlied@linux.ie \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=stefan@olimex.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox