From: Alex Hung <alex.hung@canonical.com>
To: rjw@rjwysocki.net, lenb@kernel.org, alex.hung@canonical.com,
linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: [PATCH] ACPI/PCI: pci_link: change log level of no _PRS messages
Date: Fri, 9 Feb 2018 14:56:43 -0800 [thread overview]
Message-ID: <1518217003-19637-1-git-send-email-alex.hung@canonical.com> (raw)
In recent Intel hardware the IRQs become non-configurable after BIOS
initializes them in PEI phase and _PRS objects are no longer included in
ASL.
This is the same as "static (non-configurable) devices do not
specify a _PRS object" in ACPI spec. As a result, error messages
saying "ACPI Exception: AE_NOT_FOUND, Evaluating _PRS" does not need to
be in kernel messages all the time but only when debug is enabled.
Signed-off-by: Alex Hung <alex.hung@canonical.com>
---
drivers/acpi/pci_link.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/acpi/pci_link.c b/drivers/acpi/pci_link.c
index 85ad679..9d9cf24 100644
--- a/drivers/acpi/pci_link.c
+++ b/drivers/acpi/pci_link.c
@@ -173,7 +173,7 @@ static int acpi_pci_link_get_possible(struct acpi_pci_link *link)
status = acpi_walk_resources(link->device->handle, METHOD_NAME__PRS,
acpi_pci_link_check_possible, link);
if (ACPI_FAILURE(status)) {
- ACPI_EXCEPTION((AE_INFO, status, "Evaluating _PRS"));
+ acpi_handle_debug(link->device->handle, "failed to evaluate _PRS");
return -ENODEV;
}
--
2.7.4
next reply other threads:[~2018-02-09 22:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-09 22:56 Alex Hung [this message]
2018-02-10 1:05 ` [PATCH] ACPI/PCI: pci_link: change log level of no _PRS messages Bjorn Helgaas
2018-02-10 7:40 ` Alex Hung
2018-02-10 8:08 ` Rafael J. Wysocki
2018-02-10 15:34 ` Bjorn Helgaas
2018-02-12 8:51 ` Rafael J. Wysocki
2018-02-12 8:58 ` Rafael J. Wysocki
2018-02-13 4:03 ` Alex Hung
2018-02-13 8:49 ` Rafael J. Wysocki
2018-02-23 5:42 ` Alex Hung
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=1518217003-19637-1-git-send-email-alex.hung@canonical.com \
--to=alex.hung@canonical.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=rjw@rjwysocki.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.