From: Krzysztof Kozlowski <krzk@kernel.org>
To: Nick Xie <xieqinick@gmail.com>
Cc: neil.armstrong@linaro.org, khilman@baylibre.com,
jbrunet@baylibre.com, martin.blumenstingl@googlemail.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-amlogic@lists.infradead.org, xianwei.zhao@amlogic.com,
christianshewitt@gmail.com, krzk+dt@kernel.org, robh@kernel.org,
conor+dt@kernel.org, nick@khadas.com
Subject: Re: [PATCH v2 1/2] dt-bindings: arm: amlogic: add Khadas VIM1S binding
Date: Wed, 14 Jan 2026 11:33:26 +0100 [thread overview]
Message-ID: <39bb1820-6e4d-4f50-87e0-93844d779f6c@kernel.org> (raw)
In-Reply-To: <CAP4nuTXeC1-6ktwLpDt_1ZRHxPSiNAoDKTxLzqEYJUfcnVogcQ@mail.gmail.com>
On 14/01/2026 11:07, Nick Xie wrote:
> Krzysztof Kozlowski <krzk@kernel.org> 于2026年1月14日周三 16:51写道:
>>
>> On Wed, Jan 14, 2026 at 02:25:48PM +0800, Nick Xie wrote:
>>> Add devicetree binding for Khadas VIM1S board based on
>>> Amlogic S4 S905Y4 SoC.
>>>
>>> Signed-off-by: Nick Xie <nick@khadas.com>
>>
>> You still have the same From/SoB mismatch.
>
> OK, I will fix it in next version.
>
>>
>>> ---
>>> Documentation/devicetree/bindings/arm/amlogic.yaml | 6 ++++++
>>> 1 file changed, 6 insertions(+)
>>>
>>> diff --git a/Documentation/devicetree/bindings/arm/amlogic.yaml b/Documentation/devicetree/bindings/arm/amlogic.yaml
>>> index 08d9963fe9259..55663e0f7f915 100644
>>> --- a/Documentation/devicetree/bindings/arm/amlogic.yaml
>>> +++ b/Documentation/devicetree/bindings/arm/amlogic.yaml
>>> @@ -247,6 +247,12 @@ properties:
>>> - amlogic,aq222
>>> - const: amlogic,s4
Look here
>>>
>>> + - description: Boards with the Amlogic Meson S4 S905Y4 SoC
>>> + items:
>>> + - enum:
>>
>> Yopu already have exactly such enum with such description, so your
>> compatible goes there. Look - it is called "Boards" - plural.
>
> The exist board aq222 is based on SoC S905X2, but the new board vim1s
> is baed on S905Y4,
> they are different SoC, so we need to put S905Y4 under S805X2 ?
What is the point of having two separate lists with enums ending the
same SoC compatible?
>
>>
>>> + - khadas,vim1s
>>> + - const: amlogic,s4
And here.
>>
>> Best regards,
>> Krzysztof
>>
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-01-14 10:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 6:25 [PATCH v2 0/2] arm64: dts: meson-s4: add support for Khadas VIM1S Nick Xie
2026-01-14 6:25 ` [PATCH v2 1/2] dt-bindings: arm: amlogic: add Khadas VIM1S binding Nick Xie
2026-01-14 8:51 ` Krzysztof Kozlowski
2026-01-14 10:07 ` Nick Xie
2026-01-14 10:13 ` neil.armstrong
2026-01-14 10:33 ` Krzysztof Kozlowski [this message]
2026-01-14 11:25 ` Nick Xie
2026-01-14 12:07 ` neil.armstrong
2026-01-14 12:06 ` neil.armstrong
2026-01-14 6:25 ` [PATCH v2 2/2] arm64: dts: add initial device-tree for Khadas VIM1S Nick Xie
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=39bb1820-6e4d-4f50-87e0-93844d779f6c@kernel.org \
--to=krzk@kernel.org \
--cc=christianshewitt@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=krzk+dt@kernel.org \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.blumenstingl@googlemail.com \
--cc=neil.armstrong@linaro.org \
--cc=nick@khadas.com \
--cc=robh@kernel.org \
--cc=xianwei.zhao@amlogic.com \
--cc=xieqinick@gmail.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