Linux Power Management development
 help / color / mirror / Atom feed
From: Kenneth Crudup <kenny@panix.com>
To: Russell Haley <yumpusamongus@gmail.com>,
	Bjorn Helgaas <helgaas@kernel.org>
Cc: rafael@kernel.org, linux-pm@vger.kernel.org,
	Kai-Heng Feng <kai.heng.feng@canonical.com>,
	Vidya Sagar <vidyas@nvidia.com>,
	Bjorn Helgaas <bhelgaas@google.com>,
	Andrea Righi <andrea.righi@canonical.com>,
	You-Sheng Yang <vicamo.yang@canonical.com>,
	linux-pci@vger.kernel.org,
	Sergey Dolgov <sergey.v.dolgov@gmail.com>,
	Nirmal Patel <nirmal.patel@linux.intel.com>,
	Jonathan Derrick <jonathan.derrick@linux.dev>,
	Jian-Hong Pan <jhp@endlessos.org>,
	"David E. Box" <david.e.box@linux.intel.com>
Subject: Re: Raphael, I'd like your help upstreaming this VMD power-saving patch, please
Date: Fri, 23 May 2025 12:21:35 -0700	[thread overview]
Message-ID: <b52a2045-0b26-4287-80a4-e1b571d76a26@panix.com> (raw)
In-Reply-To: <7aedd720-c29a-4225-a79a-d44a3a9ca129@gmail.com>


Raphael, any input?

Thanks,

-Kenny

On 5/14/25 18:23, Russell Haley wrote:
> 
> 
> On 5/12/25 4:09 PM, Bjorn Helgaas wrote:
> 
>>>   static void pcie_aspm_cap_init(struct pcie_link_state *link, int blacklist)
>>>   {
>>>   	struct pci_dev *child = link->downstream, *parent = link->pdev;
>>> @@ -866,7 +891,8 @@ static void pcie_aspm_cap_init(struct pcie_link_state *link, int blacklist)
>>>   	}
>>>   
>>>   	/* Save default state */
>>> -	link->aspm_default = link->aspm_enabled;
>>> +	link->aspm_default = pci_fixup_vmd_bridge_enable_aspm(parent) ?
>>> +		PCIE_LINK_STATE_ASPM_ALL : link->aspm_enabled;
>>
>> PCIE_LINK_STATE_ASPM_ALL includes PCIE_LINK_STATE_L1_2, so I think
>> this potentially enables L1.2.  The L1.2 configuration depends on
>> T_POWER_ON and Common_Mode_Restore_Time, which depend on electrical
>> design and are not discoverable by the kernel.  See PCIe r6.0, sec
>> 5.5.4:
>>
>>    The TPOWER_ON and Common_Mode_Restore_Time fields must be programmed
>>    to the appropriate values based on the components and AC coupling
>>    capacitors used in the connection linking the two components. The
>>    determination of these values is design implementation specific.
> 
> Does that apply to VMD?  As far as I know it's not an actual physical
> PCIe device.
> 
> - Russell
> 

-- 
Kenneth R. Crudup / Sr. SW Engineer, Scott County Consulting, Orange 
County CA


  reply	other threads:[~2025-05-23 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-11 20:10 Raphael, I'd like your help upstreaming this VMD power-saving patch, please Kenneth R. Crudup
2025-05-12 21:09 ` Bjorn Helgaas
2025-05-12 22:41   ` Kenneth Crudup
2025-05-15  1:23   ` Russell Haley
2025-05-23 19:21     ` Kenneth Crudup [this message]
2025-05-23 19:44       ` Rafael J. Wysocki
2025-05-23 20:49         ` Kenneth Crudup

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=b52a2045-0b26-4287-80a4-e1b571d76a26@panix.com \
    --to=kenny@panix.com \
    --cc=andrea.righi@canonical.com \
    --cc=bhelgaas@google.com \
    --cc=david.e.box@linux.intel.com \
    --cc=helgaas@kernel.org \
    --cc=jhp@endlessos.org \
    --cc=jonathan.derrick@linux.dev \
    --cc=kai.heng.feng@canonical.com \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=nirmal.patel@linux.intel.com \
    --cc=rafael@kernel.org \
    --cc=sergey.v.dolgov@gmail.com \
    --cc=vicamo.yang@canonical.com \
    --cc=vidyas@nvidia.com \
    --cc=yumpusamongus@gmail.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