From: Christoph Hellwig <hch@infradead.org>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: Palmer Dabbelt <palmer@sifive.com>,
linux-riscv@lists.infradead.org, lollivier@baylibre.com,
paul@pwsan.com, linux-kernel@vger.kernel.org,
aou@eecs.berkeley.edu
Subject: Re: [PATCH v3 1/5] arch: riscv: add support for building DTB files from DT source data
Date: Sun, 9 Jun 2019 00:49:30 -0700 [thread overview]
Message-ID: <20190609074930.GA25109@infradead.org> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906082245300.720@viisi.sifive.com>
On Sat, Jun 08, 2019 at 10:50:14PM -0700, Paul Walmsley wrote:
> Once there are SoC variants that have different CPU cores, but with the
> remaining chip integration the same, I think it would make sense to move
> the CONFIG_SOC_ stuff out from ARM, RISC-V, etc., into something that's
> not CPU architecture-specific. But for the time being, that seems
> premature. Might as well have it be driven by an actual use-case.
We've already had a few SOC families with the same periphals glue and
either m68k/powerpc, powerpc/mips or mips/arm/arm64 CPUs, so this isn't
exactly new. Not really sure the grouping adds that much value, though.
next prev parent reply other threads:[~2019-06-09 7:49 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-02 8:04 [PATCH v3 0/5] arch: riscv: add board and SoC DT file support Paul Walmsley
2019-06-02 8:04 ` [PATCH v3 1/5] arch: riscv: add support for building DTB files from DT source data Paul Walmsley
2019-06-04 14:37 ` Loys Ollivier
2019-06-07 5:12 ` Paul Walmsley
2019-06-07 9:49 ` Loys Ollivier
2019-06-08 17:56 ` Palmer Dabbelt
2019-06-09 5:50 ` Paul Walmsley
2019-06-09 7:49 ` Christoph Hellwig [this message]
2019-06-02 8:04 ` [PATCH v3 2/5] dt-bindings: riscv: sifive: add YAML documentation for the SiFive FU540 Paul Walmsley
2019-06-10 21:44 ` Rob Herring
2019-06-16 18:39 ` Paul Walmsley
2019-06-02 8:04 ` [PATCH v3 3/5] dt-bindings: riscv: convert cpu binding to json-schema Paul Walmsley
2019-06-02 8:04 ` [PATCH v3 4/5] riscv: dts: add initial support for the SiFive FU540-C000 SoC Paul Walmsley
2019-06-04 14:38 ` Loys Ollivier
2019-06-02 8:05 ` [PATCH v3 5/5] riscv: dts: add initial board data for the SiFive HiFive Unleashed Paul Walmsley
2019-06-04 14:41 ` Loys Ollivier
2019-06-09 6:18 ` Antony Pavlov
2019-06-16 18:36 ` Paul Walmsley
2019-06-04 14:31 ` [PATCH v3 0/5] arch: riscv: add board and SoC DT file support Loys Ollivier
2019-06-07 5:14 ` Paul Walmsley
2019-06-05 17:36 ` Kevin Hilman
2019-06-06 23:15 ` Atish Patra
2019-06-07 16:51 ` Kevin Hilman
2019-06-07 17:58 ` Atish Patra
2019-06-07 20:55 ` Auer, Lukas
2019-06-07 5:18 ` 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=20190609074930.GA25109@infradead.org \
--to=hch@infradead.org \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lollivier@baylibre.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=paul@pwsan.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;
as well as URLs for NNTP newsgroup(s).