From: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
To: Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
linux-pm@lists.linux-foundation.org, linux-pci@vger.kernel.org,
Jesse Barnes <jbarnes@virtuousgeek.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [linux-pm] [PATCH 7/8] ACPI / PCI: Do not preserve _OSC control bits returned by a query (v2)
Date: Wed, 04 Aug 2010 18:39:19 +0900 [thread overview]
Message-ID: <4C593547.2040700@jp.fujitsu.com> (raw)
In-Reply-To: <4C59284F.9080808@jp.fujitsu.com>
(2010/08/04 17:43), Hidetoshi Seto wrote:
> (2010/08/04 14:46), Kenji Kaneshige wrote:
>> By the way, I think it is getting confusing regarding who query the
>> controls. IMO, querying controls to ensure all the requested controls
>> are granted to OS should be done in acpi_pci_osc_control_set(), as
>> I said above. On the other hand, PCIe port driver need to query
>> controls for other reason... Now I think it might be better to change
>> acpi_pci_osc_control_set() like below instead of introducing
>> acpi_pci_osc_control_query().
>>
>> acpi_status acpi_pci_osc_control_set(acpi_handle handle, u32 *flags)
>> {
>> ...
>> query = control_req;
>> status = acpi_pci_query_osc(root, root->osc_support_set,&query);
>> if (ACPI_FAILURE(status))
>> goto out;
>> if ((query& control_req) != control_req) {
>> printk_(KERN_DEBUG
>> "Firmware did not grant requested _OSC control\n");
>> status = AE_SUPPORT;
>> *flags = (query& control_req);
>> goto out;
>> }
>> ...
>> }
>>
>> And do as follows in pcie_port_acpi_setup()
>>
>> status = acpi_pci_osc_control_set(handle,&flags);
>> if (status == AE_SUPPORT) {
>> /* 2nd try */
>> status = acpi_pci_osc_control_set(handle,&flags);
>> }
>> if (ACPI_FAILURE(status)) {
>> ...
>>
>> What do you think about this?
>
> I think it makes sense, though some minor cares are required.
>
> Does this incremental patch (apply after [8/8]) looks good?
> If it is OK, I'll test these 8+1 patches within the next 2days.
>
> Thanks,
> H.Seto
>
> =====
> Subject: ACPI/PCI: Unify acpi_pci_osc_control_*()
>
> Now AE_SUPPORT of acpi_pci_osc_control_set() tells not only
> that query fails with the requested control bits but also that
> the result of query is stored into the pointed place.
>
> This allow user to retry acpi_pci_osc_control_set() with the
> result of query.
>
> Signed-off-by: Hidetoshi Seto<seto.hidetoshi@jp.fujitsu.com>
> ---
> drivers/acpi/pci_root.c | 54 +++++++++++--------------------------
> drivers/pci/hotplug/acpi_pcihp.c | 2 +-
> drivers/pci/pcie/portdrv_acpi.c | 23 +++++++---------
> include/linux/acpi.h | 3 +-
> 4 files changed, 28 insertions(+), 54 deletions(-)
<snip.>
> /**
> * acpi_pci_osc_control_set - commit requested control to Firmware
> * @handle: acpi_handle for the target ACPI object
> @@ -411,14 +379,17 @@ acpi_status acpi_pci_osc_control_query(acpi_handle handle, u32 *mask)
> *
> * Attempt to take control from Firmware on requested control bits.
> **/
Updating description of this function would be appreciated.
<snip.>
> @@ -452,7 +427,10 @@ acpi_status acpi_pci_osc_control_set(acpi_handle handle, u32 flags)
> capbuf[OSC_CONTROL_TYPE] = root->osc_control_set | control_req;
> status = acpi_pci_run_osc(handle, capbuf,&result);
> if (ACPI_SUCCESS(status))
> - root->osc_control_set = result;
> + root->osc_control_set = *flags = result;
I don't think we need to update *flags here, though it depends on the design
of this function interface.
IMHO, updating *flags only when AE_SUPPORT is returned is easy to understand.
Others looks good to me.
Thanks,
Kenji Kaneshige
next prev parent reply other threads:[~2010-08-04 9:39 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-02 21:51 [PATCH 0/8] ACPI / PCI / PCIe: Rework _OSC handling (v2) Rafael J. Wysocki
2010-08-02 21:53 ` [PATCH 1/8] ACPI / PCI: Introduce acpi_pci_osc_control_query() Rafael J. Wysocki
2010-08-03 4:52 ` Kenji Kaneshige
2010-08-03 9:24 ` Rafael J. Wysocki
2010-08-03 5:04 ` Kenji Kaneshige
2010-08-03 9:27 ` Rafael J. Wysocki
2010-08-03 20:58 ` [linux-pm] " Rafael J. Wysocki
2010-08-04 4:28 ` Kenji Kaneshige
2010-08-04 23:37 ` Rafael J. Wysocki
2010-08-05 23:46 ` Rafael J. Wysocki
2010-08-02 21:54 ` [PATCH 2/8] PCI / PCIe/ AER: Introduce pci_aer_available() Rafael J. Wysocki
2010-08-03 0:46 ` Hidetoshi Seto
2010-08-03 9:28 ` Rafael J. Wysocki
2010-08-03 20:59 ` [linux-pm] " Rafael J. Wysocki
2010-08-03 9:41 ` Jike Song
2010-08-03 19:50 ` Rafael J. Wysocki
2010-08-02 21:55 ` [PATCH 3/8] PCI / PCIe: Introduce commad line switch for disabling port services Rafael J. Wysocki
2010-08-02 21:56 ` [PATCH 4/8] PCI / PCIe: Ask BIOS for control of all native services at once (v6) Rafael J. Wysocki
2010-08-03 1:14 ` Hidetoshi Seto
2010-08-03 21:01 ` Rafael J. Wysocki
2010-08-06 1:33 ` Hidetoshi Seto
2010-08-06 10:47 ` Rafael J. Wysocki
2010-08-02 21:57 ` [PATCH 5/8] PCI / PCIe: Disable PCIe port services during port initialization Rafael J. Wysocki
2010-08-02 21:58 ` [PATCH 6/8] PCI / PCIe: Remove the port driver module exit routine Rafael J. Wysocki
2010-08-02 21:59 ` [PATCH 7/8] ACPI / PCI: Do not preserve _OSC control bits returned by a query (v2) Rafael J. Wysocki
2010-08-03 4:52 ` Kenji Kaneshige
2010-08-03 7:13 ` Hidetoshi Seto
2010-08-03 9:33 ` Rafael J. Wysocki
2010-08-03 21:02 ` [linux-pm] " Rafael J. Wysocki
2010-08-04 5:46 ` Kenji Kaneshige
2010-08-04 8:41 ` Hidetoshi Seto
2010-08-04 9:23 ` Kenji Kaneshige
2010-08-04 10:29 ` Rafael J. Wysocki
2010-08-04 23:51 ` Rafael J. Wysocki
2010-08-05 3:40 ` Hidetoshi Seto
2010-08-05 14:25 ` Rafael J. Wysocki
2010-08-06 1:28 ` Hidetoshi Seto
2010-08-04 8:43 ` Hidetoshi Seto
2010-08-04 9:39 ` Kenji Kaneshige [this message]
2010-08-04 12:15 ` Rafael J. Wysocki
2010-08-05 3:38 ` [linux-pm] " Hidetoshi Seto
2010-08-04 10:38 ` Rafael J. Wysocki
2010-08-02 22:00 ` [PATCH 8/8] ACPI / PCI: Reorder checks in acpi_pci_osc_control_set() Rafael J. Wysocki
2010-08-03 4:51 ` [PATCH 0/8] ACPI / PCI / PCIe: Rework _OSC handling (v2) Kenji Kaneshige
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=4C593547.2040700@jp.fujitsu.com \
--to=kaneshige.kenji@jp.fujitsu.com \
--cc=jbarnes@virtuousgeek.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=rjw@sisk.pl \
--cc=seto.hidetoshi@jp.fujitsu.com \
/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).