From: Ben Dooks <ben.dooks@codethink.co.uk>
To: Alexandre Ghiti <alex@ghiti.fr>, linux-pci@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-riscv@lists.infradead.org,
Bjorn Helgaas <bhelgaas@google.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Greentime Hu <greentime.hu@sifive.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
David Abdurachmanov <david.abdurachmanov@sifive.com>,
Neill Whillans <neill.whillans@codethink.co.uk>
Subject: Re: [V3] PCI: fu740: Drop to 2.5GT/s to fix initial device probing on some boards
Date: Wed, 23 Mar 2022 10:40:11 +0000 [thread overview]
Message-ID: <bded4b1e-3404-6bcd-3289-dc8d5b4d713a@codethink.co.uk> (raw)
In-Reply-To: <85e864fd-762e-0780-f829-bfbb178ab24e@ghiti.fr>
On 23/03/2022 10:36, Alexandre Ghiti wrote:
> On 3/21/22 14:49, Alexandre Ghiti wrote:
>> Hi Ben,
>>
>> On 3/18/22 16:24, Ben Dooks wrote:
>>> The fu740 PCIe core does not probe any devices on the SiFive Unmatched
>>> board without this fix (or having U-Boot explicitly start the PCIe via
>>> either boot-script or user command). The fix is to start the link at
>>> 2.5GT/s speeds and once the link is up then change the maximum speed
>>> back
>>> to the default.
>>>
>>> The U-Boot driver claims to set the link-speed to 2.5GT/s to get the
>>> probe
>>> to work (and U-Boot does print link up at 2.5GT/s) in the following
>>> code:
>>> https://source.denx.de/u-boot/u-boot/-/blob/master/drivers/pci/pcie_dw_sifive.c?id=v2022.01#L271
>>>
>>>
>>> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
[snip]
>>> static int fu740_pcie_host_init(struct pcie_port *pp)
>>
>> +cc Maciej and David as there is this other fix that seems to do the
>> same but differently, it's been under review for some time now:
>> https://lore.kernel.org/all/20220302000043.GA662523@bhelgaas/t/
>>
I did have a quick look, but I think because we don't get any PCIe
probing at-all we don't even have a device to attach to.
>> I fell onto this issue recently, I'll give your patch and the above a
>> try soon.
>
>
> FWIW, I have tested this and it solved my issue with nvme not being
> probed, so:
>
> Tested-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
Ok, great. Our test rig seems to be still working with this.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
https://www.codethink.co.uk/privacy.html
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next prev parent reply other threads:[~2022-03-23 10:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-18 15:24 [V3] PCI: fu740: Drop to 2.5GT/s to fix initial device probing on some boards Ben Dooks
2022-03-18 23:03 ` Palmer Dabbelt
2022-03-19 12:40 ` Ben Dooks
2022-03-21 13:49 ` Alexandre Ghiti
2022-03-23 10:36 ` Alexandre Ghiti
2022-03-23 10:40 ` Ben Dooks [this message]
2022-04-14 0:10 ` Maciej W. Rozycki
2022-04-14 7:11 ` Ben Dooks
2022-05-02 11:46 ` Maciej W. Rozycki
2022-05-29 15:56 ` Ben Dooks
2022-03-21 20:29 ` Bjorn Helgaas
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=bded4b1e-3404-6bcd-3289-dc8d5b4d713a@codethink.co.uk \
--to=ben.dooks@codethink.co.uk \
--cc=alex@ghiti.fr \
--cc=bhelgaas@google.com \
--cc=david.abdurachmanov@sifive.com \
--cc=greentime.hu@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=macro@orcam.me.uk \
--cc=neill.whillans@codethink.co.uk \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox