From: Colin Foster <colin.foster@in-advantage.com>
To: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Cc: "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>,
"Rob Herring" <robh+dt@kernel.org>, "Andrew Davis" <afd@ti.com>
Subject: Re: [PATCH v4 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board
Date: Wed, 22 Feb 2023 13:40:41 -0800 [thread overview]
Message-ID: <Y/aL2fquXe0aJleG@colin-ia-desktop> (raw)
In-Reply-To: <20230222203847.2664903-2-colin.foster@in-advantage.com>
On Wed, Feb 22, 2023 at 12:38:46PM -0800, Colin Foster wrote:
> Add yaml documentation for TI OMAP devices for the Phytec PCM-049 SoM and
> the Phytec PCM-959 development kit.
>
> Signed-off-by: Colin Foster <colin.foster@in-advantage.com>
> ---
>
> v4
> * New patch, based on a WIP from Andrew Davis <afd@ti.com>
>
> ---
> .../devicetree/bindings/arm/ti,omap.yaml | 29 +++++++++++++++++++
> 1 file changed, 29 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/arm/ti,omap.yaml
>
> diff --git a/Documentation/devicetree/bindings/arm/ti,omap.yaml b/Documentation/devicetree/bindings/arm/ti,omap.yaml
> new file mode 100644
> index 000000000000..9c0e08f74fee
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/arm/ti,omap.yaml
> @@ -0,0 +1,29 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/arm/ti,omap.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: Texas Instruments OMAP SoC architecture
> +
> +maintainers:
> + - Tony Lindgren <tony@atomide.com>
> +
> +description:
> + Platforms based on Texas Instruments OMAP SoC architecture.
> +
> +properties:
> + $nodename:
> + const: '/'
> + compatibnle:
Oops. Caught this typo too late. I can wait until after the merge window
or resend next week. There's probably other feedback.
> + oneOf:
> +
> + - description: TI OMAP 4460 SoC based platforms
> + items:
> + - enum:
> + - phytec,pcm049 # Phytec OMAP 4460 SoM
> + - phytec,pcm959 # Phytec development board for the pcm049
> + - const: ti,omap4460
> + - const: ti,omap4
> +
> +additionalProperties: true
> --
> 2.25.1
>
next prev parent reply other threads:[~2023-02-22 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 20:38 [PATCH v4 0/2] add support for Phytec PCM-049 and PCM-959 Colin Foster
2023-02-22 20:38 ` [PATCH v4 1/2] dt-bindings: arm: omap: add phytec pcm-049 som and pcm-959 dev board Colin Foster
2023-02-22 21:40 ` Colin Foster [this message]
2023-02-23 16:00 ` Andrew Davis
2023-02-23 16:25 ` Colin Foster
2023-02-23 17:17 ` Andrew Davis
2023-02-26 17:22 ` Rob Herring
2023-02-27 7:15 ` Tony Lindgren
2023-02-22 20:38 ` [PATCH v4 2/2] arm: dts: omap4: pcm959: add initial support for phytec pcm959 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=Y/aL2fquXe0aJleG@colin-ia-desktop \
--to=colin.foster@in-advantage.com \
--cc=afd@ti.com \
--cc=arnd@arndb.de \
--cc=bcousson@baylibre.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@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=robh+dt@kernel.org \
--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 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).