[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <473e0ac5-f12a-c66f-6696-8b7fe6e540f0@gmail.com>
Date: Sat, 25 Feb 2023 21:48:30 +0900
From: INAGAKI Hiroshi <musashino.open@...il.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-arm-kernel@...ts.infradead.org
Cc: andrew@...n.ch, gregory.clement@...tlin.com,
sebastian.hesselbarth@...il.com, arnd@...db.de, olof@...om.net,
soc@...nel.org, robh+dt@...nel.org,
krzysztof.kozlowski+dt@...aro.org
Subject: Re: [PATCH 2/2] ARM: dts: mvebu: add device tree for IIJ SA-W2
appliance
Hi Krzysztof,
thank you for the response.
On 2023/02/24 21:53, Krzysztof Kozlowski wrote:
> On 24/02/2023 13:28, INAGAKI Hiroshi wrote:
>
>>>> +
>>>> +/ {
>>>> + model = "IIJ SA-W2";
>>>> + compatible = "iij,sa-w2", "marvell,armada380";
>>> It would be nice to start documenting the board compatibles, at least
>>> for new boards.
>> So...how do I do that?
> Start with something like this for Marvell:
>
> https://lore.kernel.org/all/20230222203847.2664903-2-colin.foster@in-advantage.com/
Oh, got it. So marvell/armada-38x.yaml needs to be created from
armada-38x.txt like armada-37xx.yaml.
Questions:
- who should be assigned to "maintainers:" in new yaml?
- should the old text file be deleted when new yaml is created?
> But maybe someone already started it for Marvell? Marvell SoC
> maintainers might help here to coordinate to avoid duplicated work.
OK, I'll try to add it if no one is working on...
>
> Best regards,
> Krzysztof
>
Regards,
Hiroshi
Powered by blists - more mailing lists