From: Stefan Wahren <wahrenst@gmx.net>
To: Etienne Buira <etienne.buira@free.fr>
Cc: "Florian Fainelli" <florian.fainelli@broadcom.com>,
"Uwe Kleine-König" <u.kleine-koenig@baylibre.com>,
bcm-kernel-feedback-list@broadcom.com,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rpi-kernel@lists.infradead.org
Subject: Re: [PATCH] firmware/raspberrypi: raise timeout to 3s
Date: Thu, 15 May 2025 19:48:04 +0200 [thread overview]
Message-ID: <0703ff48-e781-49b6-8a8d-7cdbec73bb92@gmx.net> (raw)
In-Reply-To: <aCXUeOmy28tqg6Oy@Z926fQmE5jqhFMgp6>
Hi Etienne,
Am 15.05.25 um 13:48 schrieb Etienne Buira:
> On Thu, May 15, 2025 at 12:31:38PM +0200, Stefan Wahren wrote:
>> Am 15.05.25 um 11:44 schrieb Etienne Buira:
>>> Hi Stefan, and thank you for your interest.
>>>
>>> On Thu, May 15, 2025 at 09:42:43AM +0200, Stefan Wahren wrote:
>>>> Hi Etienne,
>>>>
>>>> Am 15.05.25 um 08:41 schrieb Etienne Buira:
>>>>> On Wed, May 14, 2025 at 06:20:32PM +0200, Stefan Wahren wrote:
>>>>>> Hi Etienne,
>>>>>>
>>>>>> Am 12.05.25 um 18:30 schrieb Etienne Buira:
>>>>> ../..
>>>>>> Out of curiosity and because i never saw this issue, could you please
>>>>>> provide more details?
>>>>>> There is nothing connected to HDMI 0 & 1 ?
>>>>>> Which firmware version are you running?
>>>> Please provide the dmesg output, so we can extract the firmware version.
>>> Firmware version is 2025-02-17T20:03:07, i also attach the full gzipped
>>> dmesg, as long as a patch of extra traces used.
>>> I did not specifically test other firmware versions for the timeout
>>> issue (but i did for video output).
>> Thanks, i'll try to reproduce.
>>
>> Sorry, i forgot but is this reproducible with a recent stable 6.12.x kernel?
> Just reproduced with pristine 6.12.28.
>
okay, i've update the firmware on my older Raspberry Pi 4 to the same
version as yours. But even with your configuration i don't see this kind
of fallout. So I think we shouldn't apply this patch until we really
know what's going on.
You don't have another Raspberry Pi 4 by any chance?
Another cause might be the toolchain. Currently I use a not so fresh gcc
11.3.1 from Linaro.
Except of this, I noticed that your configuration doesn't enable
DWC2_DUAL_ROLE and the LEDS_TRIGGER.
Best regards
next prev parent reply other threads:[~2025-05-15 17:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 16:30 Etienne Buira
2025-05-14 16:20 ` Stefan Wahren
2025-05-15 6:34 ` Etienne Buira
2025-05-21 8:55 ` Stefan Wahren
2025-05-21 10:04 ` [PATCH v3] " Etienne Buira
2025-05-21 13:05 ` Stefan Wahren
2025-05-15 6:41 ` [PATCH] " Etienne Buira
2025-05-15 7:42 ` Stefan Wahren
2025-05-15 9:44 ` Etienne Buira
2025-05-15 10:31 ` Stefan Wahren
2025-05-15 11:48 ` Etienne Buira
2025-05-15 17:48 ` Stefan Wahren [this message]
2025-05-15 22:27 ` Etienne Buira
2025-05-16 11:17 ` Stefan Wahren
2025-05-16 14:41 ` Searching for firmware timeout cause (was: [PATCH] firmware/raspberrypi: raise timeout to 3s) Etienne Buira
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=0703ff48-e781-49b6-8a8d-7cdbec73bb92@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=etienne.buira@free.fr \
--cc=florian.fainelli@broadcom.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=u.kleine-koenig@baylibre.com \
/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
all inboxes | Powered by JetHome®