All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Limonciello, Mario" <mario.limonciello@amd.com>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: "Rafael J . Wysocki" <rafael@kernel.org>,
	linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Len Brown <lenb@kernel.org>,
	linux-acpi@vger.kernel.org, stable@vger.kernel.org,
	Iain Lane <iain@orangesquash.org.uk>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Subject: Re: [PATCH v6 1/1] PCI: Avoid putting some root ports into D3 on some Ryzen chips
Date: Mon, 10 Jul 2023 17:42:56 -0500	[thread overview]
Message-ID: <007c0041-c0bb-09c3-15be-4e2bf82a5b03@amd.com> (raw)
In-Reply-To: <20230710203319.GA220162@bhelgaas>


On 7/10/2023 3:33 PM, Bjorn Helgaas wrote:
>
> It sounds like there's someplace the hardware designers specify how
> this should work?  Where is that?  "Modern Standby" doesn't mean
> anything to me, but maybe there's some spec that covers it?

https://learn.microsoft.com/en-us/windows-hardware/design/device-experiences/modern-standby

It quickly devolves into Microsoft specific stuff though and
I can't find anything interesting to our specific issue.
> Maybe this is the clue we need.  My eyes glaze over when reading that
> section, but if we can come up with a commit log that starts with a
> sentence from that section and connects the dots all the way to the
> platform_pci_power_manageable() implementation, that might be a good
> argument that 9d26d3a8f1b0 was a little too aggressive.
Yeah.
> I like the fact that v5 ([1] for anybody following along at home) is
> very generic:
>
>    @@ bool pci_bridge_d3_possible(struct pci_dev *bridge)
>    ...
>    +       if (pci_pcie_type(bridge) == PCI_EXP_TYPE_ROOT_PORT &&
>    +           !platform_pci_power_manageable(bridge))
>    +               return false;
>
> My objection was that we didn't have a clear connection to any specs,
> so even though the code is perfectly generic, the commit log mentioned
> specific cases (USB keyboard/mouse on xHCI device connected to USB-C
> on AMD USB4 router).
>
> But maybe we *could* make a convincing generic commit log.  I guess
> we'd also have to explain the PCI_EXP_TYPE_ROOT_PORT part of the
> patch.
OK, I'll take a stab at rewriting the v5 commit message to be more
generic as you suggested as a v7.

We might be able to drop the PCI_EXP_TYPE_ROOT_PORT part well but I
would be more worried about regressions from this.


      reply	other threads:[~2023-07-10 22:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-08 21:44 [PATCH v6 0/1] Fix suspend issues with AMD root ports Mario Limonciello
2023-07-08 21:44 ` [PATCH v6 1/1] PCI: Avoid putting some root ports into D3 on some Ryzen chips Mario Limonciello
2023-07-10 19:32   ` Bjorn Helgaas
2023-07-10 19:44     ` Limonciello, Mario
2023-07-10 20:33       ` Bjorn Helgaas
2023-07-10 22:42         ` Limonciello, Mario [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=007c0041-c0bb-09c3-15be-4e2bf82a5b03@amd.com \
    --to=mario.limonciello@amd.com \
    --cc=helgaas@kernel.org \
    --cc=iain@orangesquash.org.uk \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael@kernel.org \
    --cc=stable@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.