From: Stefan Wahren <stefan.wahren@i2se.com> To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>, Eric Anholt <eric@anholt.net> Cc: devicetree@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>, Scott Branden <sbranden@broadcom.com>, Ray Jui <rjui@broadcom.com>, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>, wahrenst@gmx.net, linux-arm-kernel@lists.infradead.org, linux-rpi-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D Date: Thu, 26 Mar 2020 18:24:45 +0100 [thread overview] Message-ID: <8c2bdd83-c8a9-7ba8-8d61-69594e6a2bde@i2se.com> (raw) In-Reply-To: <24f850f64b5c71c71938110775e16caaec2811cc.camel@suse.de> Am 26.03.20 um 13:24 schrieb Nicolas Saenz Julienne: > Hi Stefan and Florian, > > On Tue, 2020-03-03 at 18:32 +0100, Nicolas Saenz Julienne wrote: >> 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> >> --- > now that the problem Stefan was seeing is being taken care of, I think it's > fair to reconsider taking this patch. Maybe even adding a Tested-by by Stefan? after applying "drm/vc4: Fix HDMI mode validation" this commit doesn't cause any regression: Tested-by: Stefan Wahren <stefan.wahren@i2se.com> Thanks > > Regards, > Nicolas
WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com> To: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>, Eric Anholt <eric@anholt.net> Cc: devicetree@vger.kernel.org, Florian Fainelli <f.fainelli@gmail.com>, Scott Branden <sbranden@broadcom.com>, Ray Jui <rjui@broadcom.com>, linux-kernel@vger.kernel.org, bcm-kernel-feedback-list <bcm-kernel-feedback-list@broadcom.com>, wahrenst@gmx.net, linux-arm-kernel@lists.infradead.org, linux-rpi-kernel@lists.infradead.org Subject: Re: [PATCH] ARM: dts: bcm283x: Use firmware PM driver for V3D Date: Thu, 26 Mar 2020 18:24:45 +0100 [thread overview] Message-ID: <8c2bdd83-c8a9-7ba8-8d61-69594e6a2bde@i2se.com> (raw) In-Reply-To: <24f850f64b5c71c71938110775e16caaec2811cc.camel@suse.de> Am 26.03.20 um 13:24 schrieb Nicolas Saenz Julienne: > Hi Stefan and Florian, > > On Tue, 2020-03-03 at 18:32 +0100, Nicolas Saenz Julienne wrote: >> 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> >> --- > now that the problem Stefan was seeing is being taken care of, I think it's > fair to reconsider taking this patch. Maybe even adding a Tested-by by Stefan? after applying "drm/vc4: Fix HDMI mode validation" this commit doesn't cause any regression: Tested-by: Stefan Wahren <stefan.wahren@i2se.com> Thanks > > Regards, > Nicolas _______________________________________________ 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-26 17:24 UTC|newest] Thread overview: 38+ 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 17:32 ` Nicolas Saenz Julienne 2020-03-03 18:17 ` Stefan Wahren 2020-03-03 18:17 ` Stefan Wahren 2020-03-03 18:37 ` Nicolas Saenz Julienne 2020-03-03 18:37 ` Nicolas Saenz Julienne 2020-03-03 19:24 ` Stefan Wahren 2020-03-03 19:24 ` Stefan Wahren 2020-03-05 10:44 ` Nicolas Saenz Julienne 2020-03-05 10:44 ` Nicolas Saenz Julienne 2020-03-06 20:33 ` Stefan Wahren 2020-03-06 20:33 ` Stefan Wahren 2020-03-09 15:41 ` Stefan Wahren 2020-03-09 15:41 ` Stefan Wahren 2020-03-09 19:22 ` Nicolas Saenz Julienne 2020-03-09 19:22 ` Nicolas Saenz Julienne 2020-03-13 13:59 ` Stefan Wahren 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 12:24 ` Nicolas Saenz Julienne 2020-03-26 17:24 ` Stefan Wahren [this message] 2020-03-26 17:24 ` Stefan Wahren 2020-03-27 0:35 ` Florian Fainelli 2020-03-27 0:35 ` Florian Fainelli 2020-03-27 10:41 ` Nicolas Saenz Julienne 2020-03-27 10:41 ` Nicolas Saenz Julienne 2020-03-27 11:24 ` Stefan Wahren 2020-03-27 11:24 ` Stefan Wahren 2020-03-27 12:58 ` Nicolas Saenz Julienne 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=8c2bdd83-c8a9-7ba8-8d61-69594e6a2bde@i2se.com \ --to=stefan.wahren@i2se.com \ --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=nsaenzjulienne@suse.de \ --cc=rjui@broadcom.com \ --cc=sbranden@broadcom.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.