From: Borislav Petkov <bp@alien8.de>
To: Rob Herring <robh@kernel.org>
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: Fri, 29 Mar 2019 15:27:39 +0100 [thread overview]
Message-ID: <20190329142739.GG21152@zn.tnic> (raw)
In-Reply-To: <CAL_Jsq+s77J=Bwiyow2d7Q=e+z+5d64i_cL6xaYn0xdvJDb4Vg@mail.gmail.com>
On Fri, Mar 29, 2019 at 09:11:24AM -0500, Rob Herring wrote:
> I honestly don't understand the issue with EDAC is here.
The EDAC core supports only one driver and if you need to load more, you
need to dance around that.
Also, if those drivers need to talk amongst each other, then they need
to build something ad-hoc so that they can.
And the other architectures can very well do one driver per platform -
only ARM wants to do this special thing because DT said so. Or whatever.
> Highbank is separate drivers for L2 ECC (PL310) and DDR. Both are used
> on highbank.
That's because your L2 driver does allocate an edac_device
(edac_device_alloc_ctl_info()) and the DDR one an edac_mc
(edac_mc_add_mc_with_groups).
For example, altera_edac does edac_device_alloc_ctl_info() for each IP
block just fine. So a single driver *can* work.
> Only the DDR driver is used midway. (I think we never got around to
> how to report A15 L2 ECC errors within Linux.)
>
> In any case, it's all irrelevant to the DT binding. We don't design
> bindings around what some particular OS wants.
And just because DT dictates one driver per IP block, I'm not going to
redesign EDAC to fit that scheme. You or someone else who feels strongly
about it, is more than welcome to do so, of course. And then maintain it
too.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Rob Herring <robh@kernel.org>
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: [1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller
Date: Fri, 29 Mar 2019 15:27:39 +0100 [thread overview]
Message-ID: <20190329142739.GG21152@zn.tnic> (raw)
On Fri, Mar 29, 2019 at 09:11:24AM -0500, Rob Herring wrote:
> I honestly don't understand the issue with EDAC is here.
The EDAC core supports only one driver and if you need to load more, you
need to dance around that.
Also, if those drivers need to talk amongst each other, then they need
to build something ad-hoc so that they can.
And the other architectures can very well do one driver per platform -
only ARM wants to do this special thing because DT said so. Or whatever.
> Highbank is separate drivers for L2 ECC (PL310) and DDR. Both are used
> on highbank.
That's because your L2 driver does allocate an edac_device
(edac_device_alloc_ctl_info()) and the DDR one an edac_mc
(edac_mc_add_mc_with_groups).
For example, altera_edac does edac_device_alloc_ctl_info() for each IP
block just fine. So a single driver *can* work.
> Only the DDR driver is used midway. (I think we never got around to
> how to report A15 L2 ECC errors within Linux.)
>
> In any case, it's all irrelevant to the DT binding. We don't design
> bindings around what some particular OS wants.
And just because DT dictates one driver per IP block, I'm not going to
redesign EDAC to fit that scheme. You or someone else who feels strongly
about it, is more than welcome to do so, of course. And then maintain it
too.
WARNING: multiple messages have this Message-ID (diff)
From: Borislav Petkov <bp@alien8.de>
To: Rob Herring <robh@kernel.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Albert Ou <aou@eecs.berkeley.edu>,
Palmer Dabbelt <palmer@sifive.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Yash Shah <yash.shah@sifive.com>,
James Morse <james.morse@arm.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
linux-riscv@lists.infradead.org,
Mauro Carvalho Chehab <mchehab@kernel.org>,
linux-edac@vger.kernel.org
Subject: Re: [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller
Date: Fri, 29 Mar 2019 15:27:39 +0100 [thread overview]
Message-ID: <20190329142739.GG21152@zn.tnic> (raw)
In-Reply-To: <CAL_Jsq+s77J=Bwiyow2d7Q=e+z+5d64i_cL6xaYn0xdvJDb4Vg@mail.gmail.com>
On Fri, Mar 29, 2019 at 09:11:24AM -0500, Rob Herring wrote:
> I honestly don't understand the issue with EDAC is here.
The EDAC core supports only one driver and if you need to load more, you
need to dance around that.
Also, if those drivers need to talk amongst each other, then they need
to build something ad-hoc so that they can.
And the other architectures can very well do one driver per platform -
only ARM wants to do this special thing because DT said so. Or whatever.
> Highbank is separate drivers for L2 ECC (PL310) and DDR. Both are used
> on highbank.
That's because your L2 driver does allocate an edac_device
(edac_device_alloc_ctl_info()) and the DDR one an edac_mc
(edac_mc_add_mc_with_groups).
For example, altera_edac does edac_device_alloc_ctl_info() for each IP
block just fine. So a single driver *can* work.
> Only the DDR driver is used midway. (I think we never got around to
> how to report A15 L2 ECC errors within Linux.)
>
> In any case, it's all irrelevant to the DT binding. We don't design
> bindings around what some particular OS wants.
And just because DT dictates one driver per IP block, I'm not going to
redesign EDAC to fit that scheme. You or someone else who feels strongly
about it, is more than welcome to do so, of course. And then maintain it
too.
--
Regards/Gruss,
Boris.
Good mailing practices for 400: avoid top-posting and trim the reply.
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2019-03-29 14:27 UTC|newest]
Thread overview: 56+ 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:20 ` Yash Shah
2019-03-12 9:20 ` Yash Shah
2019-03-12 9:21 ` [PATCH 1/2] edac: sifive: Add DT documentation for SiFive L2 cache Controller Yash Shah
2019-03-12 9:21 ` Yash Shah
2019-03-12 9:21 ` [1/2] " Yash Shah
2019-03-28 13:16 ` [PATCH 1/2] " Rob Herring
2019-03-28 13:16 ` Rob Herring
2019-03-28 13:16 ` [1/2] " Rob Herring
2019-03-28 18:47 ` [PATCH 1/2] " James Morse
2019-03-28 18:47 ` James Morse
2019-03-28 18:47 ` [1/2] " James Morse
2019-03-29 14:11 ` [PATCH 1/2] " Rob Herring
2019-03-29 14:11 ` Rob Herring
2019-03-29 14:11 ` [1/2] " Rob Herring
2019-03-29 14:27 ` Borislav Petkov [this message]
2019-03-29 14:27 ` [PATCH 1/2] " Borislav Petkov
2019-03-29 14:27 ` [1/2] " Borislav Petkov
2019-03-29 19:41 ` [PATCH 1/2] " Rob Herring
2019-03-29 19:41 ` Rob Herring
2019-03-29 19:41 ` [1/2] " Rob Herring
2019-03-29 20:24 ` [PATCH 1/2] " Borislav Petkov
2019-03-29 20:24 ` Borislav Petkov
2019-03-29 20:24 ` [1/2] " Borislav Petkov
2019-04-04 1:04 ` [PATCH 1/2] " Rob Herring
2019-04-04 1:04 ` Rob Herring
2019-04-04 1:04 ` [1/2] " Rob Herring
2019-04-01 16:36 ` [PATCH 1/2] " James Morse
2019-04-01 16:36 ` James Morse
2019-04-01 16:36 ` [1/2] " James Morse
2019-04-04 1:17 ` [PATCH 1/2] " Rob Herring
2019-04-04 1:17 ` Rob Herring
2019-04-04 1:17 ` [1/2] " 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:21 ` Yash Shah
2019-03-12 9:21 ` [2/2] " Yash Shah
2019-03-12 9:28 ` [PATCH 2/2] " Borislav Petkov
2019-03-12 9:28 ` Borislav Petkov
2019-03-12 9:28 ` [2/2] " Borislav Petkov
2019-03-25 0:16 ` [PATCH 2/2] " Paul Walmsley
2019-03-25 0:16 ` Paul Walmsley
2019-03-25 0:16 ` [2/2] " Paul Walmsley
2019-03-25 6:54 ` [PATCH 2/2] " Borislav Petkov
2019-03-25 6:54 ` Borislav Petkov
2019-03-25 6:54 ` [2/2] " Borislav Petkov
2019-03-25 21:18 ` [PATCH 2/2] " Paul Walmsley
2019-03-25 21:18 ` Paul Walmsley
2019-03-25 21:18 ` [2/2] " Paul Walmsley
2019-03-25 21:47 ` [PATCH 2/2] " Borislav Petkov
2019-03-25 21:47 ` Borislav Petkov
2019-03-25 21:47 ` [2/2] " Borislav Petkov
2019-03-12 16:31 ` [PATCH 2/2] " Paul Walmsley
2019-03-12 16:31 ` Paul Walmsley
2019-03-12 16:31 ` [2/2] " Paul Walmsley
2019-03-12 16:32 ` [PATCH 0/2] L2 Cache EDAC Support for HiFive Unleashed Paul Walmsley
2019-03-12 16:32 ` 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=20190329142739.GG21152@zn.tnic \
--to=bp@alien8.de \
--cc=aou@eecs.berkeley.edu \
--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=robh@kernel.org \
--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 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.