From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] edac: xgene: fix cpuid abuse
Date: Mon, 01 Jun 2015 20:09:55 +0200 [thread overview]
Message-ID: <1702535.joP9YpVrU1@wuerfel> (raw)
In-Reply-To: <CAPw-ZT=591MT3HZcZ7TsfD_13mEJQ5swsw3kV2BoVxYUaYADCA@mail.gmail.com>
On Monday 01 June 2015 10:04:51 Loc Ho wrote:
> Hi Arnd,
>
> Thanks for the changes, some minor change requested below.
>
> > The new x-gene EDAC driver incorrectly tried to figure out the version of
> > one of its IP blocks by looking at the version of the CPU core, which is
> > only vagely related.
> >
> > This removes the incorrect code and instead uses the version of the IP
> > block in the compatible string where it belongs.
> >
> > Found using build testing on x86, which does not provide the arm64
> > cpuid interface.
> >
> > Signed-off-by: Arnd Bergmann <arnd@arndb.de>
> > ---
> >
> > How about this one? We should make sure this gets fixed before the binding
> > gets set in stone with a kernel release.
> >
> > Loc, do you know if some of the other blocks might also have versions
> > associated with them? Normally we try to use more specific product names,
> > but in case of APM there don't seem to be any more specific names
> > than X-Gene and X-Gene2 any more.
> >
>
> I already asked the designer. There is no version register in the PMD block.
Ok.
> > diff --git a/Documentation/devicetree/bindings/edac/apm-xgene-edac.txt b/Documentation/devicetree/bindings/edac/apm-xgene-edac.txt
> > index 480911c38ff9..e31b696ba939 100644
> > --- a/Documentation/devicetree/bindings/edac/apm-xgene-edac.txt
> > +++ b/Documentation/devicetree/bindings/edac/apm-xgene-edac.txt
> > @@ -25,7 +25,7 @@ Required properties for memory controller subnode:
> > - memory-controller : Instance number of the memory controller.
> >
> > Required properties for PMD subnode:
> > -- compatible : Shall be "apm,xgene-edac-pmd".
> > +- compatible : Shall be "apm,xgene-edac-pmd" or "apm,xgene-v2-edac-pmd"
>
> Can we change to "apm,xgene-edac-pmd-v2". I would like to associate
> with the PMD instead with the family name. The PMD (processor module)
> might be re-use in future chip as is such as Gen3, Gen4, and etc.
Makes sense.
> > + xgene_edac_pmd_add(edac, child, 1);
> > + if (of_device_is_compatible(child, "apm,xgene-v2-edac-pmd"))
>
> Change to "apm,xgene-edac-pmd-v2"
>
>
> > + xgene_edac_pmd_add(edac, child, 2);
> > }
> >
> > return 0;
>
> Again... Thanks for the changes.
Can you send a fixed version of the patch?
Arnd
next prev parent reply other threads:[~2015-06-01 18:09 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-22 23:32 [PATCH v11 0/4] edac: Add APM X-Gene SoC EDAC driver Loc Ho
2015-05-22 23:32 ` [PATCH v11 1/5] arm64: Enable EDAC on ARM64 Loc Ho
2015-05-22 23:32 ` [PATCH v11 2/5] MAINTAINERS: Add entry for APM X-Gene SoC EDAC driver Loc Ho
2015-05-22 23:32 ` [PATCH v11 3/5] Documentation: Add documentation for the APM X-Gene SoC EDAC DTS binding Loc Ho
2015-05-22 23:32 ` [PATCH v11 4/5] edac: Add APM X-Gene SoC EDAC driver Loc Ho
2015-05-22 23:33 ` [PATCH v11 5/5] arm64: Add APM X-Gene SoC EDAC DTS entries Loc Ho
2015-06-01 14:42 ` [PATCH v11 4/5] edac: Add APM X-Gene SoC EDAC driver Arnd Bergmann
2015-06-01 15:11 ` Catalin Marinas
2015-06-01 15:17 ` Mark Rutland
2015-06-01 15:27 ` [PATCH] edac: xgene: fix cpuid abuse Arnd Bergmann
2015-06-01 17:04 ` Loc Ho
2015-06-01 18:09 ` Arnd Bergmann [this message]
2015-05-29 9:46 ` [PATCH v11 0/4] edac: Add APM X-Gene SoC EDAC driver Borislav Petkov
2015-05-29 18:06 ` Loc Ho
2015-05-29 18:59 ` Borislav Petkov
2015-05-29 20:05 ` [PATCH] EDAC, edac_stub: Drop arch-specific include Borislav Petkov
2015-05-29 21:25 ` Loc Ho
2015-05-29 21:41 ` Borislav Petkov
2015-05-29 20:18 ` [PATCH v11 0/4] edac: Add APM X-Gene SoC EDAC driver Loc Ho
-- strict thread matches above, loose matches on Subject: below --
2015-06-01 22:09 [PATCH] edac: xgene: fix cpuid abuse Loc Ho
2015-06-02 19:10 ` Borislav Petkov
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=1702535.joP9YpVrU1@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.org \
/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