public inbox for linux-pci@vger.kernel.org
 help / color / mirror / Atom feed
From: Lukas Wunner <lukas@wunner.de>
To: Naveen Kumar P <naveenkumar.parna@gmail.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
	Bjorn Helgaas <helgaas@kernel.org>
Subject: Re: Assistance Needed: PCIe Device BAR Reset Issue
Date: Fri, 31 Jan 2025 13:09:51 +0100	[thread overview]
Message-ID: <Z5y9j0eOQTIrcD7E@wunner.de> (raw)
In-Reply-To: <CAMciSVUzFL+myQTTRD-OZRf+o9UUPDE87SzUxQ2cYdjrfd7iHQ@mail.gmail.com>

On Fri, Jan 31, 2025 at 03:37:26PM +0530, Naveen Kumar P wrote:
> PCIe Device: PLDA Device 5555
[...]
> Initially, the BAR value is 0xb0400000. However, after some time, reading
> from the PCIe device's BAR memory fails and returns 0xffff

If you're reading "all ones" from config space, it means the device is
inaccessible and the host bridge is returning this fabricated value after
a timeout.

>         Kernel modules: m1801_pci

That's not a driver in the upstream kernel.

Maybe that driver allows the device to runtime suspend to D3hot,
which in turn allows its upstream bridge to also runtime suspend
to D3hot.  Then the device would be inaccessible.

> Verified power management settings:
> 
> cat /sys/module/pcie_aspm/parameters/policy
> Output: [default] performance powersave powersupersave

/sys/bus/pci/devices/0000:01:00.0/power/runtime_status
would tell you whether the device is runtime suspended.

Thanks,

Lukas

  reply	other threads:[~2025-01-31 12:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-31 10:07 Assistance Needed: PCIe Device BAR Reset Issue Naveen Kumar P
2025-01-31 12:09 ` Lukas Wunner [this message]
2025-02-01  9:03 ` Naveen Kumar P

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=Z5y9j0eOQTIrcD7E@wunner.de \
    --to=lukas@wunner.de \
    --cc=helgaas@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=naveenkumar.parna@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