From: Manivannan Sadhasivam <mani@kernel.org>
To: linux-pci@vger.kernel.org,
Marek Vasut <marek.vasut+renesas@mailbox.org>
Cc: "Krzysztof Wilczyński" <kwilczynski@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Geert Uytterhoeven" <geert+renesas@glider.be>,
"Lorenzo Pieralisi" <lpieralisi@kernel.org>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Rob Herring" <robh@kernel.org>,
"Yoshihiro Shimoda" <yoshihiro.shimoda.uh@renesas.com>,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH] PCI: rcar-gen4: Assure reset occurs before DBI access
Date: Thu, 25 Sep 2025 22:06:14 +0530 [thread overview]
Message-ID: <175881817482.390261.3355390363280103413.b4-ty@kernel.org> (raw)
In-Reply-To: <20250924005610.96484-1-marek.vasut+renesas@mailbox.org>
On Wed, 24 Sep 2025 02:55:45 +0200, Marek Vasut wrote:
> Assure the reset is latched and the core is ready for DBI access.
> On R-Car V4H, the PCIe reset is asynchronized and does not take
> effect immediately, but needs a short time to complete. In case
> DBI access happens in that short time, that access generates an
> SError. Make sure that condition can never happen, read back the
> state of the reset which should turn the asynchronized reset into
> synchronized one, and wait a little over 1ms to add additional
> safety margin.
>
> [...]
Applied, thanks!
[1/1] PCI: rcar-gen4: Assure reset occurs before DBI access
commit: 1d45d0c80b9e8fd8167e0621146a32eecebd430f
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
prev parent reply other threads:[~2025-09-25 16:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-24 0:55 [PATCH] PCI: rcar-gen4: Assure reset occurs before DBI access Marek Vasut
2025-09-25 13:41 ` Geert Uytterhoeven
2025-09-25 16:39 ` Manivannan Sadhasivam
2025-09-25 16:36 ` Manivannan Sadhasivam [this message]
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=175881817482.390261.3355390363280103413.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=bhelgaas@google.com \
--cc=geert+renesas@glider.be \
--cc=kwilczynski@kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=lpieralisi@kernel.org \
--cc=magnus.damm@gmail.com \
--cc=marek.vasut+renesas@mailbox.org \
--cc=robh@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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