mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Yi xin Zhu <yzhu@maxlinear.com>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
	"kees@kernel.org" <kees@kernel.org>,
	"dave.jiang@intel.com" <dave.jiang@intel.com>,
	"av2082000@gmail.com" <av2082000@gmail.com>,
	"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 1/3] dt-bindings: lgm-dma: Added intel,dma-sw-desc property.
Date: Fri, 15 Aug 2025 10:32:01 +0200	[thread overview]
Message-ID: <a0a1bc99-0322-4f63-a903-12983facddc9@kernel.org> (raw)
In-Reply-To: <SA1PR19MB490961745C428F56D7E114F7C234A@SA1PR19MB4909.namprd19.prod.outlook.com>

On 15/08/2025 09:07, Yi xin Zhu wrote:
> Hi Krzysztof,
> 
> On 08/08/2025 14:10, Krzysztof wrote:
>>
>>
>> Where is the changelog?
>>
> Sorry for missing the changelog.  I will include it in V3 patch.
> 
>>> +  intel,dma-sw-desc:
>>> +    type: boolean
>>> +    description:
>>> +      Indicates that the DMA driver should operate in 
>>> + software-managed
>> mode.
>>> +      If this property is not present, it implies that DMA 
>>> + descriptors are
>> managed and generated by another hardware component that controls the 
>> DMA engine.
>>
>> Nothing improved:
>> 1. Still wrongly wrapped.
>> 2. Still SW property.
>>
>> I don't think you read the feedback. You need to describe hardware, not SW.
>>
>> Best regards,
>> Krzysztof
> 
> Could you please give me some advice with regarding to the device tree attribute?
> My understanding is if I can create a phandle link to describe the DMA descriptors are provided by some HW component.  
> That follows the comments. Something like this:
> 
> intel,dma-desc-provider = <&xxx_hw>;
> 
> Then it describes some HW component manages the DMA descriptors.


It is not sufficient to tell. Creating phandles representing fake
hardware is still not hardware description.

> Without it, it means SW manage the DMA descriptors.
> Please correct me if my understanding is wrong.


Yes, it is wrong, because you focus on syntax instead of on the hardware
problem or hardware characteristic.

> 
> However, in the existing driver,  HW manages descriptor mode is the default mode.
> I can't create such link in the device tree without breaking the devicetree ABI.
> So, is it okay I create an attribute like below ?
> 
> Intel,dma-desc-provider = "CPU";   // it means CPU manage DMA descriptors.
> 
> Intel,dma-desc-provider = "XXX_HW";  // it means XX_HW manage DMA descriptors.


And how is it not a OS policy? Bring reasoning and arguments, otherwise
I cannot help you. Your reply above has zero hardware-related arguments,
zero facts, zero hardware description.

Best regards,
Krzysztof

  reply	other threads:[~2025-08-15  8:32 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-08  3:22 Zhu Yixin
2025-08-08  3:22 ` [PATCH v2 2/3] dmaengine: lgm-dma: splitting CDMA and HDMA functions Zhu Yixin
2025-08-08  3:22 ` [PATCH v2 3/3] dmaengine: lgm-dma: Added Software management functions on HDMA Zhu Yixin
2025-08-08  6:11   ` Krzysztof Kozlowski
2025-08-15  6:51     ` Yi xin Zhu
2025-08-08  6:09 ` [PATCH v2 1/3] dt-bindings: lgm-dma: Added intel,dma-sw-desc property Krzysztof Kozlowski
2025-08-15  7:07   ` Yi xin Zhu
2025-08-15  8:32     ` Krzysztof Kozlowski [this message]
2025-08-15 10:06       ` Yi xin Zhu
2025-08-15 10:40         ` Krzysztof Kozlowski
2025-08-18  8:41           ` Yi xin Zhu
2025-08-24 10:26             ` Krzysztof Kozlowski

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=a0a1bc99-0322-4f63-a903-12983facddc9@kernel.org \
    --to=krzk@kernel.org \
    --cc=av2082000@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=dave.jiang@intel.com \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=kees@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=vkoul@kernel.org \
    --cc=yzhu@maxlinear.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

all inboxes | Powered by JetHome®