From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Cc: "Serge Semin" <fancer.lancer@gmail.com>,
"Alexey Malahov" <Alexey.Malahov@baikalelectronics.ru>,
"Pavel Parkhomenko" <Pavel.Parkhomenko@baikalelectronics.ru>,
"Krzysztof Wilczyński" <kw@linux.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Gustavo Pimentel" <gustavo.pimentel@synopsys.com>,
"Vinod Koul" <vkoul@kernel.org>, "Rob Herring" <robh@kernel.org>,
"Bjorn Helgaas" <bhelgaas@google.com>,
"Lorenzo Pieralisi" <lorenzo.pieralisi@arm.com>,
"Jingoo Han" <jingoohan1@gmail.com>,
"Frank Li" <Frank.Li@nxp.com>,
"Manivannan Sadhasivam" <manivannan.sadhasivam@linaro.org>
Subject: RE: [PATCH v3 19/24] dmaengine: dw-edma: Use non-atomic io-64 methods
Date: Wed, 6 Jul 2022 05:42:31 +0000 [thread overview]
Message-ID: <TYBPR01MB53418C1BC8791CB6D068A177D8809@TYBPR01MB5341.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <20220610091459.17612-20-Sergey.Semin@baikalelectronics.ru>
Hi,
> From: Serge Semin, Sent: Friday, June 10, 2022 6:15 PM
>
> Instead of splitting the 64-bits IOs up into two 32-bits ones it's
> possible to use an available set of the non-atomic readq/writeq methods
> implemented exactly for such cases. They are defined in the dedicated
> header files io-64-nonatomic-lo-hi.h/io-64-nonatomic-hi-lo.h. So in case
> if the 64-bits readq/writeq methods are unavailable on some platforms at
> consideration, the corresponding drivers can have any of these headers
> included and stop locally re-implementing the 64-bits IO accessors taking
> into account the non-atomic nature of the included methods. Let's do that
> in the DW eDMA driver too. Note by doing so we can discard the
> CONFIG_64BIT config ifdefs from the code. Also note that if a platform
> doesn't support 64-bit DBI IOs then the corresponding accessors will just
> directly call the lo_hi_readq()/lo_hi_writeq() methods.
>
> Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
> Reviewed-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> Tested-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
> ---
> drivers/dma/dw-edma/dw-edma-v0-core.c | 71 +++++++++------------------
> 1 file changed, 24 insertions(+), 47 deletions(-)
>
> diff --git a/drivers/dma/dw-edma/dw-edma-v0-core.c b/drivers/dma/dw-edma/dw-edma-v0-core.c
> index e6d611176891..4348d2323125 100644
> --- a/drivers/dma/dw-edma/dw-edma-v0-core.c
> +++ b/drivers/dma/dw-edma/dw-edma-v0-core.c
<snip>
> @@ -417,18 +404,8 @@ void dw_edma_v0_core_start(struct dw_edma_chunk *chunk, bool first)
> SET_CH_32(dw, chan->dir, chan->id, ch_control1,
> (DW_EDMA_V0_CCS | DW_EDMA_V0_LLE));
> /* Linked list */
> - if ((chan->dw->chip->flags & DW_EDMA_CHIP_32BIT_DBI) ||
I'm trying to use this patch series, but I could not apply this patch.
I investigated why, and then IIUC the DW_EDMA_CHIP_32BIT_DBI flag doesn't
exist on the following based patches:
https://patchwork.kernel.org/project/linux-pci/cover/20220624143947.8991-1-Sergey.Semin@baikalelectronics.ru/
https://patchwork.kernel.org/project/linux-dmaengine/cover/20220524152159.2370739-1-Frank.Li@nxp.com/
According to the comment from Zhi Li [1], the flag can be skipped by the fixed patch [2].
That's why the flag doesn't exist on the based patches.
[1]
https://patchwork.kernel.org/project/linux-dmaengine/patch/20220503005801.1714345-9-Frank.Li@nxp.com/#24844332
[2]
https://git.kernel.org/pub/scm/linux/kernel/git/vkoul/dmaengine.git/commit/?h=fixes&id=8fc5133d6d4da65cad6b73152fc714ad3d7f91c1
Since both codes in #ifdef and #else are the same, we can just remove code of the #else part.
But, what do you think?
-----
#ifdef CONFIG_64BIT
/* llp is not aligned on 64bit -> keep 32bit accesses */
SET_CH_32(dw, chan->dir, chan->id, llp.lsb,
lower_32_bits(chunk->ll_region.paddr));
SET_CH_32(dw, chan->dir, chan->id, llp.msb,
upper_32_bits(chunk->ll_region.paddr));
#else /* CONFIG_64BIT */
SET_CH_32(dw, chan->dir, chan->id, llp.lsb,
lower_32_bits(chunk->ll_region.paddr));
SET_CH_32(dw, chan->dir, chan->id, llp.msb,
upper_32_bits(chunk->ll_region.paddr));
#endif /* CONFIG_64BIT */
-----
Best regards,
Yoshihiro Shimoda
> - !IS_ENABLED(CONFIG_64BIT)) {
> - SET_CH_32(dw, chan->dir, chan->id, llp.lsb,
> - lower_32_bits(chunk->ll_region.paddr));
> - SET_CH_32(dw, chan->dir, chan->id, llp.msb,
> - upper_32_bits(chunk->ll_region.paddr));
> - } else {
> - #ifdef CONFIG_64BIT
> - SET_CH_64(dw, chan->dir, chan->id, llp.reg,
> - chunk->ll_region.paddr);
> - #endif
> - }
> + SET_CH_64(dw, chan->dir, chan->id, llp.reg,
> + chunk->ll_region.paddr);
> }
> /* Doorbell */
> SET_RW_32(dw, chan->dir, doorbell,
> --
> 2.35.1
next prev parent reply other threads:[~2022-07-06 5:42 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 9:14 [PATCH v3 00/24] dmaengine: dw-edma: Add RP/EP local DMA controllers support Serge Semin
2022-06-10 9:14 ` [PATCH v3 01/24] dmaengine: Fix dma_slave_config.dst_addr description Serge Semin
2022-06-10 9:14 ` [PATCH v3 02/24] dmaengine: dw-edma: Release requested IRQs on failure Serge Semin
2022-06-10 9:14 ` [PATCH v3 03/24] dmaengine: dw-edma: Convert ll/dt phys-address to PCIe bus/DMA address Serge Semin
2022-06-10 9:14 ` [PATCH v3 04/24] dmaengine: dw-edma: Fix missing src/dst address of the interleaved xfers Serge Semin
2022-06-10 9:14 ` [PATCH v3 05/24] dmaengine: dw-edma: Don't permit non-inc " Serge Semin
2022-06-10 9:14 ` [PATCH v3 06/24] dmaengine: dw-edma: Fix invalid interleaved xfers semantics Serge Semin
2022-06-10 9:14 ` [PATCH v3 07/24] dmaengine: dw-edma: Add CPU to PCIe bus address translation Serge Semin
2022-06-10 9:14 ` [PATCH v3 08/24] dmaengine: dw-edma: Add PCIe bus address getter to the remote EP glue-driver Serge Semin
2022-06-10 9:14 ` [PATCH v3 09/24] dmaengine: dw-edma: Drop chancnt initialization Serge Semin
2022-06-10 9:14 ` [PATCH v3 10/24] dmaengine: dw-edma: Fix DebugFS reg entry type Serge Semin
2022-06-10 9:14 ` [PATCH v3 11/24] dmaengine: dw-edma: Stop checking debugfs_create_*() return value Serge Semin
2022-06-10 9:14 ` [PATCH v3 12/24] dmaengine: dw-edma: Add dw_edma prefix to the DebugFS nodes descriptor Serge Semin
2022-06-10 9:14 ` [PATCH v3 13/24] dmaengine: dw-edma: Convert DebugFS descs to being kz-allocated Serge Semin
2022-06-10 9:14 ` [PATCH v3 14/24] dmaengine: dw-edma: Rename DebugFS dentry variables to 'dent' Serge Semin
2022-06-10 9:14 ` [PATCH v3 15/24] dmaengine: dw-edma: Simplify the DebugFS context CSRs init procedure Serge Semin
2022-06-10 9:14 ` [PATCH v3 16/24] dmaengine: dw-edma: Move eDMA data pointer to DebugFS node descriptor Serge Semin
2022-06-10 9:14 ` [PATCH v3 17/24] dmaengine: dw-edma: Join Write/Read channels into a single device Serge Semin
2022-06-10 9:14 ` [PATCH v3 18/24] dmaengine: dw-edma: Use DMA-engine device DebugFS subdirectory Serge Semin
2022-06-10 9:14 ` [PATCH v3 19/24] dmaengine: dw-edma: Use non-atomic io-64 methods Serge Semin
2022-07-06 5:42 ` Yoshihiro Shimoda [this message]
2022-07-06 14:28 ` [EXT] " Frank Li
2022-07-07 0:35 ` Yoshihiro Shimoda
2022-06-10 9:14 ` [PATCH v3 20/24] dmaengine: dw-edma: Drop DT-region allocation Serge Semin
2022-06-10 9:14 ` [PATCH v3 21/24] dmaengine: dw-edma: Replace chip ID number with device name Serge Semin
2022-06-10 9:14 ` [PATCH v3 22/24] dmaengine: dw-edma: Bypass dma-ranges mapping for the local setup Serge Semin
2022-07-09 8:31 ` Manivannan Sadhasivam
2022-06-10 9:14 ` [PATCH v3 23/24] dmaengine: dw-edma: Skip cleanup procedure if no private data found Serge Semin
2022-06-10 9:14 ` [PATCH v3 24/24] PCI: dwc: Add DW eDMA engine support Serge Semin
2022-07-09 8:36 ` Manivannan Sadhasivam
2022-06-10 9:21 ` [PATCH v3 00/24] dmaengine: dw-edma: Add RP/EP local DMA controllers support Serge Semin
2022-07-11 14:45 ` Manivannan Sadhasivam
2022-07-11 14:49 ` Manivannan Sadhasivam
2022-07-11 15:39 ` Serge Semin
2022-07-21 12:16 ` Vinod Koul
2022-07-28 11:33 ` Serge Semin
2022-07-28 12:48 ` Vinod Koul
2022-07-28 14:17 ` 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=TYBPR01MB53418C1BC8791CB6D068A177D8809@TYBPR01MB5341.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=Alexey.Malahov@baikalelectronics.ru \
--cc=Frank.Li@nxp.com \
--cc=Pavel.Parkhomenko@baikalelectronics.ru \
--cc=Sergey.Semin@baikalelectronics.ru \
--cc=bhelgaas@google.com \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=jingoohan1@gmail.com \
--cc=kw@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=manivannan.sadhasivam@linaro.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;
as well as URLs for NNTP newsgroup(s).