DMA Engine development
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Dharma.B@microchip.com
Cc: Ludovic.Desroches@microchip.com, vkoul@kernel.org,
	robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	Nicolas.Ferre@microchip.com, alexandre.belloni@bootlin.com,
	claudiu.beznea@tuxon.dev, Charan.Pedumuru@microchip.com,
	linux-arm-kernel@lists.infradead.org, dmaengine@vger.kernel.org,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
	Tony.Han@microchip.com, Cristian.Birsan@microchip.com
Subject: Re: [PATCH 2/2] dt-bindings: dma: at_xdmac: document dma-channels property
Date: Wed, 5 Feb 2025 15:16:48 +0100	[thread overview]
Message-ID: <870df4b8-fa96-47c1-b82a-5db52a5f0788@kernel.org> (raw)
In-Reply-To: <74ac11e8-2285-436b-9186-4793cb2b7239@microchip.com>

On 05/02/2025 14:58, Dharma.B@microchip.com wrote:
> Hi Krzysztof,
> 
> On 05/02/25 5:10 pm, Krzysztof Kozlowski wrote:
>> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
>>
>> On Wed, Feb 05, 2025 at 11:17:03AM +0530, Dharma Balasubiramani wrote:
>>> Add document for the property "dma-channels" for XDMA controller.
>>
>> I don't understand why. You are duplicating dma schema.

Here-----------------------^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

>>
>> The same as with other patch - your commit msg is redundant. You say
>> what we see the diff but you never explain why you are doing these
>> changes. And in both cases this is really non-obvious.
>>
>> Apply this feedback to all future contributions - say why you are doing
>> changes instead of repeating what subject and diff are already saying.
> 
> Thanks for your feedback, do you want me to include the description of 
> dma-channels from the diff in the commit message?
> 
> The reason for this change is:
> "This property is required when the channel count cannot be read from 
> the XDMAC_GTYPE register (which occurs when accessing from the 
> non-secure world on certain devices)."
> 
> Isn't this already clear from the description in the diff?


OK, so this describes why you need this. It does not solve why do you
need this patch. Do you see any warnings?

Best regards,
Krzysztof

  reply	other threads:[~2025-02-05 14:16 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05  5:47 [PATCH 0/2] dmaengine: at_xdmac: retrieve DMA channels from device tree Dharma Balasubiramani
2025-02-05  5:47 ` [PATCH 1/2] dmaengine: at_xdmac: get the number of " Dharma Balasubiramani
2025-02-05  5:47 ` [PATCH 2/2] dt-bindings: dma: at_xdmac: document dma-channels property Dharma Balasubiramani
2025-02-05 11:40   ` Krzysztof Kozlowski
2025-02-05 13:58     ` Dharma.B
2025-02-05 14:16       ` Krzysztof Kozlowski [this message]
2025-02-06  2:34         ` Dharma.B

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=870df4b8-fa96-47c1-b82a-5db52a5f0788@kernel.org \
    --to=krzk@kernel.org \
    --cc=Charan.Pedumuru@microchip.com \
    --cc=Cristian.Birsan@microchip.com \
    --cc=Dharma.B@microchip.com \
    --cc=Ludovic.Desroches@microchip.com \
    --cc=Nicolas.Ferre@microchip.com \
    --cc=Tony.Han@microchip.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    --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