From: bp@alien8.de (Borislav Petkov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] apei: xgene: Add ACPI APEI support for X-Gene
Date: Tue, 6 Oct 2015 13:31:33 +0200 [thread overview]
Message-ID: <20151006113133.GA28484@nazgul.tnic> (raw)
In-Reply-To: <CAPw-ZTn5stnEobMH018oLPn3nDO1uweVeVs=Otg3-6cXBWLz6g@mail.gmail.com>
On Mon, Oct 05, 2015 at 01:41:58PM -0700, Loc Ho wrote:
> Yes... We can make this generic. The only non-generic is the way the
> interrupt is cleared. As of right now, the method of clearing the
> interrupt is by writing back the same value as read. This would be
> fine for most.
Fine for most what? APM hardware, other hw?
> But to ensure 100% coverage, would an AML method be better or needed?
No idea, I'm not an ACPI guy. You probably should get in touch with the
people working on the ARM64 APEI driver and hash that out with them.
HTH.
--
Regards/Gruss,
Boris.
ECO tip #101: Trim your mails when you reply.
--
next prev parent reply other threads:[~2015-10-06 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-02 0:51 [PATCH RFC] apei: xgene: Add ACPI APEI support for X-Gene Loc Ho
2015-10-02 7:54 ` Borislav Petkov
2015-10-05 20:41 ` Loc Ho
2015-10-06 11:31 ` Borislav Petkov [this message]
2015-10-07 19:55 ` Loc Ho
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=20151006113133.GA28484@nazgul.tnic \
--to=bp@alien8.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