From: Mathias Nyman <mathias.nyman@linux.intel.com>
To: Yinbo Zhu <zhuyinbo@loongson.cn>,
Mathias Nyman <mathias.nyman@intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] usb: xhci: add LPM quirk for ensuring uPD720201 into D3 state after S5
Date: Mon, 1 Nov 2021 11:18:39 +0200 [thread overview]
Message-ID: <f7cfa6bc-a0f6-aaa6-aafa-b4fe2714ca40@linux.intel.com> (raw)
In-Reply-To: <1635751025-25906-1-git-send-email-zhuyinbo@loongson.cn>
Hi
On 1.11.2021 9.17, Yinbo Zhu wrote:
> After S5, any pci device should into D3 state that if supported, but the
> uPD720201 was not and it may be the cause of xhci firmware and cause
> OSPM power consumption is more higher that S5 than S4. I think xhci HCD
> can add a quirk ensure it into D3 state after S5 that is appropriate
> and this patch was to add LPM quirk and set PCI_D3hot to uPD720201 pmsc
> register in xhci_pci_shutdown to fix xhci power consumption issue.
>
> Signed-off-by: Yinbo Zhu <zhuyinbo@loongson.cn>
I think we need a better understanding of the underlying issue before
adding a quirk like this.
Is this a known issue with the uPD720201 controller firmware? or is it
an issue with ACPI table entries not supporting the proper D state in BIOS
on the tested platform, or something completely different?
Also, LPM usually refers to "Link Power Management" in the xHCI spec.
This is about the U1 and U2 link states for the connected USB device.
If we end up needing a new xhci quirk it will need a new name.
Thanks
-Mathias
next prev parent reply other threads:[~2021-11-01 9:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-01 7:17 [PATCH v1] usb: xhci: add LPM quirk for ensuring uPD720201 into D3 state after S5 Yinbo Zhu
2021-11-01 9:18 ` Mathias Nyman [this message]
2021-11-03 8:34 ` zhuyinbo
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=f7cfa6bc-a0f6-aaa6-aafa-b4fe2714ca40@linux.intel.com \
--to=mathias.nyman@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mathias.nyman@intel.com \
--cc=zhuyinbo@loongson.cn \
/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