From: Cai Huoqing <cai.huoqing@linux.dev>
To: Vinod Koul <vkoul@kernel.org>
Cc: fancer.lancer@gmail.com, caihuoqing <caihuoqing@baidu.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: Re: [PATCH 1/3] dmaengine: dw-edma: Rename dw_edma_core_ops structure to dw_edma_plat_ops
Date: Mon, 7 Nov 2022 11:12:43 +0800 [thread overview]
Message-ID: <20221107031243.GA10444@chq-T47> (raw)
In-Reply-To: <Y2UWvjNHBGa8PjBZ@matsya>
On 04 11月 22 19:12:22, Vinod Koul wrote:
> On 21-09-22, 14:48, Cai Huoqing wrote:
> > From: caihuoqing <caihuoqing@baidu.com>
> >
> > Rename dw_edma_core_ops structure to dw_edma_plat_ops,
> > because the 'ops' is related to platform device
>
> Is that really a case, the device can be non platform too right?
Hi, Vinod
Just means plat_ops is the common part for different mode or chips.
core_ops is the private part for different spec.
Thanks,
Cai
>
> --
> ~Vinod
next prev parent reply other threads:[~2022-11-07 3:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-21 6:48 [PATCH 0/3] dmaengine: dw-edma: Add support for native HDMA Cai Huoqing
2022-09-21 6:48 ` [PATCH 1/3] dmaengine: dw-edma: Rename dw_edma_core_ops structure to dw_edma_plat_ops Cai Huoqing
2022-11-04 13:42 ` Vinod Koul
2022-11-07 3:12 ` Cai Huoqing [this message]
2023-02-09 23:26 ` Serge Semin
2023-02-09 23:34 ` Serge Semin
2022-09-21 6:48 ` [PATCH 2/3] dmaengine: dw-edma: Create a new dw_edma_core_ops structure to abstract controller operation Cai Huoqing
2022-11-04 13:45 ` Vinod Koul
2022-11-07 3:20 ` Cai Huoqing
2023-02-10 0:57 ` Serge Semin
2023-02-10 17:06 ` Serge Semin
2022-09-21 6:48 ` [PATCH 3/3] dmaengine: dw-edma: Add support for native HDMA Cai Huoqing
2022-11-04 13:53 ` Vinod Koul
2023-02-10 18:13 ` Serge Semin
2022-09-25 17:34 ` [PATCH 0/3] " Serge Semin
2023-02-09 22:40 ` Serge Semin
2023-02-10 0:59 ` Serge Semin
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=20221107031243.GA10444@chq-T47 \
--to=cai.huoqing@linux.dev \
--cc=caihuoqing@baidu.com \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).