All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dullfire <dullfire@yahoo.com>
To: Bartosz Golaszewski <bartosz.golaszewski@linaro.org>
Cc: "Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>,
	linux-pci@vger.kernel.org, "Bjorn Helgaas" <helgaas@kernel.org>
Subject: Re: [Bug 219513] New: PCIe drivers do not bind
Date: Tue, 19 Nov 2024 10:57:26 -0600	[thread overview]
Message-ID: <52410459-d15b-4e18-a978-0c069f9cd292@yahoo.com> (raw)
In-Reply-To: <CACMJSesxsADzGQyzi13QDGh-VwEO+mgyyGmSNEyyBiL6QRAWZw@mail.gmail.com>



On 11/19/24 08:16, Bartosz Golaszewski wrote:
> On Tue, 19 Nov 2024 at 15:04, Bjorn Helgaas <helgaas@kernel.org> wrote:
>>
>> On Tue, Nov 19, 2024 at 12:55:36PM +0000, bugzilla-daemon@kernel.org wrote:
>>> https://bugzilla.kernel.org/show_bug.cgi?id=219513
>>>
>>>           Hardware: Sparc64
>>>           Priority: P3
>>>           Reporter: dullfire@yahoo.com
>>>         Regression: No
>>>
>>> Created attachment 307241
>>>   --> https://bugzilla.kernel.org/attachment.cgi?id=307241&action=edit
>>> debug info (some shell commands to check the PCIe devices and drivers)
>>>
>>> In linux-next (next-20241118), since
>>> commit 03cfe0e05650 ("PCI/pwrctl: Ensure that the pwrctl drivers are probed
>>> before the PCI client drivers")
>>> PCIe drivers no longer bind (at least on the tested SPARCv9 system).
>>>
>>> It appears a "supplier" devlink is created, however it is are dormant. see
>>> attached "bug-info.txt"
>>
>> Thanks for the report.  It sounds like you bisected this to
>> 03cfe0e05650?  Can you attach a complete dmesg log to the bugzilla?
>>
>> This commit is queued for v6.13, and the merge window is now open, so
>> if it's a regression, we need to resolve it or drop it ASAP.
> 
> Dullfire: is the DTS for this platform publicly available? If not, can
> you at least post the PCI host controller and all its children nodes
> here?
> 
> Bart

Bart: I attached to the bug report a dts extracted from the system.

Just a FYI: SPARC systems (including linux) get their device tree from the
open firmware, which likely dynamically generates at least parts of it, so
there is not a discrete source for it.

Regards,
Jonathan Currier

  reply	other threads:[~2024-11-19 17:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-219513-41252@https.bugzilla.kernel.org/>
2024-11-19 14:04 ` [Bug 219513] New: PCIe drivers do not bind Bjorn Helgaas
2024-11-19 14:16   ` Bartosz Golaszewski
2024-11-19 16:57     ` Dullfire [this message]
2024-11-19 17:27       ` Manivannan Sadhasivam
2024-11-19 17:48         ` Dullfire
2024-11-19 17:17   ` Dullfire

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=52410459-d15b-4e18-a978-0c069f9cd292@yahoo.com \
    --to=dullfire@yahoo.com \
    --cc=bartosz.golaszewski@linaro.org \
    --cc=helgaas@kernel.org \
    --cc=kwilczynski@kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=manivannan.sadhasivam@linaro.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.