mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Claudiu Beznea <claudiu.beznea@kernel.org>
To: Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: lpieralisi@kernel.org, kwilczynski@kernel.org, mani@kernel.org,
	robh@kernel.org, bhelgaas@google.com, p.zabel@pengutronix.de,
	geert+renesas@glider.be, magnus.damm@gmail.com,
	claudiu.beznea@tuxon.dev, linux-pci@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	Claudiu Beznea <claudiu.beznea.uj@bp.renesas.com>
Subject: Re: [PATCH v7 00/14] PCI: rzg3s-host: Add PCIe hotplug support
Date: Wed, 11 Nov 2026 15:55:21 +0200	[thread overview]
Message-ID: <85acc16c-01e7-46a4-af68-3d6f24fe90c1@kernel.org> (raw)
In-Reply-To: <avOBDu8XaZ-kZIsF@ninjato>

Hi, Wolfram,

On 11/10/26 22:39, Wolfram Sang wrote:
> Hi Claudiu,
> 
> finally, I got around to it...

Thank you for checking this.

> 
>> I currently can't reproduce this on my side. Do you remember if you executed
>> the below command before your test:
>>
>> echo performance > /sys/module/pcie_aspm/parameters/policy
> 
> No, I did not and it makes a difference. With the command above, removal
> also works fine. But leaving it and letting the policy stay "default",
> removal doesn't work. I don't even see this line:
> 
> pcieport 0000:00:00.0: Recovering Root Port due to Link Down
> 
> Is this expected? I'd think "default" should work as well?

What I suspect happens in this particular case is that due to the PCIe link 
being in a power saving state (when ASPM policy is default), and since the RC 
don't have native hotplug support, the RC is unable to see something happened 
with the link and to trigger the link event IRQ. Any subsequent operation that
gets the link out of a power saving mode should  make the HW aware of something 
happened at the link level and trigger the link event IRQ as well.

E.g.: if you keep the ASPM policy to default and generate a link up/down event 
that will not be seen by Linux. A subsequent lspci will trigger it. Steps to 
check this:

1/ Make sure the link up
2/ echo default > /sys/module/pcie_aspm/parameters/policy
3/ trigger link down; at this point Linux should see nothing
4/ run lspci; at this point link IRQ will be generated and Linux will take the
    action to remove the PCIe devices

Thank you,
Claudiu

      reply	other threads:[~2026-11-11 13:55 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-19  6:50 Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 01/14] PCI: rzg3s-host: Follow hardware manual clock/reset initialization order Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 02/14] PCI: rzg3s-host: Fix runtime PM handling in the NOIRQ suspend/resume phase Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 03/14] PCI: rzg3s-host: Don't mix goto-based unwinding and cleanup helpers Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 04/14] PCI: rzg3s-host: Create the INTx IRQ domain before setting the chained handlers Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 05/14] PCI: rzg3s-host: Initialize the IRQ domains after the IRQs are masked Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 06/14] PCI: rzg3s-host: Drop read-modify-write approach for the R/W1C registers Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 07/14] PCI: rzg3s-host: Use cached MSI address in .irq_compose_msi_msg() Claudiu Beznea
2026-10-20  8:45   ` Lad, Prabhakar
2026-10-20  9:10     ` Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 08/14] PCI: rzg3s-host: Drop nop instructions Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 09/14] PCI: rzg3s-host: Move host configuration code together Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 10/14] PCI: rzg3s-host: Move suspend/resume code into dedicated functions Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 11/14] PCI: rzg3s-host: Move IRQ domain setup code Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 12/14] PCI: rzg3s-host: Add helper to wait for link up Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 13/14] PCI: rzg3s-host: Re-enumerate the bus on PCIe link-state changes Claudiu Beznea
2026-10-19  6:50 ` [PATCH v7 14/14] PCI: rzg3s-host: Add bridge::reset_root_port() Claudiu Beznea
2026-10-22 19:16 ` [PATCH v7 00/14] PCI: rzg3s-host: Add PCIe hotplug support Wolfram Sang
2026-11-02  7:36   ` Claudiu Beznea
2026-11-02  7:40     ` Wolfram Sang
2026-11-10 20:39     ` Wolfram Sang
2026-11-11 13:55       ` Claudiu Beznea [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=85acc16c-01e7-46a4-af68-3d6f24fe90c1@kernel.org \
    --to=claudiu.beznea@kernel.org \
    --cc=bhelgaas@google.com \
    --cc=claudiu.beznea.uj@bp.renesas.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=geert+renesas@glider.be \
    --cc=kwilczynski@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=mani@kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=wsa+renesas@sang-engineering.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

all inboxes | Powered by JetHome®