From: Conor Dooley <conor@kernel.org>
To: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Cc: Philipp Zabel <p.zabel@pengutronix.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>,
Olivia Mackall <olivia@selenic.com>,
Herbert Xu <herbert@gondor.apana.org.au>,
Daniel Golle <daniel@makrotopia.org>,
Aurelien Jarno <aurelien@aurel32.net>,
Sebastian Reichel <sebastian.reichel@collabora.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-crypto@vger.kernel.org,
XiaoDong Huang <derrick.huang@rock-chips.com>
Subject: Re: [PATCH 1/7] dt-bindings: reset: Add SCMI reset IDs for RK3588
Date: Thu, 30 Jan 2025 18:46:12 +0000 [thread overview]
Message-ID: <20250130-payment-carpentry-bf3898625c96@spud> (raw)
In-Reply-To: <20250130-rk3588-trng-submission-v1-1-97ff76568e49@collabora.com>
[-- Attachment #1: Type: text/plain, Size: 588 bytes --]
On Thu, Jan 30, 2025 at 05:31:15PM +0100, Nicolas Frattaroli wrote:
> When TF-A is used to assert/deassert the resets through SCMI, the
> IDs communicated to it are different than the ones mainline Linux uses.
>
> Import the list of SCMI reset IDs from mainline TF-A so that devicetrees
> can use these IDs more easily.
>
> Co-developed-by: XiaoDong Huang <derrick.huang@rock-chips.com>
> Signed-off-by: XiaoDong Huang <derrick.huang@rock-chips.com>
> Signed-off-by: Nicolas Frattaroli <nicolas.frattaroli@collabora.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-30 18:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-30 16:31 [PATCH 0/7] RK3588 Hardware Random Number Generator Driver Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 1/7] dt-bindings: reset: Add SCMI reset IDs for RK3588 Nicolas Frattaroli
2025-01-30 18:46 ` Conor Dooley [this message]
2025-01-30 16:31 ` [PATCH 2/7] dt-bindings: rng: add binding for Rockchip RK3588 RNG Nicolas Frattaroli
2025-01-30 18:42 ` Conor Dooley
2025-01-31 8:30 ` Krzysztof Kozlowski
2025-01-31 9:43 ` Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 3/7] hwrng: rockchip: store dev pointer in driver struct Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 4/7] hwrng: rockchip: eliminate some unnecessary dereferences Nicolas Frattaroli
2025-01-30 16:31 ` [PATCH 5/7] hwrng: rockchip: add support for rk3588's standalone TRNG Nicolas Frattaroli
2025-01-31 8:34 ` Krzysztof Kozlowski
2025-01-30 16:31 ` [PATCH 6/7] arm64: dts: rockchip: Add rng node to RK3588 Nicolas Frattaroli
2025-01-31 10:16 ` Krzysztof Kozlowski
2025-01-30 16:31 ` [PATCH 7/7] mailmap: add entry for Nicolas Frattaroli Nicolas Frattaroli
2025-01-31 8:36 ` Krzysztof Kozlowski
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=20250130-payment-carpentry-bf3898625c96@spud \
--to=conor@kernel.org \
--cc=aurelien@aurel32.net \
--cc=conor+dt@kernel.org \
--cc=daniel@makrotopia.org \
--cc=derrick.huang@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=herbert@gondor.apana.org.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=nicolas.frattaroli@collabora.com \
--cc=olivia@selenic.com \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.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;
as well as URLs for NNTP newsgroup(s).