From: Michael Riesch <michael.riesch@wolfvision.net>
To: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Rob Herring <robh+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>, Liang Chen <cl@rock-chips.com>,
Peter Geis <pgwipeout@gmail.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Simon Xue <xxm@rock-chips.com>,
Michael Riesch <michael.riesch@wolfvision.net>
Subject: [PATCH 0/1] arm64: dts: rockchip: add missing rockchip,grf property to rk356x
Date: Mon, 23 Aug 2021 14:39:10 +0200 [thread overview]
Message-ID: <20210823123911.12095-1-michael.riesch@wolfvision.net> (raw)
Hi all,
The following error messages appear on my RK3568 EVB1 board during boot:
rockchip_clk_register_muxgrf: regmap not available
rockchip_clk_register_branches: failed to register clock clk_ddr1x: -524
These can be fixed by providing the missing rockchip,grf property to the
device tree (similar to other Rockchip SoCs, such as the RK3399).
However, the rockchip,rk3568-cru bindings do not specify a property of that
name. Am I missing something or should this property be added to the bindings?
Best regards,
Michael
Michael Riesch (1):
arm64: dts: rockchip: add missing rockchip,grf property to rk356x
arch/arm64/boot/dts/rockchip/rk356x.dtsi | 1 +
1 file changed, 1 insertion(+)
--
2.17.1
next reply other threads:[~2021-08-23 12:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 12:39 Michael Riesch [this message]
2021-08-23 12:39 ` [PATCH 1/1] arm64: dts: rockchip: add missing rockchip,grf property to rk356x Michael Riesch
2021-08-23 13:12 ` Peter Geis
2021-08-23 13:39 ` Michael Riesch
2021-08-23 13:51 ` Peter Geis
2021-08-25 8:19 ` Michael Riesch
2021-08-23 18:42 ` [PATCH 0/1] " Heiko Stuebner
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=20210823123911.12095-1-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=cl@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=xxm@rock-chips.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;
as well as URLs for NNTP newsgroup(s).