From: Stefan Wahren <wahrenst@gmx.net>
To: "H. Nikolaus Schaller" <hns@goldelico.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>
Cc: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
devicetree@vger.kernel.org, linux-rpi-kernel@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, letux-kernel@openphoenux.org,
stable@vger.kernel.org
Subject: Re: [PATCH v2] Revert v6.2-rc1 and later "ARM: dts: bcm2835-rpi: Use firmware clocks for display"
Date: Sun, 19 Jan 2025 01:36:52 +0100 [thread overview]
Message-ID: <808a325f-81bc-4f5d-8c07-fa255ef2d25a@gmx.net> (raw)
In-Reply-To: <cb9e10dfb4f50207e33ddac16794ee6b806744da.1737217627.git.hns@goldelico.com>
Hi,
Am 18.01.25 um 17:27 schrieb H. Nikolaus Schaller:
> This reverts commit 27ab05e1b7e5c5ec9b4f658e1b2464c0908298a6.
>
> I tried to upgrade a RasPi 3B+ with Waveshare 7inch HDMI LCD
> from 6.1.y to 6.6.y but found that the display is broken with
> this log message:
>
> [ 17.776315] vc4-drm soc:gpu: bound 3f400000.hvs (ops vc4_drm_unregister [vc4])
> [ 17.784034] platform 3f806000.vec: deferred probe pending
>
> Some tests revealed that while 6.1.y works, 6.2-rc1 is already broken but all
> newer kernels as well. And a bisect did lead me to this patch.
I successfully tested every Kernel release until Linux 6.13-rc with the
Raspberry Pi 3B+, so i prefer to step back and analyze this issue further.
What kernel config do you use ?
What is the value of CONFIG_CLK_RASPBERRYPI ?
Best regards
next prev parent reply other threads:[~2025-01-19 0:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-18 16:27 [PATCH v2] Revert v6.2-rc1 and later "ARM: dts: bcm2835-rpi: Use firmware clocks for display" H. Nikolaus Schaller
2025-01-19 0:36 ` Stefan Wahren [this message]
2025-01-19 15:04 ` H. Nikolaus Schaller
2025-01-20 16:34 ` Florian Fainelli
2025-01-23 14:05 ` H. Nikolaus Schaller
2025-01-19 6:35 ` Greg KH
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=808a325f-81bc-4f5d-8c07-fa255ef2d25a@gmx.net \
--to=wahrenst@gmx.net \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=hns@goldelico.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=letux-kernel@openphoenux.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rpi-kernel@lists.infradead.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
--cc=stable@vger.kernel.org \
/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