From: Michael Riesch <michael.riesch@wolfvision.net>
To: barebox@lists.infradead.org
Cc: Michael Riesch <michael.riesch@wolfvision.net>
Subject: [PATCH master 2/3] common: boards: move dependencies to wolfvision board code library
Date: Wed, 15 May 2024 10:00:35 +0200 [thread overview]
Message-ID: <20240515-b4-pf5-fixup-v1-2-a58c8ec94f48@wolfvision.net> (raw)
In-Reply-To: <20240515-b4-pf5-fixup-v1-0-a58c8ec94f48@wolfvision.net>
Since hardware ID detection has been moved to the WolfVision board code
library, move the Kconfig dependencies as well.
Signed-off-by: Michael Riesch <michael.riesch@wolfvision.net>
---
arch/arm/mach-rockchip/Kconfig | 2 --
common/boards/Kconfig | 2 ++
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/mach-rockchip/Kconfig b/arch/arm/mach-rockchip/Kconfig
index f373624f5c..e7c0c634aa 100644
--- a/arch/arm/mach-rockchip/Kconfig
+++ b/arch/arm/mach-rockchip/Kconfig
@@ -117,9 +117,7 @@ config MACH_RADXA_CM3
config MACH_WOLFVISION_PF5
select ARCH_RK3568
- select AIODEV
select BOARD_WOLFVISION
- select ROCKCHIP_SARADC
bool "WolfVision PF5 mainboard"
help
Say Y here if you are using a WolfVision PF5 mainboard
diff --git a/common/boards/Kconfig b/common/boards/Kconfig
index a2a51155ea..586a54d7ca 100644
--- a/common/boards/Kconfig
+++ b/common/boards/Kconfig
@@ -17,3 +17,5 @@ config BOARD_TQ
config BOARD_WOLFVISION
bool
+ select AIODEV
+ select ROCKCHIP_SARADC
--
2.34.1
next prev parent reply other threads:[~2024-05-15 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-15 8:00 [PATCH master 0/3] Fixes for WolfVision board code library and PF5 mainboard code Michael Riesch
2024-05-15 8:00 ` [PATCH master 1/3] arm: boards: add pr_fmt() prefix to wolfvision pf5 board code Michael Riesch
2024-05-15 8:00 ` Michael Riesch [this message]
2024-05-15 8:00 ` [PATCH master 3/3] common: boards: wolfvision: fix handling of overlays parameter Michael Riesch
2024-05-15 8:32 ` Michael Riesch
2024-05-15 9:14 ` Ahmad Fatoum
2024-05-15 10:28 ` Michael Riesch
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=20240515-b4-pf5-fixup-v1-2-a58c8ec94f48@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