devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Paresh Bhagat <p-bhagat@ti.com>,
	nm@ti.com, vigneshr@ti.com, praneeth@ti.com
Cc: kristo@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
	conor+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	khasim@ti.com, v-singh1@ti.com, afd@ti.com, bb@ti.com,
	devarsht@ti.com
Subject: Re: [PATCHv4 2/6] dt-bindings: arm: ti: Add bindings for AM62D2 SoC
Date: Tue, 24 Jun 2025 12:55:36 +0200	[thread overview]
Message-ID: <6f98274a-88c3-4afc-b324-b024f31e1628@kernel.org> (raw)
In-Reply-To: <c4362d9e-62a4-4c28-b1cd-c338467f92ae@ti.com>

On 24/06/2025 12:39, Paresh Bhagat wrote:
> 
>>>
>>> This SoC is of part K3 AM62x family, which includes the AM62A and AM62P
>>> variants. While the AM62A and AM62D are largely similar, the AM62D is
>>> specifically targeted for general-purpose DSP applications, whereas the
>>> AM62A focuses on edge AI workloads. A key distinction is that the AM62D
>>> does not include multimedia components such as the video encoder/decoder,
>>> MJPEG encoder, Vision Processing Accelerator (VPAC) for image signal
>>> processing, or the display subsystem. Additionally, the AM62D has a
>>> different pin configuration compared to the AM62A, which impacts
>>> embedded software development.
> 
> 
> This section is important as it clarifies the difference between AM62a 
> and AM62d, as we are reusing AM62a dtsi files for AM62d. Let me know if 
> you need a shorter version.

This is not important:

"While the AM62A and AM62D are largely similar, the AM62D is
specifically targeted for general-purpose DSP applications, whereas the
AM62A focuses on edge AI workloads."

It is irrelevant. Rest is fine.

> 
> 
>>>
>>> This adds dt bindings for TI's AM62D2 family of devices.
>>>
>>> More details about the SoCs can be found in the Technical Reference Manual:
>>> https://www.ti.com/lit/pdf/sprujd4
>>>
>>> Signed-off-by: Paresh Bhagat <p-bhagat@ti.com>
>>
>> And what happened with the previous comments?
> 
> 
> Yep there were some indentation problems earlier, which is fixed in this 
> version. There was also an ack from Conor Dooley in v3. I will include that.

Why you did not include it before?

Can you start using b4 for your process of submitting patches?


Best regards,
Krzysztof

  reply	other threads:[~2025-06-24 10:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-23 14:12 [PATCHv4 0/6] Add support for AM62D2 SoC and EVM Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 1/6] arm64: dts: ti: Add bootph property to nodes at source for am62a Paresh Bhagat
2025-06-23 14:45   ` Bryan Brattlof
2025-06-24  9:13     ` Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 2/6] dt-bindings: arm: ti: Add bindings for AM62D2 SoC Paresh Bhagat
2025-06-23 14:25   ` Krzysztof Kozlowski
2025-06-24 10:39     ` Paresh Bhagat
2025-06-24 10:55       ` Krzysztof Kozlowski [this message]
2025-06-24 11:21         ` Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 3/6] arm64: dts: ti: Add pinctrl entries for AM62D2 family of SoCs Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 4/6] arm64: dts: ti: Add support for AM62D2-EVM Paresh Bhagat
2025-06-24  8:21   ` Andrew Lunn
2025-06-26  8:24     ` [EXTERNAL] " Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 5/6] arm64: dts: ti: Update firmware-name for IPC Paresh Bhagat
2025-06-23 14:29   ` Bryan Brattlof
2025-06-24  9:12     ` Paresh Bhagat
2025-06-23 14:12 ` [PATCHv4 6/6] arm64: dts: ti: Add eMMC support for AM62D Paresh Bhagat
2025-06-23 14:28   ` Bryan Brattlof
2025-06-24  9:11     ` Paresh Bhagat

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=6f98274a-88c3-4afc-b324-b024f31e1628@kernel.org \
    --to=krzk@kernel.org \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devarsht@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=khasim@ti.com \
    --cc=kristo@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=p-bhagat@ti.com \
    --cc=praneeth@ti.com \
    --cc=robh@kernel.org \
    --cc=v-singh1@ti.com \
    --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).