From: Vikas C Sajjan <vikas.cha.sajjan@hpe.com>
To: tglx@linutronix.de, rjw@rjwysocki.net, rafael.j.wysocki@intel.com
Cc: linux-pm@vger.kernel.org, linux-acpi@vger.kernel.org,
linux-kernel@vger.kernel.org, kkamagui@gmail.com,
mingo@kernel.org, Vikas C Sajjan <vikas.cha.sajjan@hpe.com>
Subject: [PATCH v2 0/2] Fix improper handling of SCI INT for platforms supporting only IOAPIC mode
Date: Thu, 16 Nov 2017 14:59:53 +0530 [thread overview]
Message-ID: <1510824595-12287-1-git-send-email-vikas.cha.sajjan@hpe.com> (raw)
The platforms which support only IOAPIC mode and whose SCI INT is
greater than 16, passes SCI INT via FADT and not via MADT int src override
structure. In such cases current logic fails to handle it and throws error
"Invalid bus_irq %u for legacy override". This patch handles the above
mentioned case. While at it, also modify function mp_override_legacy_irq()
to use the newly introduced function mp_register_ioapic_irq().
This series is rebased on 'master' branch of
https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
Changes since v1:
Patch is split into 2, separating actual fix and code cleanup
as suggested by Rafael.
Vikas C Sajjan (2):
acpi/x86: Fix improper handling of SCI INT for platforms supporting
only IOAPIC mode
acpi/x86: Reuse the mp_register_ioapic_irq() in the function
mp_override_legacy_irq()
arch/x86/kernel/acpi/boot.c | 64 +++++++++++++++++++++++++++++----------------
1 file changed, 41 insertions(+), 23 deletions(-)
--
1.9.1
next reply other threads:[~2017-11-16 9:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-16 9:29 Vikas C Sajjan [this message]
2017-11-16 9:29 ` [PATCH v2 1/2] acpi/x86: Fix improper handling of SCI INT for platforms supporting only IOAPIC mode Vikas C Sajjan
2017-11-16 11:04 ` Thomas Gleixner
2017-11-16 11:36 ` Sajjan, Vikas C
2017-11-16 12:16 ` Thomas Gleixner
2017-11-16 9:29 ` [PATCH v2 2/2] acpi/x86: Reuse the mp_register_ioapic_irq() in the function mp_override_legacy_irq() Vikas C Sajjan
2017-11-16 11:05 ` Thomas Gleixner
2017-11-16 11:37 ` Sajjan, Vikas C
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=1510824595-12287-1-git-send-email-vikas.cha.sajjan@hpe.com \
--to=vikas.cha.sajjan@hpe.com \
--cc=kkamagui@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=rafael.j.wysocki@intel.com \
--cc=rjw@rjwysocki.net \
--cc=tglx@linutronix.de \
/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).