From: Huang Shijie <sjhuang@iluvatar.ai>
To: Vinod <vkoul@kernel.org>
Cc: corbet@lwn.net, dan.j.williams@intel.com, robh@kernel.org,
linux-doc@vger.kernel.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: add a new helper dmam_async_device_register
Date: Thu, 26 Jul 2018 09:21:17 +0800 [thread overview]
Message-ID: <452f2991-241b-1f0f-efad-9c7e37814c5e@iluvatar.ai> (raw)
In-Reply-To: <20180725123826.GT3661@vkoul-mobl>
Hi Vinod,
在 2018年07月25日 20:38, Vinod 写道:
> On 25-07-18, 13:46, Huang Shijie wrote:
>> This patch adds the dmam_async_device_register for DMA code.
>> Use the Devres to call the release for the DMA engine driver.
> no users?
I can add some new users if you want.
I will add an extra patch for it.
>
>> Signed-off-by: Huang Shijie <sjhuang@iluvatar.ai>
>> ---
>> Documentation/driver-model/devres.txt | 1 +
>> drivers/dma/dmaengine.c | 35 +++++++++++++++++++++++++++
>> include/linux/dmaengine.h | 1 +
>> 3 files changed, 37 insertions(+)
>>
>> diff --git a/Documentation/driver-model/devres.txt b/Documentation/driver-model/devres.txt
>> index a3e8bceb5f19..26c6de621446 100644
>> --- a/Documentation/driver-model/devres.txt
>> +++ b/Documentation/driver-model/devres.txt
>> @@ -240,6 +240,7 @@ CLOCK
>> devm_of_clk_add_hw_provider()
>>
>> DMA
>> + dmam_async_device_register()
> can we name it dmaengine_async_device_register, not to confuse with dma APIs
ok.
If no one objects the dmaengine_async_device_register().
I will use it in the next version.
Thanks
Huang Shijie
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2018-07-26 1:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-25 5:46 [PATCH] dmaengine: add a new helper dmam_async_device_register Huang Shijie
2018-07-25 12:38 ` Vinod
2018-07-26 1:21 ` Huang Shijie [this message]
2018-07-26 4:10 ` Vinod
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=452f2991-241b-1f0f-efad-9c7e37814c5e@iluvatar.ai \
--to=sjhuang@iluvatar.ai \
--cc=corbet@lwn.net \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-doc@vger.kernel.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