From: Frank Wunderlich <frank-w@public-files.de>
To: Michael Riesch <michael.riesch@wolfvision.net>
Cc: barebox@lists.infradead.org,
Michael Riesch <michael.riesch@wolfvision.net>
Subject: Aw: [PATCH 0/2] align rk356x drivers as preparation for mainline dts
Date: Tue, 10 May 2022 10:11:30 +0200 [thread overview]
Message-ID: <trinity-e9285084-1a6d-4f4b-9552-ba07aa2d8aee-1652170290235@3c-app-gmx-bs05> (raw)
In-Reply-To: <20220509113618.1602657-1-michael.riesch@wolfvision.net>
Hi,
> Gesendet: Montag, 09. Mai 2022 um 13:36 Uhr
> Von: "Michael Riesch" <michael.riesch@wolfvision.net>
> The changes are tested exclusively on the RK3568 EVB1 -- Frank, if you could
> give this a test on the BananaPi it would be great.
currently usb on r2pro v1 is broken in barebox. Have got it working for upper port and then applied this series.
It does not seem to break anything, upper port still working in my local repo (based on master).
> Looking forward to your comments!
>
> Best regards,
> Michael
regards Frank
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2022-05-10 8:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-09 11:36 Michael Riesch
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 ` Frank Wunderlich [this message]
2022-05-11 6:28 ` [PATCH 0/2] align rk356x drivers as preparation for mainline dts 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=trinity-e9285084-1a6d-4f4b-9552-ba07aa2d8aee-1652170290235@3c-app-gmx-bs05 \
--to=frank-w@public-files.de \
--cc=barebox@lists.infradead.org \
--cc=michael.riesch@wolfvision.net \
/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