linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: linux-acpi@vger.kernel.org, timur@codeaurora.org, cov@codeaurora.org
Cc: linux-pci@vger.kernel.org, ravikanth.nalla@hpe.com,
	lenb@kernel.org, harish.k@hpe.com, ashwin.reghunandanan@hpe.com,
	bhelgaas@google.com, rjw@rjwysocki.net,
	Sinan Kaya <okaya@codeaurora.org>
Subject: [PATCH V2 0/3] simplify ACPI PCI IRQ code
Date: Fri,  8 Apr 2016 21:26:29 -0400	[thread overview]
Message-ID: <1460165192-4526-1-git-send-email-okaya@codeaurora.org> (raw)

differences from V1: https://patchwork.ozlabs.org/patch/599869/

Implement acpi_link_trigger and acpi_pci_compatible_trigger functions to
validate that all requesters agree on the IRQ polarity and trigger before
claiming for PCI and SCI interrupts.


Sinan Kaya (3):
  acpi,pci,irq: reduce resource requirements
  acpi,pci,irq: remove redundant code in acpi_irq_penalty_init
  acpi,pci,irq: remove SCI penalize function

 arch/x86/kernel/acpi/boot.c |   1 -
 arch/x86/pci/acpi.c         |   1 -
 drivers/acpi/pci_link.c     | 185 +++++++++++++++++++++++++++++---------------
 include/acpi/acpi_drivers.h |   1 -
 include/linux/acpi.h        |   1 -
 5 files changed, 122 insertions(+), 67 deletions(-)

-- 
1.8.2.1


             reply	other threads:[~2016-04-09  1:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-09  1:26 Sinan Kaya [this message]
2016-04-09  1:26 ` [PATCH V2 1/3] acpi,pci,irq: reduce resource requirements Sinan Kaya
2016-04-12  5:19   ` Bjorn Helgaas
2016-04-12 16:25     ` Sinan Kaya
2016-04-09  1:26 ` [PATCH V2 2/3] acpi,pci,irq: remove redundant code in acpi_irq_penalty_init Sinan Kaya
2016-04-09  1:26 ` [PATCH V2 3/3] acpi,pci,irq: remove SCI penalize function Sinan Kaya

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=1460165192-4526-1-git-send-email-okaya@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=ashwin.reghunandanan@hpe.com \
    --cc=bhelgaas@google.com \
    --cc=cov@codeaurora.org \
    --cc=harish.k@hpe.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=ravikanth.nalla@hpe.com \
    --cc=rjw@rjwysocki.net \
    --cc=timur@codeaurora.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).