Linux PCI subsystem development
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@mailbox.org>
To: "Manivannan Sadhasivam" <mani@kernel.org>,
	"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
	"Krzysztof Wilczyński" <kwilczynski@kernel.org>
Cc: linux-pci@vger.kernel.org,
	Geert Uytterhoeven <geert@linux-m68k.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 v2] PCI: rcar-gen4: Add missing 1ms delay after PWR reset assertion
Date: Fri, 19 Sep 2025 15:30:14 +0200	[thread overview]
Message-ID: <475cfd27-54d2-44b3-9b26-5de4b75033ff@mailbox.org> (raw)
In-Reply-To: <3h3tkv6jmkwqqsb6bdotdx4bcnnzqqqzgl5digryxo5bc4qpm6@np76zatxj6ff>

On 9/19/25 2:33 PM, Manivannan Sadhasivam wrote:

Hello Manivannan,

>>> Because it is the controller driver which can determine whether or not the
>>> controller is in HSC domain based on its compatible string, add the missing
>>> delay into the controller driver.
>>>
>>> This 1ms delay is documented on R-Car V4H and V4M, it is currently unclear
>>> whether S4 is affected as well. This patch does apply the extra delay on
>>> R-Car S4 as well.
>>
> 
> What are the implications of not having the delay? Just asking to determine if
> this patch is a stable candidate or not.

Observable, thus far, none. However, the current behavior does not 
follow the reference manual operations chart, so I think this should be 
in stable, else the hardware is operated out of specification.

>> [...]
>>> -	if (!reset_control_status(dw->core_rsts[DW_PCIE_PWR_RST].rstc))
>>> +	if (!reset_control_status(dw->core_rsts[DW_PCIE_PWR_RST].rstc)) {
>>>   		reset_control_assert(dw->core_rsts[DW_PCIE_PWR_RST].rstc);
>>> +		fsleep(1000);
>>> +	}
>>
>> Would it be a prudent thing to do here to add a comment over the fsleep()
>> or over the if-statement to document briefly (and for posterity) why we
>> sleep here?
>>
> 
> I can add the quote to the reference manual while applying.
I'll send a V3 with a comment shortly.

      reply	other threads:[~2025-09-19 13:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-18 23:12 [PATCH v2] PCI: rcar-gen4: Add missing 1ms delay after PWR reset assertion Marek Vasut
2025-09-19 10:00 ` Krzysztof Wilczyński
2025-09-19 12:33   ` Manivannan Sadhasivam
2025-09-19 13:30     ` Marek Vasut [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=475cfd27-54d2-44b3-9b26-5de4b75033ff@mailbox.org \
    --to=marek.vasut@mailbox.org \
    --cc=bhelgaas@google.com \
    --cc=geert+renesas@glider.be \
    --cc=geert@linux-m68k.org \
    --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=mani@kernel.org \
    --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