From: Sam Protsenko <semen.protsenko@linaro.org>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Sriranjani P <sriranjani.p@samsung.com>,
Chanho Park <chanho61.park@samsung.com>
Subject: Re: [PATCH 3/4] dt-bindings: soc: samsung: exynos-sysreg: add dedicated SYSREG compatibles to Exynos5433
Date: Fri, 25 Nov 2022 08:22:19 -0600 [thread overview]
Message-ID: <CAPLW+4kwFCLaiowajdCnA09eT4emOB-3d-6cbA=ZYyRLwYuCxw@mail.gmail.com> (raw)
In-Reply-To: <20221125112201.240178-3-krzysztof.kozlowski@linaro.org>
On Fri, 25 Nov 2022 at 05:22, Krzysztof Kozlowski
<krzysztof.kozlowski@linaro.org> wrote:
>
> Exynos5433 has several different SYSREGs, so use dedicated compatibles
> for them.
>
> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>
> ---
>
> Cc: Sriranjani P <sriranjani.p@samsung.com>
> Cc: Chanho Park <chanho61.park@samsung.com>
> Cc: Sam Protsenko <semen.protsenko@linaro.org>
> ---
Hi Krzysztof,
Just curious: what is the rationale for adding those more specific
sysregs? AFAIR, e.g. in Exynos850, different SysReg instances have
pretty much the same register layout.
Other than that:
Reviewed-by: Sam Protsenko <semen.protsenko@linaro.org>
> .../bindings/soc/samsung/samsung,exynos-sysreg.yaml | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
> index 68064a5e339c..42357466005e 100644
> --- a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
> +++ b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
> @@ -17,10 +17,21 @@ properties:
> - samsung,exynos3-sysreg
> - samsung,exynos4-sysreg
> - samsung,exynos5-sysreg
> - - samsung,exynos5433-sysreg
> - samsung,exynos850-sysreg
> - samsung,exynosautov9-sysreg
> - const: syscon
> + - items:
> + - enum:
> + - samsung,exynos5433-cam0-sysreg
> + - samsung,exynos5433-cam1-sysreg
> + - samsung,exynos5433-disp-sysreg
> + - samsung,exynos5433-fsys-sysreg
> + - const: samsung,exynos5433-sysreg
> + - const: syscon
> + - items:
> + - const: samsung,exynos5433-sysreg
> + - const: syscon
> + deprecated: true
>
> reg:
> maxItems: 1
> --
> 2.34.1
>
next prev parent reply other threads:[~2022-11-25 14:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20221125112237epcas5p42180c4d081cce89e14ac0975a94cdbc4@epcas5p4.samsung.com>
2022-11-25 11:21 ` [PATCH 1/4] arm64: dts: exynos: add dedicated SYSREG compatibles to Exynos5433 Krzysztof Kozlowski
2022-11-25 11:21 ` [PATCH 2/4] dt-bindings: soc: samsung: exynos-sysreg: split from syscon Krzysztof Kozlowski
2022-11-25 14:05 ` Lee Jones
2022-11-25 14:15 ` Sam Protsenko
2022-11-25 14:32 ` Sriranjani P
2022-11-26 13:07 ` Krzysztof Kozlowski
2022-11-25 16:56 ` Alim Akhtar
2022-11-25 11:22 ` [PATCH 3/4] dt-bindings: soc: samsung: exynos-sysreg: add dedicated SYSREG compatibles to Exynos5433 Krzysztof Kozlowski
2022-11-25 14:22 ` Sam Protsenko [this message]
2022-11-25 14:47 ` Krzysztof Kozlowski
2022-11-25 14:57 ` Sam Protsenko
2022-11-25 15:01 ` Krzysztof Kozlowski
2022-11-25 16:40 ` Alim Akhtar
2022-11-25 14:33 ` Sriranjani P
2022-11-25 17:06 ` Alim Akhtar
2022-11-26 13:08 ` Krzysztof Kozlowski
2022-11-25 11:22 ` [PATCH 4/4] dt-bindings: soc: samsung: exynos-sysreg: add clocks for Exynos850 Krzysztof Kozlowski
2022-11-25 14:33 ` Sriranjani P
2022-11-25 14:38 ` Sam Protsenko
2022-11-25 14:49 ` Krzysztof Kozlowski
2022-11-25 15:01 ` Sam Protsenko
2022-11-25 14:22 ` [PATCH 1/4] arm64: dts: exynos: add dedicated SYSREG compatibles to Exynos5433 Sam Protsenko
2022-11-25 14:29 ` Sriranjani P
2022-11-25 16:51 ` Alim Akhtar
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='CAPLW+4kwFCLaiowajdCnA09eT4emOB-3d-6cbA=ZYyRLwYuCxw@mail.gmail.com' \
--to=semen.protsenko@linaro.org \
--cc=alim.akhtar@samsung.com \
--cc=chanho61.park@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=lee@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=sriranjani.p@samsung.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).