From: Michael Riesch <michael.riesch@wolfvision.net>
To: barebox@lists.infradead.org
Cc: Frank Wunderlich <frank-w@public-files.de>,
Michael Riesch <michael.riesch@wolfvision.net>
Subject: [PATCH 0/2] align rk356x drivers as preparation for mainline dts
Date: Mon, 9 May 2022 13:36:16 +0200 [thread overview]
Message-ID: <20220509113618.1602657-1-michael.riesch@wolfvision.net> (raw)
Hi all,
These patches align the barebox drivers for the Naneng Combo PHY and the dwc3
with the current device tree bindings in mainline Linux. Thereby, the
migration from the initial device tree files related to the RK3568 EVB1 and
the BananaPi R2Pro to their equivalents in mainline Linux is facilitated.
In order to ensure compatibility, the initial device tree files in
arch/arm/dts are adjusted accordingly.
The changes are tested exclusively on the RK3568 EVB1 -- Frank, if you could
give this a test on the BananaPi it would be great.
Looking forward to your comments!
Best regards,
Michael
Michael Riesch (2):
phy: rockchip: align naneng-combphy clocks and resets with binding
usb: dwc3: align dwc3 clocks with binding
arch/arm/dts/rk3568-bpi-r2-pro.dts | 7 +-
arch/arm/dts/rk3568-evb1-v10.dts | 14 ++--
arch/arm/dts/rk3568.dtsi | 82 +++++++------------
.../rockchip/phy-rockchip-naneng-combphy.c | 19 +----
drivers/usb/dwc3/core.c | 50 ++++++++---
5 files changed, 79 insertions(+), 93 deletions(-)
--
2.30.2
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2022-05-09 11:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 11:36 Michael Riesch [this message]
2022-05-09 11:36 ` [PATCH 1/2] phy: rockchip: align naneng-combphy clocks and resets with binding Michael Riesch
2022-05-09 11:36 ` [PATCH 2/2] usb: dwc3: align dwc3 clocks " Michael Riesch
2022-05-10 8:11 ` Aw: [PATCH 0/2] align rk356x drivers as preparation for mainline dts Frank Wunderlich
2022-05-11 6:28 ` 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=20220509113618.1602657-1-michael.riesch@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=barebox@lists.infradead.org \
--cc=frank-w@public-files.de \
/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