linux-rockchip.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Qu Wenruo <wqu@suse.com>
To: Linux ARM <linux-arm-kernel@lists.infradead.org>,
	"open list:ARM/Rockchip SoC..."
	<linux-rockchip@lists.infradead.org>
Subject: RK3399 (RockPro64) can't setup upstream opp tables
Date: Fri, 17 Sep 2021 10:45:08 +0800	[thread overview]
Message-ID: <0c0c80c7-460f-8a34-93d4-41351741f6ed@suse.com> (raw)

Hi,

Recently I find that no matter what opp tables I'm using (default and 
op1), the RockPro64 board always failed to add the opp table with the 
following error messages:

[    2.443667] rk3399-dmc-freq ffa80000.dmc: supply center not found, 
using dummy regulator
[    2.444366] dwmmc_rockchip fe310000.mmc: IDMAC supports 32-bit 
address mode.
[    2.444527] rk3399-dmc-freq ffa80000.dmc: Invalid operating-points in 
device tree.
[    2.445037] dwmmc_rockchip fe310000.mmc: Using internal DMA controller.
[    2.445661] rk3399-dmc-freq: probe of ffa80000.dmc failed with error -22

I tried the default opp table (rk3399-opp.dts) and the op1, they both 
failed with the same messages.

Upstream kernel v5.14.2 (With one commit reverted to address the 
ethernet regression) and upstream v5.15-rc1 kernels both tested, no good 
result.

Is there some regression in rockchip related code that prevents the 
default/op1 opp tables from getting applied properly?

Thanks,
Qu


_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip

             reply	other threads:[~2021-09-17  2:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-17  2:45 Qu Wenruo [this message]
2021-09-17 10:34 ` RK3399 (RockPro64) can't setup upstream opp tables Qu Wenruo

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=0c0c80c7-460f-8a34-93d4-41351741f6ed@suse.com \
    --to=wqu@suse.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-rockchip@lists.infradead.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).