From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Pratham Patel <prathampatel@thefossguy.com>,
"sebastian.reichel@collabora.com"
<sebastian.reichel@collabora.com>,
"saravanak@google.com" <saravanak@google.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-rockchip@lists.infradead.org"
<linux-rockchip@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"regressions@lists.linux.dev" <regressions@lists.linux.dev>,
"stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Fixing the devicetree of Rock 5 Model B (and possibly others)
Date: Sat, 23 Mar 2024 18:17:39 +0100 [thread overview]
Message-ID: <092a7c4c-0a75-4b27-acec-385fdcfb9f7a@leemhuis.info> (raw)
In-Reply-To: <tQ0L3-34g4t-mzfQIP6KDe5OYelGnEo6Udzq6Kb_nEcljppSQUXOktpE__nL-CdLOu9gW-4tIIbjtSbqrdCrjEkdhZLPiiHTqRcCB6WORuM=@thefossguy.com>
On 23.03.24 18:02, Pratham Patel wrote:
> Since the introduction of the `of: property: fw_devlink: Fix stupid bug in remote-endpoint parsing` patch,
There is an earlier bug report asking for a revert of that patch:
https://lore.kernel.org/all/ZfvN5jDrftG-YRG4@titan/
> an issue
Is your problem maybe similar to the one above?
Ciao, Thorsten
> with the device-tree of the Rock 5 Model B has been detected. All the stable kernels (6.7.y and 6.8.y) work on the Orange Pi 5, which has the Rockchip RK3588S SoC (same as the RK3588, but less I/O basically). So, being an owner of only two SBCs which use the RK3588* SoC, it appears that the Rock 5 Model B's DT is incorrect.
>
> I looked at the patch and tried several things, neither resulted in anything that would point me to the core issue. Then I tried this:
>
> ```
> $ grep -C 3 remote-endpoint arch/arm64/boot/dts/rockchip/rk3588-rock-5b.dts
>
> port {
> es8316_p0_0: endpoint {
> remote-endpoint = <&i2s0_8ch_p0_0>;
> };
> };
> };
> --
> i2s0_8ch_p0_0: endpoint {
> dai-format = "i2s";
> mclk-fs = <256>;
> remote-endpoint = <&es8316_p0_0>;
> };
> };
> };
> ```
>
> So, from a cursory look, the issue seems to be related to either the DT node for the audio codec or related to the es8316's binding itself. Though I doubt that the later is the issue because if that were the issue, _someone_ with a Pine64 Pinebook Pro would've raised alarms. So far, this seems to be related to the `rk3588-rock-5b.dts` and possibly with the `rk3588s-rock-5a.dts` too.
>
> I would **love** to help but I'm afraid I device-trees are not something that I am at-all familiar with. That said, I am open to methods of debugging this issue to provide a fix myself.
>
> I would have replied to the patch's link but unfortunately, I haven't yet setup neomutt and my email provider's web UI doesn't have a [straightforward] way to reply using the 'In-Reply-To' header, hence a new thread. Apologies for the inconvenience caused.
>
> -- Pratham Patel
next prev parent reply other threads:[~2024-03-23 17:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-23 17:02 Fixing the devicetree of Rock 5 Model B (and possibly others) Pratham Patel
2024-03-23 17:08 ` Pratham Patel
2024-03-23 17:09 ` Dragan Simic
2024-04-01 23:24 ` Saravana Kannan
2024-04-02 23:32 ` Pratham Patel
2024-04-03 0:46 ` Saravana Kannan
2024-04-03 1:03 ` Pratham Patel
2024-04-03 13:52 ` Sebastian Reichel
2024-04-05 8:32 ` Pratham Patel
2024-04-03 13:51 ` Dragan Simic
2024-03-23 17:17 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2024-03-23 17:23 ` Pratham Patel
2024-04-03 15:26 Pratham Patel
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=092a7c4c-0a75-4b27-acec-385fdcfb9f7a@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=prathampatel@thefossguy.com \
--cc=regressions@lists.linux.dev \
--cc=saravanak@google.com \
--cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).