From: Stefan Wahren <stefan.wahren@i2se•com>
To: Florian Fainelli <f.fainelli@gmail•com>,
Stefan Wahren <wahrenst@gmx•net>, Eric Anholt <eric@anholt•net>,
Ray Jui <rjui@broadcom•com>,
Scott Branden <sbranden@broadcom•com>,
Paul Kocialkowski <paul.kocialkowski@bootlin•com>,
boris.brezillon@bootlin•com
Cc: bcm-kernel-feedback-list@broadcom•com,
linux-arm-kernel@lists•infradead.org,
dri-devel@lists•freedesktop.org
Subject: Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
Date: Thu, 10 Oct 2019 09:09:51 +0200 [thread overview]
Message-ID: <c04a47e7-595c-84e3-fd6f-643d7ba1d0ea@i2se.com> (raw)
In-Reply-To: <877621f0-2fbc-55d1-391e-b2ffbce186ac@gmail.com>
On 09.10.19 23:42, Florian Fainelli wrote:
> On 10/9/19 2:33 PM, Stefan Wahren wrote:
>> Hi Florian,
>>
>> Am 23.09.19 um 20:56 schrieb Florian Fainelli:
>>> On 9/8/2019 8:44 AM, Stefan Wahren wrote:
>>>> Since release of the new BCM2835 PM driver there has been several reports
>>>> of V3D probing issues. This is caused by timeouts during powering-up the
>>>> GRAFX PM domain:
>>>>
>>>> bcm2835-power: Timeout waiting for grafx power OK
>>>>
>>>> I was able to reproduce this reliable on my Raspberry Pi 3B+ after setting
>>>> force_turbo=1 in the firmware configuration. Since there are no issues
>>>> using the firmware PM driver with the same setup, there must be an issue
>>>> in the BCM2835 PM driver.
>>>>
>>>> Unfortunately there hasn't been much progress in identifying the root cause
>>>> since June (mostly in the lack of documentation), so i decided to switch
>>>> back until the issue in the BCM2835 PM driver is fixed.
>>>>
>>>> Link: https://github.com/raspberrypi/linux/issues/3046
>>>> Fixes: e1dc2b2e1bef (" ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware.")
>>>> Cc: stable@vger•kernel.org
>>>> Signed-off-by: Stefan Wahren <wahrenst@gmx•net>
>>> Applied to devicetree/fixes, thanks!
>> i noticed that X hangs with recent Raspbian and Linux 5.4-rc2 after this
>> revert has been applied.
>>
>> Is there a chance to drop the revert?
> I have not sent anything yet as I wanted to get some testing done on
> other platforms, so yes, I can definitively drop that particular changes
> from devicetree/fixes and not send it for a 5.4-rc3 pull request. Does
> that work for you?
Yes, definitely
Thanks Stefan
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists•infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-10-10 7:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-08 15:44 [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware." Stefan Wahren
2019-09-11 20:48 ` Eric Anholt
2019-09-20 17:52 ` Florian Fainelli
2019-09-20 22:55 ` Stefan Wahren
2019-09-23 18:56 ` Florian Fainelli
2019-10-09 21:33 ` Stefan Wahren
2019-10-09 21:42 ` Florian Fainelli
2019-10-10 7:09 ` Stefan Wahren [this message]
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=c04a47e7-595c-84e3-fd6f-643d7ba1d0ea@i2se.com \
--to=stefan.wahren@i2se$(echo .)com \
--cc=bcm-kernel-feedback-list@broadcom$(echo .)com \
--cc=boris.brezillon@bootlin$(echo .)com \
--cc=dri-devel@lists$(echo .)freedesktop.org \
--cc=eric@anholt$(echo .)net \
--cc=f.fainelli@gmail$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=paul.kocialkowski@bootlin$(echo .)com \
--cc=rjui@broadcom$(echo .)com \
--cc=sbranden@broadcom$(echo .)com \
--cc=wahrenst@gmx$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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