LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: Al Stone <ahs3@redhat.com>
Cc: linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org,
Prashanth Prakash <pprakash@codeaurora.org>
Subject: Re: [PATCH v3 0/3] mailbox: ACPI: Remove incorrect error message about parsing PCCT
Date: Sun, 13 May 2018 10:30:05 +0200 [thread overview]
Message-ID: <190779407.lJoETU6Q66@aspire.rjw.lan> (raw)
In-Reply-To: <20180501003907.4322-1-ahs3@redhat.com>
On Tuesday, May 1, 2018 2:39:04 AM CEST Al Stone wrote:
> This set of patches provide some cleanup in ACPI for minor issues
> found while correcting a bogus error message (the first two patches),
> and the correction for the error message itself (patch 3/3). Note
> that patches 1/3 and 2/3 are not required for 3/3 to work: 1/3 only
> changes a comment and 2/3 makes an ACPI table parsing loop a wee bit
> more robust.
>
> For patch 3/3, many systems on boot have been reporting "Error parsing
> PCC subspaces from PCCT" which turns out to not be an error at all.
> The issue is that the probe for ACPI mailboxes defined in the PCCT
> (Platform Communications Channel Table) makes a faulty assumption about
> the content of the PCCT. What's more, when the error is reported, no
> further PCC mailboxes are set up, even when they have been defined
> in the PCCT. So, in the reported cases, there was no error and the
> data in the PCCT was being ignored. This is described in more detail
> in patch 3/3.
>
> Since these patches primarily involve ACPI usages, it may make
> sense for all of them to go through the linux-acpi tree; clearly,
> this is up to the maintainers, though.
>
> v3:
> -- properly format docbook info in patch 1/3
> -- remove extra parens in patch 2/3
> -- clean up formatting, remove pr_warn() calls used in debugging but
> providing no value, clean up docbook info for count_pcc_subspaces()
> and parse_pcc_subspaces(), all in patch 3/3
>
> v2:
> -- removed one extraneous '+' in a comment in patch 3/3
> -- fixed an if test that had a predicate that kbuild pointed out would
> always be zero
>
> Al Stone (3):
> ACPI: improve function documentation for acpi_parse_entries_array()
> ACPI: ensure acpi_parse_entries_array() does not access non-existent
> table data
> mailbox: ACPI: erroneous error message when parsing the ACPI PCCT
>
> drivers/acpi/tables.c | 12 ++++---
> drivers/mailbox/pcc.c | 96 +++++++++++++++++++++++++++++++++------------------
> 2 files changed, 71 insertions(+), 37 deletions(-)
I've applied [1-2/3] and I'm waiting on input from Prashanth on the [3/3].
Thanks,
Rafael
prev parent reply other threads:[~2018-05-13 8:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-01 0:39 Al Stone
2018-05-01 0:39 ` [PATCH v3 1/3] ACPI: improve function documentation for acpi_parse_entries_array() Al Stone
2018-05-01 0:39 ` [PATCH v3 2/3] ACPI: ensure acpi_parse_entries_array() does not access non-existent table data Al Stone
2018-05-15 17:19 ` Rafael J. Wysocki
2018-05-15 21:53 ` Al Stone
2018-05-16 15:09 ` Al Stone
2018-05-01 0:39 ` [PATCH v3 3/3] mailbox: ACPI: erroneous error message when parsing the ACPI PCCT Al Stone
2018-05-12 11:49 ` Rafael J. Wysocki
2018-05-14 21:04 ` Prakash, Prashanth
2018-05-14 22:49 ` Al Stone
2018-05-15 8:00 ` Rafael J. Wysocki
2018-05-16 22:01 ` [PATCH v4 3/3] mailbox: ACPI: erroneous error message when parsing the ACPI, PCCT Al Stone
2018-05-17 10:24 ` Rafael J. Wysocki
2018-05-17 19:48 ` Prakash, Prashanth
2018-05-23 11:34 ` Rafael J. Wysocki
2018-05-16 22:03 ` [PATCH v3 3/3] mailbox: ACPI: erroneous error message when parsing the ACPI PCCT Al Stone
2018-05-13 8:30 ` Rafael J. Wysocki [this message]
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=190779407.lJoETU6Q66@aspire.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=ahs3@redhat.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pprakash@codeaurora.org \
--subject='Re: [PATCH v3 0/3] mailbox: ACPI: Remove incorrect error message about parsing PCCT' \
/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
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).