From: Krzysztof Kozlowski <krzk@kernel.org>
To: Kaustabh Chakraborty <kauschluss@disroot.org>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Alim Akhtar <alim.akhtar@samsung.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/5] dt-bindings: samsung: exynos-sysreg: add exynos7870 sysregs
Date: Wed, 18 Jun 2025 17:40:15 +0200 [thread overview]
Message-ID: <00e28a4a-78d6-4452-b28f-29d2e201f6d9@kernel.org> (raw)
In-Reply-To: <cd0f942a3752053e7569040f9e508b2d@disroot.org>
On 18/06/2025 16:49, Kaustabh Chakraborty wrote:
> On 2025-06-18 14:37, Krzysztof Kozlowski wrote:
>> On 18/06/2025 16:32, Kaustabh Chakraborty wrote:
>>> On 2025-06-18 09:46, Krzysztof Kozlowski wrote:
>>>> On 12/06/2025 17:23, Kaustabh Chakraborty wrote:
>>>>> Add sysreg compatible strings for the Exynos7870 SoC. Two sysregs
>>>>> are
>>>>> added, used for the SoC MIPI PHY's CSIS and DSIM blocks.
>>>>>
>>>>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
>>>>> ---
>>>>> .../devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
>>>>> | 6 ++++++
>>>>> 1 file changed, 6 insertions(+)
>>>>>
>>>>> diff --git
>>>>> a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
>>>>> b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
>>>>> index
>>>>> d27ed6c9d61ea9db77229eca60b6b9a0abc5d305..174bdb8ee932ff965de6fc17aef004a3cedffeb3
>>>>> 100644
>>>>> ---
>>>>> a/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
>>>>> +++
>>>>> b/Documentation/devicetree/bindings/soc/samsung/samsung,exynos-sysreg.yaml
>>>>> @@ -52,6 +52,12 @@ properties:
>>>>> - samsung,exynosautov9-sysreg
>>>>> - const: syscon
>>>>> deprecated: true
>>>>> + - items:
>>>>> + - enum:
>>>>> + - samsung,exynos7870-cam-sysreg
>>>>> + - samsung,exynos7870-disp-sysreg
>>>>> + - const: samsung,exynos7870-sysreg
>>>>
>>>>
>>>> Drop. These are not really compatible or your commit msg is
>>>> incomplete.
>>>> Don't use deprecated syntax and backwards compatible solutions for
>>>> new
>>>> hardware.
>>>
>>> Are you sure? The deprecated one is actually the item above. From what
>>> I
>>
>> Yes. Think why were they added.
>>
>>> understand, those are generic sysregs and don't mention their
>>> functions.
>>
>> And what is a generic sysreg?
>
> What I meant is, usually compatibles go like this (in order):
No, they don't. So you checked why they were added?
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-06-18 15:40 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-12 15:23 [PATCH 0/5] Support for Exynos7870's display stack (DECON, MIPIPHY, DSIM, etc.) Kaustabh Chakraborty
2025-06-12 15:23 ` [PATCH 1/5] dt-bindings: samsung: exynos-sysreg: add exynos7870 sysregs Kaustabh Chakraborty
2025-06-18 9:46 ` Krzysztof Kozlowski
2025-06-18 14:32 ` Kaustabh Chakraborty
2025-06-18 14:37 ` Krzysztof Kozlowski
2025-06-18 14:49 ` Kaustabh Chakraborty
2025-06-18 15:40 ` Krzysztof Kozlowski [this message]
2025-06-18 16:07 ` Kaustabh Chakraborty
2025-06-12 15:23 ` [PATCH 2/5] arch: arm64: dts: exynos7870: add DSI support Kaustabh Chakraborty
2025-06-18 10:04 ` Krzysztof Kozlowski
2025-06-12 15:23 ` [PATCH 3/5] arch: arm64: dts: exynos7870-on7xelte: enable display panel support Kaustabh Chakraborty
2025-06-18 9:57 ` Krzysztof Kozlowski
2025-06-18 14:39 ` Kaustabh Chakraborty
2025-06-12 15:23 ` [PATCH 4/5] arch: arm64: dts: exynos7870-a2corelte: " Kaustabh Chakraborty
2025-06-12 15:23 ` [PATCH 5/5] arch: arm64: dts: exynos7870-j6lte: " Kaustabh Chakraborty
2025-06-12 20:12 ` [PATCH 0/5] Support for Exynos7870's display stack (DECON, MIPIPHY, DSIM, etc.) Rob Herring (Arm)
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=00e28a4a-78d6-4452-b28f-29d2e201f6d9@kernel.org \
--to=krzk@kernel.org \
--cc=alim.akhtar@samsung.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kauschluss@disroot.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=robh@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
all inboxes | Powered by JetHome®