mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>
To: Javier Martinez Canillas <javierm@redhat.com>,
	dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Cc: Javier Martinez Canillas <javierm@redhat.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH v2 31/37] drm: rcar-du: Add support for the nomodeset kernel parameter
Date: Fri, 28 Jan 2022 09:13:36 +0000	[thread overview]
Message-ID: <164336121612.533872.1685181669511488706@Monstersaurus> (raw)
In-Reply-To: <20211217003752.3946210-32-javierm@redhat.com>

Hi Javier,

Quoting Javier Martinez Canillas (2021-12-17 00:37:46)
> According to disable Documentation/admin-guide/kernel-parameters.txt, this
> parameter can be used to disable kernel modesetting.
> 
> DRM drivers will not perform display-mode changes or accelerated rendering
> and only the system framebuffer will be available if it was set-up.

What is the 'system framebuffer' in this instance? Reading
https://www.kernel.org/doc/Documentation/admin-guide/kernel-parameters.txt
it sounds like that means anything already set up by the bootloader.

> But only a few DRM drivers currently check for nomodeset, make this driver
> to also support the command line parameter.
> 
> Signed-off-by: Javier Martinez Canillas <javierm@redhat.com>
> ---
> 
> (no changes since v1)
> 
>  drivers/gpu/drm/rcar-du/rcar_du_drv.c | 3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/drivers/gpu/drm/rcar-du/rcar_du_drv.c b/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> index 5a8131ef81d5..982e450233ed 100644
> --- a/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> +++ b/drivers/gpu/drm/rcar-du/rcar_du_drv.c
> @@ -701,6 +701,9 @@ static struct platform_driver rcar_du_platform_driver = {
>  
>  static int __init rcar_du_init(void)
>  {
> +       if (drm_firmware_drivers_only())
> +               return -ENODEV;
> +

This will completely disable all control of the display device when
nomodeset is enabled.

Is there any requirement for us to support outputting to the display if
it was previously set up? presumably without setting or changing any
modes, but simply allowing the existing frame to be updated?

I think the implication is that 'firmware drivers' would mean a display
could be updated through some firmware interface, which we won't have
... so it seems reasonable to accept that this whole driver can be
disabled in that instance.

Reading your mail that brought this thread up in my inbox, I think
you've already hit merge on this, so don't worry about adding a tag in
that instance, but I think this is ok.

Reviewed-by: Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>

>         rcar_du_of_init(rcar_du_of_table);
>  
>         return platform_driver_register(&rcar_du_platform_driver);
> -- 
> 2.33.1
>

  reply	other threads:[~2022-01-28  9:13 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-17  0:37 [PATCH v2 00/37] drm: Make drivers to honour the nomodeset parameter Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 01/37] drm: Add drm_module_{pci,platform}_driver() helper macros Javier Martinez Canillas
2021-12-17 14:31   ` Thomas Zimmermann
2021-12-17  0:37 ` [PATCH v2 02/37] drm/hisilicon/hibmc: Use drm_module_pci_driver() to register the driver Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 03/37] drm/komeda: Use drm_module_platform_driver() " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 04/37] drm/arm/hdlcd: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 05/37] drm/malidp: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 06/37] drm/aspeed: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 07/37] drm/atmel-hlcdc: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 08/37] drm/fsl-dcu: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 09/37] drm/hisilicon/kirin: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 10/37] drm/imx/dcss: " Javier Martinez Canillas
2021-12-17 15:58   ` kernel test robot
2021-12-17  0:37 ` [PATCH v2 11/37] drm/kmb: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 12/37] drm/meson: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 13/37] drm: mxsfb: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 14/37] drm/shmobile: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 15/37] drm/stm: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 16/37] drm/sun4i: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 17/37] drm/tidss: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 18/37] drm/arc: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 19/37] drm/tve200: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 20/37] drm/xlnx: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 21/37] drm/armada: Add support for the nomodeset kernel parameter Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 22/37] drm/exynos: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 23/37] drm/gma500: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 24/37] drm/hyperv: " Javier Martinez Canillas
2021-12-20 17:10   ` Deepak Rawat
2021-12-17  0:37 ` [PATCH v2 25/37] drm/imx: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 26/37] drm/ingenic: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 27/37] drm/mcde: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 28/37] drm/mediatek: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 29/37] drm/msm: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 30/37] drm/omap: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 31/37] drm: rcar-du: " Javier Martinez Canillas
2022-01-28  9:13   ` Kieran Bingham [this message]
2022-01-28  9:33     ` Thomas Zimmermann
2022-01-28 10:34       ` Laurent Pinchart
2022-01-28 10:46         ` Thomas Zimmermann
2022-01-28 11:04           ` Laurent Pinchart
2022-01-28 11:26             ` Thomas Zimmermann
2022-01-28 11:36               ` Laurent Pinchart
2022-01-28 11:53                 ` Thomas Zimmermann
2022-01-28 11:09           ` Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 32/37] drm/rockchip: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 33/37] drm/sprd: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 34/37] drm/sti: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 35/37] drm/tegra: " Javier Martinez Canillas
2021-12-17  0:37 ` [PATCH v2 36/37] drm/tilcdc: " Javier Martinez Canillas
2021-12-17 13:30   ` Jyri Sarha
2021-12-17  0:37 ` [PATCH v2 37/37] drm/xen: " Javier Martinez Canillas
2022-01-27 18:29 ` [PATCH v2 00/37] drm: Make drivers to honour the nomodeset parameter Javier Martinez Canillas

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=164336121612.533872.1685181669511488706@Monstersaurus \
    --to=kieran.bingham+renesas@ideasonboard.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=javierm@redhat.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-kernel@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®