From: INAGAKI Hiroshi <musashino.open@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Gregory CLEMENT <gregory.clement@bootlin.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
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: Wed, 12 Apr 2023 14:21:27 +0900 [thread overview]
Message-ID: <231f9093-968b-e008-f2ff-899d8b24459c@gmail.com> (raw)
In-Reply-To: <b153523b-45cf-4e2e-8d62-de15b01a158d@lunn.ch>
Hello Andrew Lunn,
thank you for your guidance, I'll do it.
Regards,
Hiroshi
On 2023/04/09 23:07, Andrew Lunn wrote:
> On Sun, Apr 09, 2023 at 02:13:11PM +0900, INAGAKI Hiroshi wrote:
>> Hello Gregory CLEMENT,
>>
>> On 2023/04/08 0:34, Gregory CLEMENT wrote:
>>> Hello INAGAKI Hiroshi,
>>>
>>> do you plan to send a v2 soon based on the reviews you got ?
>> Yes, I'm planning to send the next series.
>> But I don't know the details about "documenting the board compatibles"
>> suggested by Krzysztof Kozlowski and I don't know what to do for it, so I'm
>> pausing this contribution...
> Create Documentation/devicetree/bindings/arm/marvell/armada-380.yaml
>
> Put in it
>
> # SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> %YAML 1.2
> ---
> $id: http://devicetree.org/schemas/arm/marvell/armada-380.yaml#
> $schema: http://devicetree.org/meta-schemas/core.yaml#
>
> title: Marvell Armada 380 SoC architecture
>
> maintainers:
> - Andrew Lunn <andrew@lunn.ch>
>
> description:
> Platforms based on Marvell Armada 380 SoC architecture.
>
> properties:
> $nodename:
> const: '/'
> compatibnle:
> oneOf:
>
> - description: Marvell Armada 380 SoC based platforms
> items:
> - enum:
> - phytec,pcm049 # Phytec OMAP 4460 SoM
> - const: "marvell,armada380"
>
> additionalProperties: true
>
>
> But replace the phytex,pcm049 with the compatible for your board.
>
> Andrew
next prev parent reply other threads:[~2023-04-12 5:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 13:25 [PATCH 1/2] dt-bindings: vendor-prefixes: add Internet Initiative Japan Inc INAGAKI Hiroshi
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
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 [this message]
2023-04-12 12:26 ` Andrew Lunn
2023-02-23 15:56 ` [PATCH 1/2] dt-bindings: vendor-prefixes: add Internet Initiative Japan Inc Krzysztof Kozlowski
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=231f9093-968b-e008-f2ff-899d8b24459c@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=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;
as well as URLs for NNTP newsgroup(s).