From: Javier Martinez Canillas <javier@dowhile0.org>
To: Maxime Ripard <maxime@cerno.tech>
Cc: 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>,
Scott Branden <sbranden@broadcom.com>,
Rob Herring <robh+dt@kernel.org>,
Frank Rowand <frowand.list@gmail.com>,
devicetree@vger.kernel.org, Dom Cobley <dom@raspberrypi.com>,
Tim Gover <tim.gover@raspberrypi.com>,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
bcm-kernel-feedback-list@broadcom.com,
linux-rpi-kernel@lists.infradead.org,
Phil Elwell <phil@raspberrypi.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RESEND v4 v5 4/4] drm/vc4: Notify the firmware when DRM is in charge
Date: Tue, 11 Jan 2022 10:26:42 +0100 [thread overview]
Message-ID: <CABxcv=mseT4o71HYKETiezZ2FDFvvf=Aw+jpuOE98dVWdvwLzw@mail.gmail.com> (raw)
In-Reply-To: <20211215095117.176435-5-maxime@cerno.tech>
Hello Maxime,
On Wed, Dec 15, 2021 at 10:51 AM Maxime Ripard <maxime@cerno.tech> wrote:
>
> Once the call to drm_fb_helper_remove_conflicting_framebuffers() has
> been made, simplefb has been unregistered and the KMS driver is entirely
> in charge of the display.
>
> Thus, we can notify the firmware it can free whatever resource it was
> using to maintain simplefb functional.
>
> Signed-off-by: Maxime Ripard <maxime@cerno.tech>
> ---
Patch looks good to me.
Reviewed-by: Javier Martinez Canillas <javierm@redhat.com>
Best regards,
Javier
next prev parent reply other threads:[~2022-01-11 9:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-15 9:51 [PATCH RESEND v4 v5 0/4] drm/vc4: Use the firmware to stop the display pipeline Maxime Ripard
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 [this message]
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='CABxcv=mseT4o71HYKETiezZ2FDFvvf=Aw+jpuOE98dVWdvwLzw@mail.gmail.com' \
--to=javier@dowhile0.org \
--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=maxime@cerno.tech \
--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).