devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Nishanth Menon <nm@ti.com>, Tero Kristo <kristo@kernel.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Vignesh Raghavendra <vigneshr@ti.com>
Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, afd@ti.com
Subject: Re: [PATCH v2 0/3] arm64: dts: ti: Introduce AM62P5 SoC and board
Date: Mon, 14 Aug 2023 21:26:57 +0200	[thread overview]
Message-ID: <5a1ed797-d29a-e047-ccec-adb1dde6d74f@linaro.org> (raw)
In-Reply-To: <169179403348.1346194.1236976094485793819.b4-ty@ti.com>

On 12/08/2023 00:49, Nishanth Menon wrote:
> Hi Vignesh Raghavendra,
> 
> On Sat, 12 Aug 2023 00:14:29 +0530, Vignesh Raghavendra wrote:
>> This series adds basic support for AM62P family of SoCs and specifically
>> AM62P5 variant. Also adds AM62P5-SK support with basic peripheral
>> like UART.
>>
>> TRM at [0] and Schematics is at [1]
>>
>> [0]: https://www.ti.com/lit/pdf/spruj83
>> [1]: https://www.ti.com/lit/zip/sprr487
>>
>> [...]
> 
> Note: since the changes were trivial, I incorporated the cosmetic
> fixup suggested by Andrew locally when I applied. I have also dropped
> bootph property from board's reserved nodes inline with what we did
> for j721s2[2]. Thanks for the bootlog.
> 
> I have applied the following to branch ti-k3-dts-next on [1].
> Thank you!
> 
> [1/3] dt-bindings: arm: ti: Add bindings for AM62P5 SoCs
>       commit: b57fc5cbdbdfd04d44697800a9d59aeb3be2f273
> [2/3] arm64: dts: ti: Introduce AM62P5 family of SoCs
>       commit: 29075cc09f43a024d962da66d2e4f9eb577713d0
> [3/3] arm64: dts: ti: Add support for the AM62P5 Starter Kit
>       commit: 935c4047d42e53a06ec768ddc495a44f6869209c
> 

A bit too fast. simple-mfd *is not allowed* on its own.

Best regards,
Krzysztof


  reply	other threads:[~2023-08-14 19:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-11 18:44 [PATCH v2 0/3] arm64: dts: ti: Introduce AM62P5 SoC and board Vignesh Raghavendra
2023-08-11 18:44 ` [PATCH v2 1/3] dt-bindings: arm: ti: Add bindings for AM62P5 SoCs Vignesh Raghavendra
2023-08-11 18:44 ` [PATCH v2 2/3] arm64: dts: ti: Introduce AM62P5 family of SoCs Vignesh Raghavendra
2023-08-14 19:24   ` Krzysztof Kozlowski
2023-08-11 18:44 ` [PATCH v2 3/3] arm64: dts: ti: Add support for the AM62P5 Starter Kit Vignesh Raghavendra
2023-08-11 18:53   ` Andrew Davis
2023-08-11 22:49 ` [PATCH v2 0/3] arm64: dts: ti: Introduce AM62P5 SoC and board Nishanth Menon
2023-08-14 19:26   ` Krzysztof Kozlowski [this message]
2023-08-14 20:33     ` Nishanth Menon
2023-08-14 20:54     ` Andrew Davis
2023-08-15  6:59       ` Vignesh Raghavendra
2023-08-15 13:56         ` Andrew Davis
2023-08-16  4:00         ` Vignesh Raghavendra

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=5a1ed797-d29a-e047-ccec-adb1dde6d74f@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=afd@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=kristo@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.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).