On Tue, Jun 22, 2021 at 02:16:49PM +0200, Pali Rohár wrote: > On Tuesday 22 June 2021 12:56:04 Lorenzo Pieralisi wrote: > > [Adding Linus for GPIO discussion, thread: > > https://lore.kernel.org/linux-pci/20210531090540.2663171-1-luca@xxxxxxxxxxxxxxxx] > > > > On Tue, Jun 22, 2021 at 01:06:27PM +0200, Pali Rohár wrote: > > > Hello! > > > > > > On Tuesday 22 June 2021 12:57:22 Luca Ceresoli wrote: > > > > Nothing happened after a few weeks... I understand that knowing the > > > > correct reset timings is relevant, but unfortunately I cannot help much > > > > in finding out the correct values. > > > > > > > > However I'm wondering what should happen to this patch. It *does* fix a > > > > real bug, but potentially with an incorrect or non-optimal usleep range. > > > > Do we really want to ignore a bugfix because we are not sure about how > > > > long this delay should be? > > > > > > As there is no better solution right now, I'm fine with your patch. But > > > patch needs to be approved by Lorenzo, so please wait for his final > > > answer. > > > > I am not a GPIO expert and I have a feeling this is platform specific > > beyond what the PCI specification can actually define architecturally. > > In my opinion timeout is not platform specific as I wrote in email: > https://lore.kernel.org/linux-pci/20210310110535.zh4pnn4vpmvzwl5q@pali/ > > My experiments already proved that some PCIe cards needs to be in reset > state for some minimal time otherwise they cannot be enumerated. And it > does not matter to which platform you connect those (endpoint) cards. > > I do not think that timeout itself is platform specific. GPIO controls > PERST# pin and therefore specified sleep value directly drives how long > is card on the other end of PCIe slot in Warm Reset state. PCIe CEM spec > directly says that PERST# signal controls PCIe Warm Reset. Point taken but regardless this deviates from the PCI electromechanical specifications (ie T-PERST-CLK), does not it ? I misused "platform" to define something that apparently is not contemplated by the PCI specifications (and I would like to understand why). I guess on ACPI systems (ie where the PERST# handling is implemented in FW) this is handled in BIOS/UEFI - need to peruse the code to check how PERST# is handled and whether the delay is per host controller driver. > > What is here platform specific thing is that PERST# signal is controlled > by GPIO. But value of signal (high / low) and how long is in signal in > which state for me sounds like not an platform specific thing, but as > PCIe / CEM related. There are two different things to agree on this patch 1) how GPIO drives PERST# 2) the PERST# de-assertion delay. I appreciate they are related and that Luca had to handle them together but logically they are separated "issues", it'd be great if we manage to nail down how they should be handled before we merge this code. Lorenzo > > > There are two things I'd like to see: > > > > 1) If Linus can have a look at the GPIO bits in this thread that would > > definitely help clarify any pending controversy > > 2) Kishon to test on *existing* platforms and confirm there are no > > regressions triggered > > > > > I would suggest to add a comment for call "usleep_range(1000, 2000);" > > > that you have chosen some "random" values which worked fine on your > > > setup and that they fix mentioned bug. Comment just to mark this sleep > > > code that is suboptimal / not-so-correct and to prevent other people to > > > copy+paste this code into other (new) drivers... > > > > Yes a comment would help but as I say above I am afraid this is > > a platform specific set-up, ie that delay is somewhat tied to > > a platform, not sure there is anything we can do. > > > > If Linus and Kishon are happy with the approach we can merge this > > patch. > > > > Lorenzo
