From: Maxime Ripard <maxime@cerno.tech>
To: Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Nicolas Saenz Julienne <nsaenz@kernel.org>,
Daniel Vetter <daniel.vetter@intel.com>,
David Airlie <airlied@linux.ie>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
Maxime Ripard <maxime@cerno.tech>,
Scott Branden <sbranden@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>
Cc: bcm-kernel-feedback-list@broadcom.com,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Phil Elwell <phil@raspberrypi.com>,
Tim Gover <tim.gover@raspberrypi.com>,
Dom Cobley <dom@raspberrypi.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND v4 v5 0/4] drm/vc4: Use the firmware to stop the display pipeline
Date: Wed, 15 Dec 2021 10:51:13 +0100 [thread overview]
Message-ID: <20211215095117.176435-1-maxime@cerno.tech> (raw)
Hi,
The VC4 driver has had limited support to disable the HDMI controllers and
pixelvalves at boot if the firmware has enabled them.
However, this proved to be limited, and a bit unreliable so a new firmware
command has been introduced some time ago to make it free all its resources and
disable any display output it might have enabled.
This series takes advantage of that command to call it once the transition from
simplefb to the KMS driver has been done.
Let me know what you think,
Maxime
---
Changes from v4:
- Don't register v3d with nomodeset
Changes from v3:
- Support nomodeset
Changes from v2:
- Switch back to rpi_firmware_get / rpi_firmware_put
- Moved the rpi_firmware pointer to a local variable
Changes from v1:
- Use of_find_compatible_node instead of a phandle
- Use devm_rpi_firmware_get
Maxime Ripard (4):
firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE
drm/vc4: Support nomodeset
drm/vc4: Remove conflicting framebuffers before callind bind_all
drm/vc4: Notify the firmware when DRM is in charge
drivers/gpu/drm/vc4/vc4_drv.c | 33 +++++++++++++++++++---
include/soc/bcm2835/raspberrypi-firmware.h | 1 +
2 files changed, 30 insertions(+), 4 deletions(-)
--
2.33.1
next reply other threads:[~2021-12-15 9:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 9:51 Maxime Ripard [this message]
2021-12-15 9:51 ` [PATCH RESEND v4 v5 1/4] firmware: raspberrypi: Add RPI_FIRMWARE_NOTIFY_DISPLAY_DONE Maxime Ripard
2021-12-15 9:51 ` [PATCH RESEND v4 v5 2/4] drm/vc4: Support nomodeset Maxime Ripard
2021-12-15 10:08 ` Thomas Zimmermann
2021-12-15 9:51 ` [PATCH RESEND v4 v5 3/4] drm/vc4: Remove conflicting framebuffers before callind bind_all Maxime Ripard
2021-12-15 9:51 ` [PATCH RESEND v4 v5 4/4] drm/vc4: Notify the firmware when DRM is in charge Maxime Ripard
2022-01-11 9:26 ` Javier Martinez Canillas
2022-01-11 9:38 ` Thomas Zimmermann
2022-01-11 13:01 ` Maxime Ripard
2021-12-15 9:57 ` [PATCH RESEND v4 v5 0/4] drm/vc4: Use the firmware to stop the display pipeline Maxime Ripard
2022-01-11 12:54 ` Maxime Ripard
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=20211215095117.176435-1-maxime@cerno.tech \
--to=maxime@cerno.tech \
--cc=airlied@linux.ie \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=daniel.vetter@intel.com \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=dom@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=f.fainelli@gmail.com \
--cc=frowand.list@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=nsaenz@kernel.org \
--cc=phil@raspberrypi.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=tim.gover@raspberrypi.com \
--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;
as well as URLs for NNTP newsgroup(s).