soc.lore.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicolas Ferre <nicolas.ferre@microchip.com>
To: Eugen Hristev <eugen.hristev@microchip.com>, <robh+dt@kernel.org>
Cc: <alexandre.belloni@bootlin.com>, <soc@kernel.org>,
	<devicetree@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <ludovic.desroches@microchip.com>,
	<claudiu.beznea@microchip.com>, <codrin.ciubotariu@microchip.com>,
	"Rob Herring" <robh@kernel.org>
Subject: Re: [PATCH v5 1/4] dt-bindings: ARM: at91: document sama7g5ek board
Date: Fri, 16 Jul 2021 21:19:21 +0200	[thread overview]
Message-ID: <e6f704c2-bc96-7c3c-5100-e16303d5193e@microchip.com> (raw)
Message-ID: <20210716191921.ThcOzWpxvT7yZBYaeHF4_V2ciGWrwiZPz4LYRql7nTc@z> (raw)
In-Reply-To: <20210628120452.74408-1-eugen.hristev@microchip.com>

On 28/06/2021 at 14:04, Eugen Hristev wrote:
> Document the SAMA7G5 Evaluation Kit based on sama7g5 SoC.
> 
> Acked-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Eugen Hristev <eugen.hristev@microchip.com>

Series look good to me. I queue 1-2 in at91-dt and 2-3 in at91-defconfig 
for 5.15.
It'll be in at91-next for a few days for 0-day robot consumption.

Best regards,
   Nicolas

> ---
>   Documentation/devicetree/bindings/arm/atmel-at91.yaml | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/Documentation/devicetree/bindings/arm/atmel-at91.yaml b/Documentation/devicetree/bindings/arm/atmel-at91.yaml
> index 6fc5a22ad962..fba071b9af1d 100644
> --- a/Documentation/devicetree/bindings/arm/atmel-at91.yaml
> +++ b/Documentation/devicetree/bindings/arm/atmel-at91.yaml
> @@ -145,6 +145,11 @@ properties:
>             - const: atmel,sama5d4
>             - const: atmel,sama5
>   
> +      - items:
> +          - const: microchip,sama7g5ek # SAMA7G5 Evaluation Kit
> +          - const: microchip,sama7g5
> +          - const: microchip,sama7
> +
>         - items:
>             - enum:
>                 - atmel,sams70j19
> 


-- 
Nicolas Ferre

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2021-07-16 19:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-28 12:04 [PATCH v5 1/4] dt-bindings: ARM: at91: document sama7g5ek board Eugen Hristev
2021-06-28 12:04 ` Eugen Hristev
2021-06-28 12:04 ` [PATCH v5 2/4] ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek Eugen Hristev
2021-06-28 12:04   ` Eugen Hristev
2021-06-28 12:04 ` [PATCH v5 3/4] ARM: configs: at91: add defconfig for sama7 family of SoCs Eugen Hristev
2021-06-28 12:04   ` Eugen Hristev
2021-06-28 12:04 ` [PATCH v5 4/4] ARM: multi_v7_defconfig: add sama7g5 SoC Eugen Hristev
2021-06-28 12:04   ` Eugen Hristev
2021-07-16 19:19 ` Nicolas Ferre [this message]
2021-07-16 19:19   ` [PATCH v5 1/4] dt-bindings: ARM: at91: document sama7g5ek board Nicolas Ferre

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=e6f704c2-bc96-7c3c-5100-e16303d5193e@microchip.com \
    --to=nicolas.ferre@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@microchip.com \
    --cc=codrin.ciubotariu@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eugen.hristev@microchip.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ludovic.desroches@microchip.com \
    --cc=robh+dt@kernel.org \
    --cc=robh@kernel.org \
    --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).