mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Sascha Hauer <s.hauer@pengutronix.de>
To: Barebox List <barebox@lists.infradead.org>
Subject: [PATCH 0/2] Rockchip RK3588 fixes
Date: Tue,  5 Dec 2023 08:27:04 +0100	[thread overview]
Message-ID: <20231205072706.647255-1-s.hauer@pengutronix.de> (raw)

The RK3588 upstream dtsi files have evolved a lot. This series fixes the
worst regressions caused by this. We switch to use upstream dtsi files
and drop the downstream variants containing the PCI and SDMMC nodes. We
still have to overwrite the ranges property for the pcie2x1l2 node, I do
not yet understand what the Linux PCI driver makes different to work
with the Linux ranges properties. With this at least the PCI ethernet
controller works again. We disable some other PCI and USB nodes which
otherwise throw annoying warning messages due to missing phys.

Sascha Hauer (2):
  ARM: rockchip: rk3588: Use upstream dts files
  ARM: rockchip: rock-5a: Disable non working devices

 arch/arm/dts/rk3588-rock-5b.dts               |  39 +++++
 arch/arm/dts/rk3588.dtsi                      | 145 ------------------
 arch/arm/dts/rk3588s.dtsi                     | 126 +--------------
 .../rockchip/phy-rockchip-naneng-combphy.c    |   8 +-
 4 files changed, 44 insertions(+), 274 deletions(-)

-- 
2.39.2




             reply	other threads:[~2023-12-05  7:28 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-05  7:27 Sascha Hauer [this message]
2023-12-05  7:27 ` [PATCH 1/2] ARM: rockchip: rk3588: Use upstream dts files Sascha Hauer
2023-12-05  7:27 ` [PATCH 2/2] ARM: rockchip: rock-5a: Disable non working devices Sascha Hauer

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=20231205072706.647255-1-s.hauer@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=barebox@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