Linux SOC development
 help / color / mirror / Atom feed
From: INAGAKI Hiroshi <musashino.open@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Cc: andrew@lunn.ch, gregory.clement@bootlin.com,
	sebastian.hesselbarth@gmail.com, arnd@arndb.de, olof@lixom.net,
	soc@kernel.org, robh+dt@kernel.org,
	krzysztof.kozlowski+dt@linaro.org
Subject: Re: [PATCH 2/2] ARM: dts: mvebu: add device tree for IIJ SA-W2 appliance
Date: Sat, 4 Mar 2023 13:57:22 +0900	[thread overview]
Message-ID: <0fd898ed-9288-2030-956a-0fa4d1afc3b5@gmail.com> (raw)
In-Reply-To: <23f7e0d9-32e5-654d-9b4d-84c91f833b2f@linaro.org>

Hi Krzysztof,

On 2023/02/25 22:11, Krzysztof Kozlowski wrote:
> On 25/02/2023 13:48, INAGAKI Hiroshi wrote:
>> 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.
> I don't understand why we need three or more files... all or almost all
> platforms are having them in one file. So just merge them to one.
>
>> Questions:
>>
>> - who should be assigned to "maintainers:" in new yaml?
> Maintainer of platform.
>
>> - should the old text file be deleted when new yaml is created?
> If you convert, then yes, but we did not talk about conversion but at
> least starting documenting the new ones.

thank you for your answers and sorry for my misunderstandings...

So, (to organize my thoughts and understand correctly)

- what is the optimal solution for "documenting the board compatibles" 
of Marvell platforms in the current state?
- What should I do in this contribution of SA-W2 for "documenting the 
board compatibles"?

>
>
>
> Best regards,
> Krzysztof
>

Regards,
Hiroshi

  reply	other threads:[~2023-03-04  4:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230223132502.2045-1-musashino.open@gmail.com>
2023-02-23 13:25 ` [PATCH 2/2] ARM: dts: mvebu: add device tree for IIJ SA-W2 appliance INAGAKI Hiroshi
2023-02-23 14:17   ` Krzysztof Kozlowski
2023-02-24 12:28     ` INAGAKI Hiroshi
2023-02-24 12:53       ` Krzysztof Kozlowski
2023-02-25 12:48         ` INAGAKI Hiroshi
2023-02-25 13:11           ` Krzysztof Kozlowski
2023-03-04  4:57             ` INAGAKI Hiroshi [this message]
2023-02-23 14:43   ` Andrew Lunn
2023-02-24 12:57     ` INAGAKI Hiroshi
2023-04-07 15:34       ` Gregory CLEMENT
2023-04-09  5:13         ` INAGAKI Hiroshi
2023-04-09 14:07           ` Andrew Lunn
2023-04-12  5:21             ` INAGAKI Hiroshi
2023-04-12 12:26               ` Andrew Lunn

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=0fd898ed-9288-2030-956a-0fa4d1afc3b5@gmail.com \
    --to=musashino.open@gmail.com \
    --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=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --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