[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6f98274a-88c3-4afc-b324-b024f31e1628@kernel.org>
Date: Tue, 24 Jun 2025 12:55:36 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Paresh Bhagat <p-bhagat@...com>, nm@...com, vigneshr@...com,
praneeth@...com
Cc: kristo@...nel.org, robh@...nel.org, krzk+dt@...nel.org,
conor+dt@...nel.org, linux-arm-kernel@...ts.infradead.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, khasim@...com,
v-singh1@...com, afd@...com, bb@...com, devarsht@...com
Subject: Re: [PATCHv4 2/6] dt-bindings: arm: ti: Add bindings for AM62D2 SoC
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@...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
Powered by blists - more mailing lists