From: Rob Herring <robh@kernel.org>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
soc@kernel.org, "Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board
Date: Thu, 9 Feb 2023 11:35:34 -0600 [thread overview]
Message-ID: <20230209173534.GA539622-robh@kernel.org> (raw)
In-Reply-To: <20230209025525.148872-2-colin.foster@in-advantage.com>
On Wed, Feb 08, 2023 at 06:55:24PM -0800, Colin Foster wrote:
> Add documentation for additional OMAP SOMs and development platforms,
> provided by Phytec as the PCM-049 SOM and the PCM-959 development kit.
>
> Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>
> v2->v3
> * Add Krzysztof Acked
>
> v1->v2
> * New patch
>
> ---
> Documentation/devicetree/bindings/arm/omap/omap.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
> index fa8b31660cad..0a28215dfa12 100644
> --- a/Documentation/devicetree/bindings/arm/omap/omap.txt
> +++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
> @@ -131,6 +131,9 @@ Boards (incomplete list of examples):
> - OMAP4 PandaBoard : Low cost community board
> compatible = "ti,omap4-panda", "ti,omap4430", "ti,omap4"
>
> +- OMAP4 PCM-959 : Commercial dev kit with PCM-049 SOM
> + compatible = "phytec,pcm959", "phytec,pcm049", "ti,omap4460", "ti,omap4430", "ti,omap4";
OMAP maintainers, if no one is going to convert all of omap.txt over to
schema, can we at least start an empty schema and add to it instead of
here...
Rob
WARNING: multiple messages have this Message-ID (diff)
From: Rob Herring <robh@kernel.org>
To: Colin Foster <colin.foster@in-advantage.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
"Tony Lindgren" <tony@atomide.com>,
"Benoît Cousson" <bcousson@baylibre.com>,
soc@kernel.org, "Olof Johansson" <olof@lixom.net>,
"Arnd Bergmann" <arnd@arndb.de>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski@linaro.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board
Date: Thu, 9 Feb 2023 11:35:34 -0600 [thread overview]
Message-ID: <20230209173534.GA539622-robh@kernel.org> (raw)
In-Reply-To: <20230209025525.148872-2-colin.foster@in-advantage.com>
On Wed, Feb 08, 2023 at 06:55:24PM -0800, Colin Foster wrote:
> Add documentation for additional OMAP SOMs and development platforms,
> provided by Phytec as the PCM-049 SOM and the PCM-959 development kit.
>
> Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> Acked-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
>
> v2->v3
> * Add Krzysztof Acked
>
> v1->v2
> * New patch
>
> ---
> Documentation/devicetree/bindings/arm/omap/omap.txt | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/arm/omap/omap.txt b/Documentation/devicetree/bindings/arm/omap/omap.txt
> index fa8b31660cad..0a28215dfa12 100644
> --- a/Documentation/devicetree/bindings/arm/omap/omap.txt
> +++ b/Documentation/devicetree/bindings/arm/omap/omap.txt
> @@ -131,6 +131,9 @@ Boards (incomplete list of examples):
> - OMAP4 PandaBoard : Low cost community board
> compatible = "ti,omap4-panda", "ti,omap4430", "ti,omap4"
>
> +- OMAP4 PCM-959 : Commercial dev kit with PCM-049 SOM
> + compatible = "phytec,pcm959", "phytec,pcm049", "ti,omap4460", "ti,omap4430", "ti,omap4";
OMAP maintainers, if no one is going to convert all of omap.txt over to
schema, can we at least start an empty schema and add to it instead of
here...
Rob
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-02-09 17:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 2:55 [PATCH v3 0/2] add support for Phytec PCM-049 and PCM-959 Colin Foster
2023-02-09 2:55 ` Colin Foster
2023-02-09 2:55 ` [PATCH v3 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board Colin Foster
2023-02-09 2:55 ` Colin Foster
2023-02-09 17:35 ` Rob Herring [this message]
2023-02-09 17:35 ` Rob Herring
2023-02-15 7:14 ` Tony Lindgren
2023-02-15 7:14 ` Tony Lindgren
2023-02-15 16:46 ` Colin Foster
2023-02-15 16:46 ` Colin Foster
2023-02-16 6:51 ` Tony Lindgren
2023-02-16 6:51 ` Tony Lindgren
2023-02-09 2:55 ` [PATCH v3 2/2] arm: dts: omap4: pcm959: add initial support for phytec pcm959 Colin Foster
2023-02-09 2:55 ` Colin Foster
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=20230209173534.GA539622-robh@kernel.org \
--to=robh@kernel.org \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=colin.foster@in-advantage.com \
--cc=devicetree@vger.kernel.org \
--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=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=soc@kernel.org \
--cc=tony@atomide.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.