linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Maciej W. Rozycki" <macro@orcam.me.uk>
To: Ben Dooks <ben.dooks@codethink.co.uk>
Cc: Alexandre Ghiti <alex@ghiti.fr>,
	linux-pci@vger.kernel.org, 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>,
	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: Mon, 2 May 2022 12:46:11 +0100 (BST)	[thread overview]
Message-ID: <alpine.DEB.2.21.2205020049130.9383@angie.orcam.me.uk> (raw)
In-Reply-To: <3acd20b2-5882-7cc0-8a7b-7b406b768c1c@codethink.co.uk>

Hi Ben,

> >   Any idea what might be causing it?  I can't see it being explicitly set
> > or cleared anywhere, be it in U-Boot or Linux, so it must be done by the
> > device itself depending on something.  And the lack of this capability
> > seems to me like non-compliance for a multiple-lane, multiple-speed
> > device.
> 
> I'll see if we can reproduce this

 Have you been able to look into it?

  Maciej

  reply	other threads:[~2022-05-02 11:46 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
2022-04-14  0:10       ` Maciej W. Rozycki
2022-04-14  7:11         ` Ben Dooks
2022-05-02 11:46           ` Maciej W. Rozycki [this message]
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=alpine.DEB.2.21.2205020049130.9383@angie.orcam.me.uk \
    --to=macro@orcam.me.uk \
    --cc=alex@ghiti.fr \
    --cc=ben.dooks@codethink.co.uk \
    --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=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;
as well as URLs for NNTP newsgroup(s).