linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
To: linux-pci@vger.kernel.org
Cc: linux-rockchip@lists.infradead.org,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, kw@linux.com, robh@kernel.org,
	bhelgaas@google.com, heiko@sntech.de, lgirdwood@gmail.com,
	broonie@kernel.org, skhan@linuxfoundation.org,
	shawn.lin@rock-chips.com, lpieralisi@kernel.org,
	linux-kernel-mentees@lists.linuxfoundation.org,
	Vincenzo Palazzo <vincenzopalazzodev@gmail.com>
Subject: [PATCH v1 0/1] Add configurable sleep for pcie-rockchip-host
Date: Tue,  9 May 2023 17:39:02 +0200	[thread overview]
Message-ID: <20230509153902.515106-1-vincenzopalazzodev@gmail.com> (raw)

I am submitting a patch to add a configurable sleep for the
Rockchip PCIe driver in the hope of resolving a persistent
issue with old ARM platforms.

It has been observed that the driver requires an extra
sleep before probing the device, particularly on some older ARM
devices like Pine64 RockPro64. While an original patch was deployed
in Manjaro ARM, the issue still persists with the upstream kernel.

This patch introduces a module parameter "bus_scan_delay" which allows users
to configure the delay before probing the device. I have tested this patch
on several platforms and it has proven to be effective.

I hope that by starting this discussion, we can collaborate and
find a more robust upstream solution for this issue.

P.S: I sent again this because I forget to add some people to the list
of cc.

Cheers!

Vincent.
-------
Vincenzo Palazzo (1):
  drivers: pci: introduce configurable delay for Rockchip PCIe bus scan

 .../admin-guide/kernel-parameters.txt         |  8 +++++
 .../boot/dts/rockchip/rk3399-rockpro64.dtsi   |  3 +-
 drivers/pci/controller/pcie-rockchip-host.c   | 29 +++++++++++++++++++
 drivers/pci/controller/pcie-rockchip.c        |  5 ++++
 drivers/pci/controller/pcie-rockchip.h        |  9 ++++++
 5 files changed, 53 insertions(+), 1 deletion(-)

--
2.40.1


                 reply	other threads:[~2023-05-09 15:39 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20230509153902.515106-1-vincenzopalazzodev@gmail.com \
    --to=vincenzopalazzodev@gmail.com \
    --cc=bhelgaas@google.com \
    --cc=broonie@kernel.org \
    --cc=heiko@sntech.de \
    --cc=kw@linux.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel-mentees@lists.linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=lpieralisi@kernel.org \
    --cc=robh@kernel.org \
    --cc=shawn.lin@rock-chips.com \
    --cc=skhan@linuxfoundation.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).