From: "Jernej Škrabec" <jernej.skrabec@gmail.com>
To: Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Chen-Yu Tsai <wens@csie.org>,
Samuel Holland <samuel@sholland.org>,
Maxime Ripard <mripard@kernel.org>,
Martin Botka <martin.botka@somainline.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Alan Ma <tech@biqu3d.com>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Martin Botka <martin.botka@somainline.org>
Subject: Re: [PATCH v3 0/2] Enable Security ID for H616
Date: Sun, 24 Sep 2023 21:57:42 +0200 [thread overview]
Message-ID: <1942306.PYKUYFuaPT@jernej-laptop> (raw)
In-Reply-To: <20230912-sid-h616-v3-0-ee18e1c5bbb5@somainline.org>
Dne torek, 12. september 2023 ob 14:25:11 CEST je Martin Botka napisal(a):
> Hello,
>
> This patch series enables Security ID (SID) support for AllWinner H616.
>
> SID support is an requirement for few things:
> - Thermal sensors
> - CPU Binning ID (cpufreq will use this)
> - EPhy
>
> This patch series doesn't add support for the consumers.
> Those will come in the future via their own series.
Applied, thanks!
Best regards,
Jernej
>
> Cheers,
> Martin
>
> Signed-off-by: Martin Botka <martin.botka@somainline.org>
> ---
> Changes in v3:
> - bindings: Make H616 compatible fallback for a64 using items and enum
> - Link to v2: https://lore.kernel.org/r/20230814-sid-h616-v2-0-0267749b4471@somainline.org
>
> Changes in v2:
> - Drop driver changes
> - Use fallback compatible in DT
> - Link to v1: https://lore.kernel.org/r/20230811-sid-h616-v1-0-d1dfc9f47b19@somainline.org
>
> ---
> Martin Botka (2):
> dt-bindings: nvmem: SID: Add binding for H616 SID controller
> arm64: dts: allwinner: h616: Add SID controller node
>
> .../devicetree/bindings/nvmem/allwinner,sun4i-a10-sid.yaml | 4 +++-
> arch/arm64/boot/dts/allwinner/sun50i-h616.dtsi | 7 +++++++
> 2 files changed, 10 insertions(+), 1 deletion(-)
> ---
> base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d
> change-id: 20230811-sid-h616-37b773e59571
>
> Best regards,
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-09-24 19:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 12:25 [PATCH v3 0/2] Enable Security ID for H616 Martin Botka
2023-09-12 12:25 ` [PATCH v3 1/2] dt-bindings: nvmem: SID: Add binding for H616 SID controller Martin Botka
2023-09-12 15:54 ` Jernej Škrabec
2023-09-12 16:34 ` Conor Dooley
2023-09-12 12:25 ` [PATCH v3 2/2] arm64: dts: allwinner: h616: Add SID controller node Martin Botka
2023-09-12 15:54 ` Jernej Škrabec
2023-09-24 19:57 ` Jernej Škrabec [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=1942306.PYKUYFuaPT@jernej-laptop \
--to=jernej.skrabec@gmail.com \
--cc=andre.przywara@arm.com \
--cc=angelogioacchino.delregno@somainline.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sunxi@lists.linux.dev \
--cc=martin.botka@somainline.org \
--cc=mripard@kernel.org \
--cc=robh+dt@kernel.org \
--cc=samuel@sholland.org \
--cc=srinivas.kandagatla@linaro.org \
--cc=tech@biqu3d.com \
--cc=wens@csie.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