From: Michael Riesch <michael.riesch@wolfvision.net>
To: barebox@lists.infradead.org
Cc: Michael Riesch <michael.riesch@wolfvision.net>
Subject: [PATCH v2 0/4] arm: boards: add wolfvision pf5 mainboard
Date: Fri, 12 Apr 2024 15:32:11 +0200 [thread overview]
Message-ID: <20240412-feature-wolfvision-pf5-v2-0-7e277cc8831b@wolfvision.net> (raw)
Habidere,
This series adds support for the WolfVision PF5 mainboard, which serves
as base for recent WolfVision products. It features the Rockchip RK3568
and can be extended with several different extension boards. The
WolfVision PF5 IO Expander is one example of such an extension board.
Support for this extension is also included in this series.
Patch 1 copies the device tree (overlay) from mainline Linux.
Patch 2 and 3 provide a library and state definition that are envisaged
to be used by all WolfVision boards.
Finally, patch 4 adds the actual PF5 mainboard support.
v2 addresses comments by Sascha and Marco -- thanks for the review!
Looking forward to your comments!
Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
---
Michael Riesch (4):
arm: dts: copy pf5 device tree from mainline linux
arm: dts: add common state for wolfvision boards
common: add wolfvision board code library
arm: boards: add wolfvision pf5 mainboard
arch/arm/boards/Makefile | 1 +
arch/arm/boards/wolfvision-pf5/.gitignore | 1 +
arch/arm/boards/wolfvision-pf5/Makefile | 3 +
arch/arm/boards/wolfvision-pf5/board.c | 88 ++++
arch/arm/boards/wolfvision-pf5/lowlevel.c | 36 ++
arch/arm/dts/Makefile | 3 +
...rk3568-wolfvision-pf5-io-expander-upstream.dtso | 137 ++++++
.../arm/dts/rk3568-wolfvision-pf5-io-expander.dtso | 11 +
arch/arm/dts/rk3568-wolfvision-pf5-upstream.dts | 528 +++++++++++++++++++++
arch/arm/dts/rk3568-wolfvision-pf5.dts | 48 ++
arch/arm/dts/wolfvision-state.dtsi | 71 +++
arch/arm/mach-rockchip/Kconfig | 9 +
common/boards/Kconfig | 3 +
common/boards/Makefile | 1 +
common/boards/wolfvision/Makefile | 2 +
common/boards/wolfvision/common.c | 142 ++++++
images/Makefile.rockchip | 1 +
include/boards/wolfvision/common.h | 32 ++
18 files changed, 1117 insertions(+)
---
base-commit: 8351de807d1430977fe83457c85face9537357d4
change-id: 20240405-feature-wolfvision-pf5-4d15a072b0b8
Best regards,
--
Michael Riesch <michael.riesch@wolfvision.net>
next reply other threads:[~2024-04-12 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-12 13:32 Michael Riesch [this message]
2024-04-12 13:32 ` [PATCH v2 1/4] arm: dts: copy pf5 device tree from mainline linux Michael Riesch
2024-04-12 13:32 ` [PATCH v2 2/4] arm: dts: add common state for wolfvision boards Michael Riesch
2024-04-12 13:32 ` [PATCH v2 3/4] common: add wolfvision board code library Michael Riesch
2024-04-12 13:32 ` [PATCH v2 4/4] arm: boards: add wolfvision pf5 mainboard Michael Riesch
2024-04-16 13:34 ` [PATCH v2 0/4] " 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=20240412-feature-wolfvision-pf5-v2-0-7e277cc8831b@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--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