Re: [PATCH 0/5] drm: shmobile: Fixes and enhancements
Hi Geert, On Fri, Mar 31, 2023 at 04:48:06PM +0200, Geert Uytterhoeven wrote: > Hi all, > > 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. > > 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 your comments! Thanks for reviving this driver. I'm looking forward to DT and KMS atomic support :-) Will you get these patches merged through drm-misc ? > [1] > https://lore.kernel.org/r/c03d4edbd650836bf6a96504df82338ec6d800ff.1680272980.git.geert+rene...@glider.be > > Geert Uytterhoeven (5): > drm: shmobile: Use %p4cc to print fourcc codes > drm: shmobile: Add support for DRM_FORMAT_XRGB > drm: shmobile: Switch to drm_crtc_init_with_planes() > drm: shmobile: Add missing call to drm_fbdev_generic_setup() > drm: shmobile: Make DRM_SHMOBILE visible on Renesas SoC platforms > > drivers/gpu/drm/shmobile/Kconfig | 2 +- > drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 35 +++--- > drivers/gpu/drm/shmobile/shmob_drm_drv.c | 3 ++ > drivers/gpu/drm/shmobile/shmob_drm_kms.c | 9 -- > drivers/gpu/drm/shmobile/shmob_drm_plane.c | 5 > 5 files changed, 47 insertions(+), 7 deletions(-) -- Regards, Laurent Pinchart
Re: [PATCH 0/5] drm: shmobile: Fixes and enhancements
Hi Thomas,
On Mon, Apr 3, 2023 at 3:14 PM Thomas Zimmermann wrote:
> Am 31.03.23 um 16:48 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 step planned is
> > to add DT support.
> >
> > This has been tested on the R-Mobile A1-based Atmark Techno
> > Armadillo-800-EVA development board, using a temporary
> > platform-enablement patch[1].
>
> Since you have the hardware for shmobile, would you be able to test
> patches occasionally?
Sure!
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
Re: [PATCH 0/5] drm: shmobile: Fixes and enhancements
Hi Geert Am 31.03.23 um 16:48 schrieb Geert Uytterhoeven: Hi all, 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. This has been tested on the R-Mobile A1-based Atmark Techno Armadillo-800-EVA development board, using a temporary platform-enablement patch[1]. Since you have the hardware for shmobile, would you be able to test patches occasionally? Best regards Thomas Thanks for your comments! [1] https://lore.kernel.org/r/c03d4edbd650836bf6a96504df82338ec6d800ff.1680272980.git.geert+rene...@glider.be Geert Uytterhoeven (5): drm: shmobile: Use %p4cc to print fourcc codes drm: shmobile: Add support for DRM_FORMAT_XRGB drm: shmobile: Switch to drm_crtc_init_with_planes() drm: shmobile: Add missing call to drm_fbdev_generic_setup() drm: shmobile: Make DRM_SHMOBILE visible on Renesas SoC platforms drivers/gpu/drm/shmobile/Kconfig | 2 +- drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 35 +++--- drivers/gpu/drm/shmobile/shmob_drm_drv.c | 3 ++ drivers/gpu/drm/shmobile/shmob_drm_kms.c | 9 -- drivers/gpu/drm/shmobile/shmob_drm_plane.c | 5 5 files changed, 47 insertions(+), 7 deletions(-) -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev OpenPGP_signature Description: OpenPGP digital signature
Re: [PATCH 0/5] drm: shmobile: Fixes and enhancements
Hi Reviewed-by: Thomas Zimmermann for the whole patchset. Best regards Thomas Am 31.03.23 um 16:48 schrieb Geert Uytterhoeven: Hi all, 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. 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 your comments! [1] https://lore.kernel.org/r/c03d4edbd650836bf6a96504df82338ec6d800ff.1680272980.git.geert+rene...@glider.be Geert Uytterhoeven (5): drm: shmobile: Use %p4cc to print fourcc codes drm: shmobile: Add support for DRM_FORMAT_XRGB drm: shmobile: Switch to drm_crtc_init_with_planes() drm: shmobile: Add missing call to drm_fbdev_generic_setup() drm: shmobile: Make DRM_SHMOBILE visible on Renesas SoC platforms drivers/gpu/drm/shmobile/Kconfig | 2 +- drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 35 +++--- drivers/gpu/drm/shmobile/shmob_drm_drv.c | 3 ++ drivers/gpu/drm/shmobile/shmob_drm_kms.c | 9 -- drivers/gpu/drm/shmobile/shmob_drm_plane.c | 5 5 files changed, 47 insertions(+), 7 deletions(-) -- Thomas Zimmermann Graphics Driver Developer SUSE Software Solutions Germany GmbH Maxfeldstr. 5, 90409 Nürnberg, Germany (HRB 36809, AG Nürnberg) Geschäftsführer: Ivo Totev OpenPGP_signature Description: OpenPGP digital signature
[PATCH 0/5] drm: shmobile: Fixes and enhancements
Hi all,
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.
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 your comments!
[1]
https://lore.kernel.org/r/c03d4edbd650836bf6a96504df82338ec6d800ff.1680272980.git.geert+rene...@glider.be
Geert Uytterhoeven (5):
drm: shmobile: Use %p4cc to print fourcc codes
drm: shmobile: Add support for DRM_FORMAT_XRGB
drm: shmobile: Switch to drm_crtc_init_with_planes()
drm: shmobile: Add missing call to drm_fbdev_generic_setup()
drm: shmobile: Make DRM_SHMOBILE visible on Renesas SoC platforms
drivers/gpu/drm/shmobile/Kconfig | 2 +-
drivers/gpu/drm/shmobile/shmob_drm_crtc.c | 35 +++---
drivers/gpu/drm/shmobile/shmob_drm_drv.c | 3 ++
drivers/gpu/drm/shmobile/shmob_drm_kms.c | 9 --
drivers/gpu/drm/shmobile/shmob_drm_plane.c | 5
5 files changed, 47 insertions(+), 7 deletions(-)
--
2.34.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
