From: nicolas saenz julienne <nsaenz@kernel.org>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>,
Peter Robinson <pbrobinson@gmail.com>,
Arnd Bergmann <arnd@arndb.de>,
bcm-kernel-feedback-list@broadcom.com,
Daniel Vetter <daniel@ffwll.ch>, David Airlie <airlied@linux.ie>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
Emma Anholt <emma@anholt.net>,
Florian Fainelli <f.fainelli@gmail.com>,
javierm@redhat.com, linux-arm-kernel@lists.infradead.org,
linux-rpi-kernel@lists.infradead.org, maxime@cerno.tech,
Rob Herring <robh+dt@kernel.org>,
Stefan Wahren <stefan.wahren@i2se.com>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>
Subject: Re: [PATCH v5 2/6] drm/v3d: Get rid of pm code
Date: Fri, 03 Jun 2022 09:07:26 +0200 [thread overview]
Message-ID: <5550435a41ca9ec190015ce1b872be85edcd71b7.camel@kernel.org> (raw)
In-Reply-To: <20220601110249.569540-3-pbrobinson@gmail.com>
On Wed, 2022-06-01 at 12:02 +0100, Peter Robinson wrote:
> Runtime PM doesn't seem to work correctly on this driver. On top of
> that, commit 8b6864e3e138 ("drm/v3d/v3d_drv: Remove unused static
> variable 'v3d_v3d_pm_ops'") hints that it most likely never did as the
> driver's PM ops were not hooked-up.
>
> So, in order to support regular operation with V3D on BCM2711 (Raspberry
> Pi 4), get rid of the PM code. PM will be reinstated once we figure out
> the underlying issues.
>
> Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> Signed-off-by: Peter Robinson <pbrobinson@gmail.com>
> ---
Hi Florian, any thoughts on this?
Are brcm,7268-v3d and brcm,7278-v3d using runtime PM downstream?
Nicolas
next prev parent reply other threads:[~2022-06-03 7:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-01 11:02 [PATCH v5 0/6] Raspberry PI 4 V3D enablement Peter Robinson
2022-06-01 11:02 ` [PATCH v5 1/6] dt-bindings: gpu: v3d: Add BCM2711's compatible Peter Robinson
2022-06-02 11:58 ` Stefan Wahren
2022-06-02 14:49 ` Rob Herring
2022-06-02 22:56 ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 2/6] drm/v3d: Get rid of pm code Peter Robinson
2022-06-02 22:59 ` Javier Martinez Canillas
2022-06-03 7:07 ` nicolas saenz julienne [this message]
2022-06-01 11:02 ` [PATCH v5 3/6] drm/v3d: Add support for bcm2711 Peter Robinson
2022-06-02 12:00 ` Stefan Wahren
2022-06-02 23:05 ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 4/6] ARM: dts: bcm2711: Enable V3D Peter Robinson
2022-06-02 12:04 ` Stefan Wahren
2022-06-02 13:32 ` Peter Robinson
2022-06-02 23:07 ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 5/6] ARM: configs: Enable DRM_V3D Peter Robinson
2022-06-02 11:48 ` Stefan Wahren
2022-06-02 23:09 ` Javier Martinez Canillas
2022-06-01 11:02 ` [PATCH v5 6/6] arm64: config: " Peter Robinson
2022-06-02 12:05 ` Stefan Wahren
2022-06-02 23:10 ` 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=5550435a41ca9ec190015ce1b872be85edcd71b7.camel@kernel.org \
--to=nsaenz@kernel.org \
--cc=airlied@linux.ie \
--cc=arnd@arndb.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=catalin.marinas@arm.com \
--cc=daniel@ffwll.ch \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=emma@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=javierm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=maxime@cerno.tech \
--cc=nsaenzjulienne@suse.de \
--cc=pbrobinson@gmail.com \
--cc=robh+dt@kernel.org \
--cc=stefan.wahren@i2se.com \
--cc=will@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;
as well as URLs for NNTP newsgroup(s).