Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
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: sta...@vger.kernel.org Signed-off-by: Stefan Wahren >>> 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 ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
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: sta...@vger.kernel.org >>> Signed-off-by: Stefan Wahren >> 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? -- Florian ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
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: sta...@vger.kernel.org >> Signed-off-by: Stefan Wahren > 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? Stefan ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
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: sta...@vger.kernel.org > Signed-off-by: Stefan Wahren Applied to devicetree/fixes, thanks! -- Florian ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
Hi Florian, Am 20.09.19 um 19:52 schrieb Florian Fainelli: > On 9/8/19 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: sta...@vger.kernel.org >> Signed-off-by: Stefan Wahren > Do you want me to pick up this change directly, or would you want to > issue a pull request for 5.4-rcX with other fixes? there aren't any other fixes, please pick up this directly. Thanks Stefan ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
On 9/8/19 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: sta...@vger.kernel.org > Signed-off-by: Stefan Wahren Do you want me to pick up this change directly, or would you want to issue a pull request for 5.4-rcX with other fixes? -- Florian ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel
Re: [PATCH] Revert "ARM: bcm283x: Switch V3D over to using the PM driver instead of firmware."
Stefan Wahren writes: > 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: sta...@vger.kernel.org > Signed-off-by: Stefan Wahren Acked-by: Eric Anholt I wish someone with firmware source had the time to look into why using open source drivers to drive this hardware was failing, but I don't have that time or code any more. signature.asc Description: PGP signature ___ dri-devel mailing list dri-devel@lists.freedesktop.org https://lists.freedesktop.org/mailman/listinfo/dri-devel