From: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
David Airlie <airlied@gmail.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Daniel Vetter <daniel@ffwll.ch>,
linux-renesas-soc@vger.kernel.org,
dri-devel@lists.freedesktop.org
Subject: Re: [PATCH v2 0/5] drm: shmobile: Fixes and enhancements
Date: Tue, 18 Apr 2023 11:09:28 +0300 [thread overview]
Message-ID: <20230418080928.GA30837@pendragon.ideasonboard.com> (raw)
In-Reply-To: <CAMuHMdUqKCokNc-phYFoGKa0vFwCMDdy7RZ-kn6F8yqkvtfkfA@mail.gmail.com>
Hi Geert,
On Tue, Apr 18, 2023 at 10:00:35AM +0200, Geert Uytterhoeven wrote:
> On Tue, Apr 18, 2023 at 9:49 AM Laurent Pinchart wrote:
> > On Mon, Apr 17, 2023 at 03:40:20PM +0200, Geert Uytterhoeven wrote:
> > > Currently, there are two drivers for the LCD controller on Renesas
> > > SuperH-based and ARM-based SH-Mobile and R-Mobile SoCs:
> > > 1. sh_mobile_lcdcfb, using the fbdev framework,
> > > 2. shmob_drm, using the DRM framework.
> > > However, only the former driver can be used, as all platform support
> > > integrates the former. None of these drivers support DT-based systems.
> > >
> > > This patch series is a first step to enable the SH-Mobile DRM driver for
> > > Renesas ARM-based SH-Mobile and R-Mobile SoCs. The next step planned is
> > > to add DT support.
> > >
> > > Changes compared to v1:
> > > - Add Reviewed-by,
> > > - Drop dependency on ARM.
> > >
> > > This has been tested on the R-Mobile A1-based Atmark Techno
> > > Armadillo-800-EVA development board, using a temporary
> > > platform-enablement patch[1].
> > >
> > > Thanks for applying to drm-misc!
> >
> > Would you like to request drm-misc committer rights ? :-)
>
> Don't the listed maintainers for drivers/gpu/drm/shmobile/ don't
> have such access already?
Actually, as you're taking over maintenance for this driver, would you
send a patch to update MAINTAINERS ?
--
Regards,
Laurent Pinchart
prev parent reply other threads:[~2023-04-18 8:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-17 13:40 [PATCH v2 0/5] drm: shmobile: Fixes and enhancements Geert Uytterhoeven
2023-04-17 13:40 ` [PATCH v2 1/5] drm: shmobile: Use %p4cc to print fourcc codes Geert Uytterhoeven
2023-04-18 7:46 ` Laurent Pinchart
2023-04-17 13:40 ` [PATCH v2 2/5] drm: shmobile: Add support for DRM_FORMAT_XRGB8888 Geert Uytterhoeven
2023-04-17 13:40 ` [PATCH v2 3/5] drm: shmobile: Switch to drm_crtc_init_with_planes() Geert Uytterhoeven
2023-04-17 13:40 ` [PATCH v2 4/5] drm: shmobile: Add missing call to drm_fbdev_generic_setup() Geert Uytterhoeven
2023-04-17 13:40 ` [PATCH v2 5/5] drm: shmobile: Make DRM_SHMOBILE visible on Renesas SoC platforms Geert Uytterhoeven
2023-04-18 7:50 ` [PATCH v2 0/5] drm: shmobile: Fixes and enhancements Laurent Pinchart
2023-04-18 8:00 ` Geert Uytterhoeven
2023-04-18 8:09 ` Laurent Pinchart [this message]
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=20230418080928.GA30837@pendragon.ideasonboard.com \
--to=laurent.pinchart@ideasonboard.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=tzimmermann@suse.de \
/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