From: Cai Huoqing <cai.huoqing@linux.dev>
To: fancer.lancer@gmail.com
Cc: caihuoqing <caihuoqing@baidu.com>,
Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Vinod Koul <vkoul@kernel.org>,
linux-kernel@vger.kernel.org, dmaengine@vger.kernel.org
Subject: [PATCH 1/3] dmaengine: dw-edma: Rename dw_edma_core_ops structure to dw_edma_plat_ops
Date: Wed, 21 Sep 2022 14:48:50 +0800 [thread overview]
Message-ID: <20220921064859.10328-2-cai.huoqing@linux.dev> (raw)
In-Reply-To: <20220921064859.10328-1-cai.huoqing@linux.dev>
From: caihuoqing <caihuoqing@baidu.com>
Rename dw_edma_core_ops structure to dw_edma_plat_ops,
because the 'ops' is related to platform device
Signed-off-by: caihuoqing <caihuoqing@baidu.com>
---
drivers/dma/dw-edma/dw-edma-pcie.c | 4 ++--
include/linux/dma/edma.h | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/dma/dw-edma/dw-edma-pcie.c b/drivers/dma/dw-edma/dw-edma-pcie.c
index 3f9dadc73854..5604f3771866 100644
--- a/drivers/dma/dw-edma/dw-edma-pcie.c
+++ b/drivers/dma/dw-edma/dw-edma-pcie.c
@@ -109,7 +109,7 @@ static u64 dw_edma_pcie_address(struct device *dev, phys_addr_t cpu_addr)
return region.start;
}
-static const struct dw_edma_core_ops dw_edma_pcie_core_ops = {
+static const struct dw_edma_plat_ops dw_edma_pcie_plat_ops = {
.irq_vector = dw_edma_pcie_irq_vector,
.pci_address = dw_edma_pcie_address,
};
@@ -225,7 +225,7 @@ static int dw_edma_pcie_probe(struct pci_dev *pdev,
chip->mf = vsec_data.mf;
chip->nr_irqs = nr_irqs;
- chip->ops = &dw_edma_pcie_core_ops;
+ chip->ops = &dw_edma_pcie_plat_ops;
chip->ll_wr_cnt = vsec_data.wr_ch_cnt;
chip->ll_rd_cnt = vsec_data.rd_ch_cnt;
diff --git a/include/linux/dma/edma.h b/include/linux/dma/edma.h
index 9d44da4aa59d..642dd325259b 100644
--- a/include/linux/dma/edma.h
+++ b/include/linux/dma/edma.h
@@ -37,7 +37,7 @@ struct dw_edma_region {
* iATU windows. That will be done by the controller
* automatically.
*/
-struct dw_edma_core_ops {
+struct dw_edma_plat_ops {
int (*irq_vector)(struct device *dev, unsigned int nr);
u64 (*pci_address)(struct device *dev, phys_addr_t cpu_addr);
};
@@ -77,7 +77,7 @@ enum dw_edma_chip_flags {
struct dw_edma_chip {
struct device *dev;
int nr_irqs;
- const struct dw_edma_core_ops *ops;
+ const struct dw_edma_plat_ops *ops;
u32 flags;
void __iomem *reg_base;
--
2.25.1
next prev parent reply other threads:[~2022-09-21 6:49 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 ` Cai Huoqing [this message]
2022-11-04 13:42 ` [PATCH 1/3] dmaengine: dw-edma: Rename dw_edma_core_ops structure to dw_edma_plat_ops Vinod Koul
2022-11-07 3:12 ` Cai Huoqing
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=20220921064859.10328-2-cai.huoqing@linux.dev \
--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).