From: Brian Masney <bmasney@redhat.com>
To: Christian Marangi <ansuelsmth@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: en7523: add support for dedicated PCIe PERSTOUT reset
Date: Fri, 24 Jul 2026 15:06:08 -0400 [thread overview]
Message-ID: <amO3oF6B6aHVfL9K@redhat.com> (raw)
In-Reply-To: <20260723190133.22577-2-ansuelsmth@gmail.com>
On Thu, Jul 23, 2026 at 09:01:31PM +0200, Christian Marangi wrote:
> Add support for resetting the PCIe lines with the PERSTOUT reset. These
> special reset are controlled by the PCIC register and are specific to each
> of the 3 PCIe lines.
>
> Contrary to the dedicated reset register where 0 deassert and 1 assert the
> reset line for the related bit, for PCIe PERSTOUT reset in the PCIC
> register, the deassert and assert value is swapped, with 1 for deassert and
> 0 for assert. (HW have these bit set as 1 by default after a cold boot)
> This is internally handled in the reset function.
>
> PCI enable/disable are updated to drop PERSTOUT bits in favor dedicated
> reset handling.
>
> Signed-off-by: Christian Marangi <ansuelsmth@gmail.com>
Reviewed-by: Brian Masney <bmasney@redhat.com>
prev parent reply other threads:[~2026-07-24 19:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-23 19:01 [PATCH 1/2] dt-bindings: clock: airoha: Add additional reset for PCIe PERSTOUT Christian Marangi
2026-07-23 19:01 ` [PATCH 2/2] clk: en7523: add support for dedicated PCIe PERSTOUT reset Christian Marangi
2026-07-24 19:06 ` Brian Masney [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=amO3oF6B6aHVfL9K@redhat.com \
--to=bmasney@redhat.com \
--cc=ansuelsmth@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sboyd@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