From: Bjorn Helgaas <helgaas@kernel.org>
To: Duc Dang <dhdang@apm.com>
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Punit Agrawal <punit.agrawal@arm.com>,
Marc Zyngier <marc.zyngier@arm.com>,
Rafael Wysocki <rafael@kernel.org>,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
patches <patches@apm.com>, Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Defining polarity and trigger mode for static interrupts in _PRT
Date: Thu, 25 Aug 2016 12:20:29 -0500 [thread overview]
Message-ID: <20160825172029.GC11257@localhost> (raw)
In-Reply-To: <CADaLNDkJ5wQC-59oD26J0F8T+pP5BEJcSTN16j_EYm-pmfPi=A@mail.gmail.com>
On Thu, Aug 25, 2016 at 09:46:25AM -0700, Duc Dang wrote:
> On Thu, Aug 25, 2016 at 4:14 AM, Lorenzo Pieralisi <lorenzo.pieralisi@arm.com> wrote:
> > On Thu, Aug 25, 2016 at 11:04:02AM +0100, Punit Agrawal wrote:
> >> If there are no good reason to restrict using link devices to
> >> configurable interrupts, perhaps the spec needs an update.
> >
> > Yes and that's what I am going to ask if nobody complains.
>
> In my opinion, if the interrupt is not configurable, I should be able
> to choose not to use interrupt link, which requires a spec. update as
> well to specify the polarity of the fixed interrupts?
This is a little out of my area, but I really don't see the point of
an ACPI spec update. PCI has specified level/low and ACPI systems
have worked that way for decades.
Can't you just make your GIC driver aware of the fact that some of
its inputs have inverters on them and are effectively active low?
Then all the generic code should work just like it does on other
systems.
next prev parent reply other threads:[~2016-08-25 17:20 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CADaLNDm-HmnOsrntDC8zz28bwiQZVv36LG-iMDATqzavY7cXVg@mail.gmail.com>
2016-08-24 14:27 ` Defining polarity and trigger mode for static interrupts in _PRT Lorenzo Pieralisi
2016-08-24 19:30 ` Bjorn Helgaas
2016-08-24 20:30 ` Marc Zyngier
2016-08-24 22:19 ` Duc Dang
2016-08-24 22:56 ` Bjorn Helgaas
2016-08-25 11:18 ` Marc Zyngier
2016-08-25 16:52 ` Duc Dang
2016-08-25 18:59 ` Marc Zyngier
2016-08-26 9:08 ` Lorenzo Pieralisi
2016-08-26 11:04 ` okaya
2016-08-26 12:08 ` Marc Zyngier
2016-08-26 14:07 ` Sinan Kaya
2016-08-26 17:06 ` Lorenzo Pieralisi
2016-08-26 22:53 ` Sinan Kaya
2016-08-30 10:08 ` Lorenzo Pieralisi
2016-08-30 15:51 ` Duc Dang
2016-08-30 17:54 ` Sinan Kaya
2016-08-31 10:07 ` Lorenzo Pieralisi
2016-08-31 13:05 ` Bjorn Helgaas
2016-08-31 13:34 ` Lorenzo Pieralisi
2016-08-31 16:05 ` Bjorn Helgaas
2016-08-31 16:37 ` Lorenzo Pieralisi
2016-08-31 23:08 ` Rafael J. Wysocki
2016-09-02 11:09 ` Lorenzo Pieralisi
2016-09-02 21:28 ` Rafael J. Wysocki
2016-08-25 10:04 ` Punit Agrawal
2016-08-25 11:14 ` Lorenzo Pieralisi
2016-08-25 16:46 ` Duc Dang
2016-08-25 17:20 ` Bjorn Helgaas [this message]
2016-08-24 15:26 ` Marc Zyngier
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=20160825172029.GC11257@localhost \
--to=helgaas@kernel.org \
--cc=bhelgaas@google.com \
--cc=dhdang@apm.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=marc.zyngier@arm.com \
--cc=patches@apm.com \
--cc=punit.agrawal@arm.com \
--cc=rafael@kernel.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;
as well as URLs for NNTP newsgroup(s).