From: Thomas Zimmermann <tzimmermann@suse.de>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v3 0/5] drm: shmobile: Fixes and enhancements
Date: Wed, 24 May 2023 14:02:59 +0200 [thread overview]
Message-ID: <35df2c16-6e5b-bc8a-e65c-9244a815dcbd@suse.de> (raw)
In-Reply-To: <CAMuHMdXPJ02UWuH1v_ZaoWmbHALu0Qe2K27nhuvwKBmjno+YMw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1697 bytes --]
Am 24.05.23 um 13:54 schrieb Geert Uytterhoeven:
> Hi Thomas,
>
> On Wed, May 24, 2023 at 1:42 PM Thomas Zimmermann <tzimmermann@suse.de> wrote:
>> Am 23.05.23 um 17:31 schrieb Geert Uytterhoeven:
>>> 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 steps planned are
>>> to (1) add DT support (works, but needs a hack due to lack of (2)), and (2)
>>> convert the driver to atomic modesetting.
>>>
>>> Changes compared to v2[1]:
>>> - Add Reviewed-by.
>>>
>>> Changes compared to v1[2]:
>>> - 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[3].
>>>
>>> Thanks for applying to drm-misc!
>>
>> It's all been reviewed. Do you want me to merge the patchset?
>
> That would be great! Thanks!
Done. Thanks for the patches.
>
> Gr{oetje,eeting}s,
>
> Geert
>
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstrasse 146, 90461 Nuernberg, Germany
GF: Ivo Totev, Andrew Myers, Andrew McDonald, Boudien Moerman
HRB 36809 (AG Nuernberg)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
prev parent reply other threads:[~2023-05-24 12:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 15:31 Geert Uytterhoeven
2023-05-23 15:31 ` [PATCH v3 1/5] drm: shmobile: Use %p4cc to print fourcc codes Geert Uytterhoeven
2023-05-23 15:31 ` [PATCH v3 2/5] drm: shmobile: Add support for DRM_FORMAT_XRGB8888 Geert Uytterhoeven
2023-05-23 15:31 ` [PATCH v3 3/5] drm: shmobile: Switch to drm_crtc_init_with_planes() Geert Uytterhoeven
2023-05-23 15:31 ` [PATCH v3 4/5] drm: shmobile: Add missing call to drm_fbdev_generic_setup() Geert Uytterhoeven
2023-05-23 15:31 ` [PATCH v3 5/5] drm: shmobile: Make DRM_SHMOBILE visible on Renesas SoC platforms Geert Uytterhoeven
2023-05-24 11:42 ` [PATCH v3 0/5] drm: shmobile: Fixes and enhancements Thomas Zimmermann
2023-05-24 11:54 ` Geert Uytterhoeven
2023-05-24 12:02 ` Thomas Zimmermann [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=35df2c16-6e5b-bc8a-e65c-9244a815dcbd@suse.de \
--to=tzimmermann@suse.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=geert@linux-m68k.org \
--cc=kieran.bingham+renesas@ideasonboard.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
/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®