DMA Engine development
 help / color / mirror / Atom feed
From: Vaishnav Achath <vaishnav.a@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <peter.ujfalusi@gmail.com>,
	<vkoul@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
	<conor+dt@kernel.org>, <dmaengine@vger.kernel.org>,
	<devicetree@vger.kernel.org>
Cc: <linux-kernel@vger.kernel.org>, <u-kumar1@ti.com>,
	<j-choudhary@ti.com>, <vigneshr@ti.com>
Subject: Re: [PATCH v2 1/2] dt-bindings: dma: ti: k3-bcdma: Add J722S CSI BCDMA
Date: Wed, 27 Nov 2024 10:32:30 +0530	[thread overview]
Message-ID: <3df3d649-b921-49db-a050-ef935b7e9748@ti.com> (raw)
In-Reply-To: <8399720e-2a91-4374-b049-ff1d7e66d83e@kernel.org>

Hi Krzysztof,

On 26/11/24 19:49, Krzysztof Kozlowski wrote:
> On 26/11/2024 13:51, Vaishnav Achath wrote:
>> J722S CSI BCDMA is similar to J721S2 CSI BCDMA and
>> supports both RX and TX channels. Add an entry for
>> J722S CSIRX BCDMA.
> 
> Please wrap commit message according to Linux coding style / submission
> process (neither too early nor over the limit):
> https://elixir.bootlin.com/linux/v6.4-rc1/source/Documentation/process/submitting-patches.rst#L597
> 

I will fix this in next revision.

>>
>> Signed-off-by: Vaishnav Achath <vaishnav.a@ti.com>
>> ---
>>
>> V1->V2:
>>    * Address review from Conor to add new J722S compatible
>>    * J722S BCDMA is more similar to J721S2 in terms of RX/TX support,
>>    add an entry alongside J721S2 instead of modifying AM62A.
>>
>> V1: https://lore.kernel.org/all/20241125083914.2934815-1-vaishnav.a@ti.com/
>>
>>   Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml | 4 +++-
>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml b/Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml
>> index 27b8e1636560..37832c71bd8e 100644
>> --- a/Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml
>> +++ b/Documentation/devicetree/bindings/dma/ti/k3-bcdma.yaml
>> @@ -196,7 +196,9 @@ allOf:
>>         properties:
>>           compatible:
>>             contains:
>> -            const: ti,j721s2-dmss-bcdma-csi
>> +            enum:
>> +              - ti,j721s2-dmss-bcdma-csi
>> +              - ti,j722s-dmss-bcdma-csi
> 
> This compatible was never documented. There is no dependency here, no
> cover letter explaining where is this compatible introduced.
> 
> 

This was a mistake from my end, sorry about that, it was supposed to be 
introduced in this patch itself, will fix it in the next revision. Thank 
you for the review.

Thanks and Regards,
Vaishnav

> 
> 
> Best regards,
> Krzysztof

      reply	other threads:[~2024-11-27  5:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-26 12:51 [PATCH v2 1/2] dt-bindings: dma: ti: k3-bcdma: Add J722S CSI BCDMA Vaishnav Achath
2024-11-26 12:51 ` [PATCH v2 2/2] dmaengine: ti: k3-udma: Add support for " Vaishnav Achath
2024-11-26 14:19 ` [PATCH v2 1/2] dt-bindings: dma: ti: k3-bcdma: Add " Krzysztof Kozlowski
2024-11-27  5:02   ` Vaishnav Achath [this message]

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=3df3d649-b921-49db-a050-ef935b7e9748@ti.com \
    --to=vaishnav.a@ti.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=j-choudhary@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peter.ujfalusi@gmail.com \
    --cc=robh@kernel.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vkoul@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