From: Paul Cercueil <paul@crapouillou.net>
To: Siarhei Volkau <lis8215@gmail.com>
Cc: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mips@vger.kernel.org
Subject: Re: [PATCH v3 2/2] dmaengine: JZ4780: Add support for the JZ4755.
Date: Tue, 18 Oct 2022 22:02:37 +0100 [thread overview]
Message-ID: <DSVYJR.6R2II2D52YQ5@crapouillou.net> (raw)
In-Reply-To: <20221018181219.3251309-3-lis8215@gmail.com>
Hi Siarhei,
Le mar., oct. 18 2022 at 21:12:19 +0300, Siarhei Volkau
<lis8215@gmail.com> a écrit :
> The JZ4755 has 4 DMA channels per DMA unit, two idential DMA units.
>
> The JZ4755 has the similar DMA engine to JZ4725b and it has the
> same bug as JZ4725b, see commit a40c94be2336.
> At least the JZ_SOC_DATA_BREAK_LINKS flag make it work much better,
> although not ideal.
>
> Tested-by: Siarhei Volkau <lis8215@gmail.com>
> Signed-off-by: Siarhei Volkau <lis8215@gmail.com>
You forgot my tag that I added on your V2.
Reviewed-by: Paul Cercueil <paul@crapouillou.net>
Cheers,
-Paul
> ---
> drivers/dma/dma-jz4780.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/dma/dma-jz4780.c b/drivers/dma/dma-jz4780.c
> index 2a483802d..9c1a6e9a9 100644
> --- a/drivers/dma/dma-jz4780.c
> +++ b/drivers/dma/dma-jz4780.c
> @@ -1038,6 +1038,13 @@ static const struct jz4780_dma_soc_data
> jz4725b_dma_soc_data = {
> JZ_SOC_DATA_BREAK_LINKS,
> };
>
> +static const struct jz4780_dma_soc_data jz4755_dma_soc_data = {
> + .nb_channels = 4,
> + .transfer_ord_max = 5,
> + .flags = JZ_SOC_DATA_PER_CHAN_PM | JZ_SOC_DATA_NO_DCKES_DCKEC |
> + JZ_SOC_DATA_BREAK_LINKS,
> +};
> +
> static const struct jz4780_dma_soc_data jz4760_dma_soc_data = {
> .nb_channels = 5,
> .transfer_ord_max = 6,
> @@ -1101,6 +1108,7 @@ static const struct jz4780_dma_soc_data
> x1830_dma_soc_data = {
> static const struct of_device_id jz4780_dma_dt_match[] = {
> { .compatible = "ingenic,jz4740-dma", .data = &jz4740_dma_soc_data
> },
> { .compatible = "ingenic,jz4725b-dma", .data =
> &jz4725b_dma_soc_data },
> + { .compatible = "ingenic,jz4755-dma", .data = &jz4755_dma_soc_data
> },
> { .compatible = "ingenic,jz4760-dma", .data = &jz4760_dma_soc_data
> },
> { .compatible = "ingenic,jz4760-mdma", .data =
> &jz4760_mdma_soc_data },
> { .compatible = "ingenic,jz4760-bdma", .data =
> &jz4760_bdma_soc_data },
> --
> 2.36.1
>
next prev parent reply other threads:[~2022-10-18 21:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 18:12 [PATCH v3 0/2] Add Ingenic JZ4755 DMA support Siarhei Volkau
2022-10-18 18:12 ` [PATCH v3 1/2] dt-bindings: ingenic: Add support for the JZ4755 dmaengine Siarhei Volkau
2022-10-18 18:12 ` [PATCH v3 2/2] dmaengine: JZ4780: Add support for the JZ4755 Siarhei Volkau
2022-10-18 21:02 ` Paul Cercueil [this message]
2022-10-19 13:43 ` [PATCH v3 0/2] Add Ingenic JZ4755 DMA support Vinod Koul
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=DSVYJR.6R2II2D52YQ5@crapouillou.net \
--to=paul@crapouillou.net \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=lis8215@gmail.com \
--cc=robh+dt@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