From: Rob Herring <robh@kernel.org>
To: Borislav Petkov <bp@alien8.de>
Cc: James Morse <james.morse@arm.com>,
Yash Shah <yash.shah@sifive.com>,
linux-riscv@lists.infradead.org, linux-edac@vger.kernel.org,
Palmer Dabbelt <palmer@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Albert Ou <aou@eecs.berkeley.edu>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller
Date: Wed, 3 Apr 2019 20:04:08 -0500 [thread overview]
Message-ID: <CAL_Jsq+NMapJqM4N_kpeojvrS_W19vPLfMzdiENy6FjcOiqoDA@mail.gmail.com> (raw)
In-Reply-To: <20190329202416.GI21152@zn.tnic>
On Fri, Mar 29, 2019 at 3:24 PM Borislav Petkov <bp@alien8.de> wrote:
>
> On Fri, Mar 29, 2019 at 02:41:05PM -0500, Rob Herring wrote:
> > DT dictates aligning with what the h/w looks like which has little to
> > do with OS driver design.
>
> Ok, then, where does this goal for doing a driver or compilation unit
> per IP block come from?
>
> Because everytime an ARM EDAC driver pops up, we are having the same
> discussion.
>
> > I never said you should change EDAC and I outlined how things should
> > be handled if it is one driver.
>
> Ok, we will add that to the EDAC driver design document we're currently
> working on.
>
> > DT and OS subsystems are independent things. I can't tell you how to
> > design the subsystem and you can't dictate DT design (based on EDAC
> > design).
>
> I don't think I've ever intentionally or unintentionally dictated DT
> design - all I've opposed to is having multiple EDAC drivers on ARM.
No, but folks just extend 1 driver to mean 1 DT node because that's
easy and certainly the more common case.
Rob
next prev parent reply other threads:[~2019-04-04 1:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-12 9:20 [PATCH 0/2] L2 Cache EDAC Support for HiFive Unleashed Yash Shah
2019-03-12 9:21 ` [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller Yash Shah
2019-03-28 13:16 ` Rob Herring
2019-03-28 18:47 ` James Morse
2019-03-29 14:11 ` Rob Herring
2019-03-29 14:27 ` Borislav Petkov
2019-03-29 19:41 ` Rob Herring
2019-03-29 20:24 ` Borislav Petkov
2019-04-04 1:04 ` Rob Herring [this message]
2019-04-01 16:36 ` James Morse
2019-04-04 1:17 ` Rob Herring
2019-03-12 9:21 ` [PATCH 2/2] sifive: edac: Add EDAC driver for Sifive l2 Cache Controller Yash Shah
2019-03-12 9:28 ` Borislav Petkov
2019-03-25 0:16 ` Paul Walmsley
2019-03-25 6:54 ` Borislav Petkov
2019-03-25 21:18 ` Paul Walmsley
2019-03-25 21:47 ` Borislav Petkov
2019-03-12 16:31 ` Paul Walmsley
2019-03-12 16:32 ` [PATCH 0/2] L2 Cache EDAC Support for HiFive Unleashed 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=CAL_Jsq+NMapJqM4N_kpeojvrS_W19vPLfMzdiENy6FjcOiqoDA@mail.gmail.com \
--to=robh@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=bp@alien8.de \
--cc=devicetree@vger.kernel.org \
--cc=james.morse@arm.com \
--cc=linux-edac@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=yash.shah@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;
as well as URLs for NNTP newsgroup(s).