From: Loys Ollivier <lollivier@baylibre.com>
To: Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>
Cc: Loys Ollivier <lollivier@baylibre.com>,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, Kevin Hilman <khilman@baylibre.com>
Subject: [PATCH 2/3] riscv: select SiFive platform drivers with SOC_SIFIVE
Date: Mon, 17 Jun 2019 21:29:49 +0200 [thread overview]
Message-ID: <1560799790-20287-3-git-send-email-lollivier@baylibre.com> (raw)
In-Reply-To: <1560799790-20287-1-git-send-email-lollivier@baylibre.com>
On selection of SOC_SIFIVE select the corresponding platform drivers.
Signed-off-by: Loys Ollivier <lollivier@baylibre.com>
---
arch/riscv/Kconfig.socs | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/arch/riscv/Kconfig.socs b/arch/riscv/Kconfig.socs
index 60dae1b5f276..536c0ef4aee8 100644
--- a/arch/riscv/Kconfig.socs
+++ b/arch/riscv/Kconfig.socs
@@ -2,6 +2,11 @@ menu "SoC selection"
config SOC_SIFIVE
bool "SiFive SoCs"
+ select SERIAL_SIFIVE
+ select SERIAL_SIFIVE_CONSOLE
+ select CLK_SIFIVE
+ select CLK_SIFIVE_FU540_PRCI
+ select SIFIVE_PLIC
help
This enables support for SiFive SoC platform hardware.
--
2.7.4
next prev parent reply other threads:[~2019-06-17 19:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-17 19:29 [PATCH 0/3] riscv: add SOC_SIFIVE config for SiFive specific resource Loys Ollivier
2019-06-17 19:29 ` [PATCH 1/3] arch: riscv: add config option for building SiFive's SoC resource Loys Ollivier
2019-06-19 7:04 ` Palmer Dabbelt
2019-06-17 19:29 ` Loys Ollivier [this message]
2019-06-19 7:04 ` [PATCH 2/3] riscv: select SiFive platform drivers with SOC_SIFIVE Palmer Dabbelt
2019-06-17 19:29 ` [PATCH 3/3] riscv: defconfig: enable SOC_SIFIVE Loys Ollivier
2019-06-19 7:04 ` Palmer Dabbelt
2019-06-28 3:10 ` [PATCH 0/3] riscv: add SOC_SIFIVE config for SiFive specific resource Paul Walmsley
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=1560799790-20287-3-git-send-email-lollivier@baylibre.com \
--to=lollivier@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=khilman@baylibre.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
/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
all inboxes | Powered by JetHome®