From: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
To: Stefan Wahren <stefan.wahren@i2se.com>,
Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Eric Anholt <eric@anholt.net>
Cc: devicetree@vger.kernel.org, wahrenst@gmx.net,
linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D
Date: Tue, 03 Mar 2020 19:37:17 +0100 [thread overview]
Message-ID: <03fcb1e2bc7f3ff389b6dfbf3964e159a93ae835.camel@suse.de> (raw)
In-Reply-To: <736f0c59-352b-03b2-f77f-bfc22171b3fb@i2se.com>
[-- Attachment #1.1: Type: text/plain, Size: 1036 bytes --]
On Tue, 2020-03-03 at 19:17 +0100, Stefan Wahren wrote:
> Hi Nicolas,
>
> Am 03.03.20 um 18:32 schrieb Nicolas Saenz Julienne:
> > The register based driver turned out to be unstable, specially on RPi3a+
> > but not limited to it. While a fix is being worked on, we roll back to
> > using firmware based scheme.
> >
> > Fixes: e1dc2b2e1bef ("ARM: bcm283x: Switch V3D over to using the PM driver
> > instead of firmware")
> > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> > ---
> >
> > See https://github.com/raspberrypi/linux/issues/3046 for more reference.
> > Note: I tested this on RPi3b, RPi3a+ and RPi2b.
>
> as i already wrote this prevent X to start on current Raspbian on my
> Raspberry Pi 3A+ (multi_v7_defconfig, no u-boot). We must be careful here.
>
> I will take a look at the debug UART. Maybe there are more helpful
> information.
It seems we're seeing different things, I tested this on raspbian
(multi_v7_defconfig) and on arm64. I'll try again from scratch tomorrow.
[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2020-03-03 18:37 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-03 17:32 [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D Nicolas Saenz Julienne
2020-03-03 18:17 ` Stefan Wahren
2020-03-03 18:37 ` Nicolas Saenz Julienne [this message]
2020-03-03 19:24 ` Stefan Wahren
2020-03-05 10:44 ` Nicolas Saenz Julienne
2020-03-06 20:33 ` Stefan Wahren
2020-03-09 15:41 ` Stefan Wahren
2020-03-09 19:22 ` Nicolas Saenz Julienne
2020-03-13 13:59 ` Stefan Wahren
2020-03-15 19:16 ` Stefan Wahren
2020-03-16 12:40 ` Nicolas Saenz Julienne
2020-03-16 13:57 ` Dave Stevenson
2020-03-20 14:43 ` Nicolas Saenz Julienne
2020-03-23 14:56 ` Maxime Ripard
2020-03-23 15:55 ` Dave Stevenson
2020-03-23 18:48 ` Stefan Wahren
2020-03-23 19:10 ` Dave Stevenson
2020-03-26 12:24 ` Nicolas Saenz Julienne
2020-03-26 17:24 ` Stefan Wahren
2020-03-27 0:35 ` Florian Fainelli
2020-03-27 10:41 ` Nicolas Saenz Julienne
2020-03-27 11:24 ` Stefan Wahren
2020-03-27 12:58 ` Nicolas Saenz Julienne
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=03fcb1e2bc7f3ff389b6dfbf3964e159a93ae835.camel@suse.de \
--to=nsaenzjulienne@suse.de \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=eric@anholt.net \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stefan.wahren@i2se.com \
--cc=wahrenst@gmx.net \
/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).