From: Loys Ollivier <lollivier@baylibre.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Paul Walmsley <paul@pwsan.com>,
Palmer Dabbelt <palmer@sifive.com>,
Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v3 1/5] arch: riscv: add support for building DTB files from DT source data
Date: Fri, 07 Jun 2019 11:49:10 +0200 [thread overview]
Message-ID: <86y32dwwrt.fsf@baylibre.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906062208280.28147@viisi.sifive.com>
On Thu 06 Jun 2019 at 22:12, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> On Tue, 4 Jun 2019, Loys Ollivier wrote:
>
>> Always build it ?
>> Any particular reason to drop ARCH_SIFIVE ?
>
> Palmer had some reservations about it, so I dropped it for now. But then
> as I was thinking about it, I remembered that I also had some reservations
> about it, years ago: that everyone should use CONFIG_SOC_* for this,
> rather than CONFIG_ARCH. CONFIG_ARCH_* seems better reserved for
> CPU architectures.
Agree on the CONFIG_SOC.
>
> If you agree, would you like to send a followup series, based on the DT
> patches, to make the SiFive DT file builds depend on CONFIG_SOC_* instead?
Sure, I'd be glad to follow up on that. I'll send a followup series to
start a discussion.
--
Loys
WARNING: multiple messages have this Message-ID (diff)
From: Loys Ollivier <lollivier@baylibre.com>
To: Paul Walmsley <paul.walmsley@sifive.com>
Cc: linux-riscv@lists.infradead.org, Paul Walmsley <paul@pwsan.com>,
Palmer Dabbelt <palmer@sifive.com>,
linux-kernel@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>
Subject: Re: [PATCH v3 1/5] arch: riscv: add support for building DTB files from DT source data
Date: Fri, 07 Jun 2019 11:49:10 +0200 [thread overview]
Message-ID: <86y32dwwrt.fsf@baylibre.com> (raw)
In-Reply-To: <alpine.DEB.2.21.9999.1906062208280.28147@viisi.sifive.com>
On Thu 06 Jun 2019 at 22:12, Paul Walmsley <paul.walmsley@sifive.com> wrote:
> On Tue, 4 Jun 2019, Loys Ollivier wrote:
>
>> Always build it ?
>> Any particular reason to drop ARCH_SIFIVE ?
>
> Palmer had some reservations about it, so I dropped it for now. But then
> as I was thinking about it, I remembered that I also had some reservations
> about it, years ago: that everyone should use CONFIG_SOC_* for this,
> rather than CONFIG_ARCH. CONFIG_ARCH_* seems better reserved for
> CPU architectures.
Agree on the CONFIG_SOC.
>
> If you agree, would you like to send a followup series, based on the DT
> patches, to make the SiFive DT file builds depend on CONFIG_SOC_* instead?
Sure, I'd be glad to follow up on that. I'll send a followup series to
start a discussion.
--
Loys
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-06-07 9:49 UTC|newest]
Thread overview: 55+ 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 ` 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-02 8:04 ` Paul Walmsley
2019-06-04 14:37 ` Loys Ollivier
2019-06-04 14:37 ` Loys Ollivier
2019-06-07 5:12 ` Paul Walmsley
2019-06-07 5:12 ` Paul Walmsley
2019-06-07 9:49 ` Loys Ollivier [this message]
2019-06-07 9:49 ` Loys Ollivier
2019-06-08 17:56 ` Palmer Dabbelt
2019-06-08 17:56 ` Palmer Dabbelt
2019-06-09 5:50 ` Paul Walmsley
2019-06-09 5:50 ` Paul Walmsley
2019-06-09 7:49 ` Christoph Hellwig
2019-06-09 7:49 ` Christoph Hellwig
2019-06-02 8:04 ` [PATCH v3 2/5] dt-bindings: riscv: sifive: add YAML documentation for the SiFive FU540 Paul Walmsley
2019-06-02 8:04 ` Paul Walmsley
2019-06-10 21:44 ` Rob Herring
2019-06-10 21:44 ` Rob Herring
2019-06-16 18:39 ` Paul Walmsley
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 ` Paul Walmsley
2019-06-02 8:04 ` 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-02 8:04 ` Paul Walmsley
2019-06-04 14:38 ` Loys Ollivier
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-02 8:05 ` Paul Walmsley
2019-06-04 14:41 ` Loys Ollivier
2019-06-04 14:41 ` Loys Ollivier
2019-06-09 6:18 ` Antony Pavlov
2019-06-09 6:18 ` Antony Pavlov
2019-06-09 6:18 ` Antony Pavlov
2019-06-16 18:36 ` Paul Walmsley
2019-06-16 18:36 ` Paul Walmsley
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-04 14:31 ` Loys Ollivier
2019-06-07 5:14 ` Paul Walmsley
2019-06-07 5:14 ` Paul Walmsley
2019-06-05 17:36 ` Kevin Hilman
2019-06-05 17:36 ` Kevin Hilman
2019-06-06 23:15 ` Atish Patra
2019-06-06 23:15 ` Atish Patra
2019-06-07 16:51 ` Kevin Hilman
2019-06-07 16:51 ` Kevin Hilman
2019-06-07 17:58 ` Atish Patra
2019-06-07 17:58 ` Atish Patra
2019-06-07 20:55 ` Auer, Lukas
2019-06-07 20:55 ` Auer, Lukas
2019-06-07 5:18 ` Paul Walmsley
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=86y32dwwrt.fsf@baylibre.com \
--to=lollivier@baylibre.com \
--cc=aou@eecs.berkeley.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.