From: Sinan Kaya <okaya@kernel.org>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: Christoph Hellwig <hch@infradead.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled
Date: Tue, 11 Dec 2018 17:22:25 -0500 [thread overview]
Message-ID: <6644defb-9199-6467-6e3e-8ce552b56f87@kernel.org> (raw)
In-Reply-To: <CAJZ5v0g5t4sx6mY=mCPWOdZLbhEAXo5Ah1TZw9jZNJQ-+cgWsw@mail.gmail.com>
On 12/11/2018 5:16 PM, Rafael J. Wysocki wrote:
>> AFAIK, ACPI spec says that AML code running on non-existing op-regions to be
>> discarded last time I checked.
> I guess you mean "disregarded"?
>
I have seen Linux complain about reads/writes to non-existing I2C opregions
before as a read/write failure for every single AML transaction. I was under the
impression that we didn't care.
> So the spec appears to expect the OS to silently ignore the failures
> in those cases, so why should an error be returned?
>
I can certainly return success for this case when CONFIG_PCI is not present.
>> I know Linux is noisy about these.
next prev parent reply other threads:[~2018-12-11 22:22 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-10 18:13 [PATCH v3 1/3] ACPI: Allow PCI to be disabled for reboot Sinan Kaya
2018-12-10 18:13 ` [PATCH v3 2/3] ACPI / OSL: Allow PCI to be disabled Sinan Kaya
2018-12-11 10:07 ` Rafael J. Wysocki
2018-12-11 16:52 ` Sinan Kaya
2018-12-11 17:09 ` Christoph Hellwig
2018-12-11 17:37 ` Sinan Kaya
2018-12-11 21:46 ` Rafael J. Wysocki
2018-12-11 21:57 ` Sinan Kaya
2018-12-11 22:16 ` Rafael J. Wysocki
2018-12-11 22:22 ` Sinan Kaya [this message]
2018-12-11 22:51 ` Rafael J. Wysocki
2018-12-11 23:00 ` Sinan Kaya
2018-12-10 18:13 ` [PATCH v3 3/3] PCI/ACPI: Allow ACPI to be built without PCI support 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=6644defb-9199-6467-6e3e-8ce552b56f87@kernel.org \
--to=okaya@kernel.org \
--cc=hch@infradead.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox