linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: "Limonciello, Mario" <Mario.Limonciello@dell.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
	"open list:ULTRA-WIDEBAND (UWB) SUBSYSTEM:" 
	<linux-usb@vger.kernel.org>,
	Michael Jamet <michael.jamet@intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Andreas Noever <andreas.noever@gmail.com>,
	Lukas Wunner <lukas@wunner.de>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Christian Kellner <christian@kellner.me>,
	Len Brown <lenb@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH 4/6] ACPI: Execute platform _OSC also with query bit clear
Date: Wed, 27 Jan 2021 14:49:35 +0200	[thread overview]
Message-ID: <20210127124935.GC2542@lahna.fi.intel.com> (raw)
In-Reply-To: <SA1PR19MB4926A9A1E4D0AD96FAE236B3FABC9@SA1PR19MB4926.namprd19.prod.outlook.com>

On Tue, Jan 26, 2021 at 10:43:32PM +0000, Limonciello, Mario wrote:
> > I would put that information into the changelog.
> 
> Thanks, @Mika Westerberg can you collapse that in when you re-spin the
> series?

Sure.

> > 
> > Moreover, have you looked at acpi_pci_osc_control_set()?
> > 
> > What it does is analogous to what you are proposing, but a bit
> > different, and I would like to preserve consistency between _OSC use
> > cases.
> > 
> > So would it be possible to adjust the _SB _OSC evaluation flow to
> > follow the PCI _OSC one?  That is, if any control bits are there, pass
> > them along with the last evaluation of _OSC with the query flag clear.
> > Or is the latter defective and if so then why?
> 
> Basically the only difference is another line cloning OSC_CONTROL_DWORD from
> capbuf_ret to capbuf?
> 
> Yes, this actually sounds like it better adheres to the spec to me.
> 
> Quoting spec:
> " If the OS is granted control of a feature in the Control Field in one call to
> _OSC, then it must preserve the set state of that bit (requesting that feature)
> in all subsequent calls."

However, the platform wide _OSC does not actually have this
OSC_CONTROL_DWORD at all ;-)

I think what we do in this patch is already equivalent to what the PCI
_OSC is doing:

  1. Query bit set _OSC
  2. Take the returned OSC_SUPPORT_DWORD buffer and
  3. Pass it to the _OSC with query bit clear.

I may be missing something, though.

  reply	other threads:[~2021-01-27 12:55 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-26 15:57 [PATCH 0/6] thunderbolt / ACPI: Add support for USB4 _OSC Mika Westerberg
2021-01-26 15:57 ` [PATCH 1/6] thunderbolt: Fix possible NULL pointer dereference in tb_acpi_add_link() Mika Westerberg
2021-01-28 12:36   ` Mika Westerberg
2021-01-26 15:57 ` [PATCH 2/6] thunderbolt: Add support for PCIe tunneling disabled (SL5) Mika Westerberg
2021-01-26 16:18   ` Yehezkel Bernat
2021-01-26 16:26     ` Mika Westerberg
2021-01-26 16:29       ` Yehezkel Bernat
2021-01-26 15:57 ` [PATCH 3/6] thunderbolt: Allow disabling XDomain protocol Mika Westerberg
2021-01-26 15:57 ` [PATCH 4/6] ACPI: Execute platform _OSC also with query bit clear Mika Westerberg
2021-01-26 16:25   ` Yehezkel Bernat
2021-01-26 17:21   ` Rafael J. Wysocki
2021-01-26 17:37     ` Limonciello, Mario
2021-01-26 17:42       ` Rafael J. Wysocki
2021-01-26 22:43         ` Limonciello, Mario
2021-01-27 12:49           ` Mika Westerberg [this message]
2021-01-27 13:50             ` Rafael J. Wysocki
2021-01-26 15:57 ` [PATCH 5/6] ACPI: Add support for native USB4 control _OSC Mika Westerberg
2021-01-26 17:35   ` Rafael J. Wysocki
2021-01-26 17:46     ` Mika Westerberg
2021-01-26 18:25       ` Rafael J. Wysocki
2021-01-26 18:27   ` Rafael J. Wysocki
2021-01-26 15:57 ` [PATCH 6/6] thunderbolt: Add support for native USB4 _OSC Mika Westerberg
2021-01-26 16:37 ` [PATCH 0/6] thunderbolt / ACPI: Add support for " Yehezkel Bernat

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=20210127124935.GC2542@lahna.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=Mario.Limonciello@dell.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=christian@kellner.me \
    --cc=gregkh@linuxfoundation.org \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --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;
as well as URLs for NNTP newsgroup(s).