From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tony Dinh <mibodhi@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Gregory Clement <gregory.clement@bootlin.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Arnd Bergmann <arnd@arndb.de>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Olof Johansson <olof@lixom.net>, Rob Herring <robh+dt@kernel.org>,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
linux-kernel@vger.kernel.org, soc@kernel.org
Subject: Re: [PATCH] ARM: dts: mvebu: Add support for Thecus N2350 board
Date: Fri, 17 Feb 2023 09:38:38 +0100 [thread overview]
Message-ID: <fb9c9533-b72b-7e20-0ee2-cca6491ea2af@linaro.org> (raw)
In-Reply-To: <CAJaLiFypS2wtsj65D1WrSjsgDeN+jpUVYcbvOHdiYvneiCK_Aw@mail.gmail.com>
On 16/02/2023 22:25, Tony Dinh wrote:
> Hi Andrew,
> Hi Krzysztof,
>
> On Thu, Feb 16, 2023 at 12:31 AM Krzysztof Kozlowski
> <krzysztof.kozlowski@linaro.org> wrote:
>>
>> On 16/02/2023 02:10, Tony Dinh wrote:
>>> Thecus N2350 is a NAS based on Marvell Armada 385 SoC.
>>>
>>> Board Specification:
>>>
>>> - Marvel MV88F6820 Dual Core at 1GHz
>>> - 1 GiB DDR4 RAM
>>> - 4MB Macronix mx25l3205d SPI flash
>>> - 512MB Hynix H27U4G8F2DTR-BC NAND flash
>>> - I2C
>>> - 2x USB 3.0
>>> - 1x GBE LAN port (PHY: Marvell 88E1510)
>>> - 2x SATA (hot swap slots)
>>> - 3x buttons
>>> - 10x LEDS
>>> - serial console
>>>
>>> Signed-off-by: Tony Dinh <mibodhi@gmail.com>
>>> ---
>>>
>>> arch/arm/boot/dts/Makefile | 1 +
>>> arch/arm/boot/dts/armada-385-thecus-n2350.dts | 432 ++++++++++++++++++
>>> 2 files changed, 433 insertions(+)
>>> create mode 100644 arch/arm/boot/dts/armada-385-thecus-n2350.dts
>>>
>>> diff --git a/arch/arm/boot/dts/Makefile b/arch/arm/boot/dts/Makefile
>>> index d08a3c450..749790e6e 100644
>>> --- a/arch/arm/boot/dts/Makefile
>>> +++ b/arch/arm/boot/dts/Makefile
>>> @@ -1528,6 +1528,7 @@ dtb-$(CONFIG_MACH_ARMADA_38X) += \
>>> armada-385-linksys-rango.dtb \
>>> armada-385-linksys-shelby.dtb \
>>> armada-385-synology-ds116.dtb \
>>> + armada-385-thecus-n2350.dtb \
>>> armada-385-turris-omnia.dtb \
>>> armada-388-clearfog.dtb \
>>> armada-388-clearfog-base.dtb \
>>> diff --git a/arch/arm/boot/dts/armada-385-thecus-n2350.dts b/arch/arm/boot/dts/armada-385-thecus-n2350.dts
>>> new file mode 100644
>>> index 000000000..38114d842
>>> --- /dev/null
>>> +++ b/arch/arm/boot/dts/armada-385-thecus-n2350.dts
>>> @@ -0,0 +1,432 @@
>>> +// SPDX-License-Identifier: (GPL-2.0 OR MIT)
>>> +/*
>>> + * Device Tree file for Thecus N2350 board
>>> + *
>>> + * Copyright (C) 2018-2023 Tony Dinh <mibodhi@gmail.com>
>>> + * Copyright (C) 2018 Manuel Jung <manuel.jung@hotmail.com>
>>> + */
>>> +
>>> +/dts-v1/;
>>> +#include <dt-bindings/input/input.h>
>>> +#include <dt-bindings/gpio/gpio.h>
>>> +#include "armada-385.dtsi"
>>> +
>>> +/ {
>>> + model = "Thecus N2350";
>>> + compatible = "thecus,n2350", "marvell,armada385";
>>
>> Missing vendor prefix documentation. I wanted to say: "missing new
>> compatible documentation", but seems Marvell is missing these. Let's
>> start documenting at least new compatibles in YAML? Like Rob proposed
>> here for OMAP:
>> https://lore.kernel.org/all/20230209173534.GA539622-robh@kernel.org/
>
> I was under the impression that the Documentation patch has to be a
> separate patch, as stated in
> Documentation/devicetree/bindings/submitting-patches.rst. Should I
> include documentation in this add-support patch?
Yes, it must be separate patch and must be first in the patchset using
new compatibles. Otherwise when we apply this, we get warnings of
undocumented compatibles.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-02-17 8:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-16 1:10 [PATCH] ARM: dts: mvebu: Add support for Thecus N2350 board Tony Dinh
2023-02-16 3:59 ` Andrew Lunn
2023-02-16 8:31 ` Krzysztof Kozlowski
2023-02-16 21:25 ` Tony Dinh
2023-02-17 8:38 ` Krzysztof Kozlowski [this message]
2023-04-07 15:36 ` Gregory CLEMENT
2023-04-07 19:50 ` Tony Dinh
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=fb9c9533-b72b-7e20-0ee2-cca6491ea2af@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=andrew@lunn.ch \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=gregory.clement@bootlin.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mibodhi@gmail.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=soc@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;
as well as URLs for NNTP newsgroup(s).