From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] dmaengine: fsl-edma: fixup reg offset and hw S/G support in big-endian model
Date: Tue, 23 Sep 2014 14:30:30 +0200 [thread overview]
Message-ID: <45444544.Xl4NeUiTm0@wuerfel> (raw)
In-Reply-To: <1411463719-7728-1-git-send-email-jingchang.lu@freescale.com>
On Tuesday 23 September 2014 17:15:19 Jingchang Lu wrote:
> @@ -459,20 +480,27 @@ static void fill_tcd_params(struct fsl_edma_engine *edma,
> u16 csr = 0;
>
> /*
> - * eDMA hardware SGs require the TCD parameters stored in memory
> - * the same endian as the eDMA module so that they can be loaded
> - * automatically by the engine
> + * eDMA hardware SGs requires the TCDs to be auto loaded
> + * in the same endian as the core whenver the eDAM engine's
> + * register endian. So we don't swap the value, waitting
> + * for fsl_set_tcd_params doing the swap.
> */
This makes no sense: how would the eDMA hardware know what endianess
the CPU is using to write this data? Have you tried this running on
the same hardware with both big-endian and little-endian kernels?
Also, you access this as little-endian data unconditionally rather
than cpu-endian as the comment suggests, maybe that is what you meant
here?
> - edma_writel(edma, src, &(tcd->saddr));
> - edma_writel(edma, dst, &(tcd->daddr));
> - edma_writew(edma, attr, &(tcd->attr));
> - edma_writew(edma, EDMA_TCD_SOFF_SOFF(soff), &(tcd->soff));
> - edma_writel(edma, EDMA_TCD_NBYTES_NBYTES(nbytes), &(tcd->nbytes));
> - edma_writel(edma, EDMA_TCD_SLAST_SLAST(slast), &(tcd->slast));
> - edma_writew(edma, EDMA_TCD_CITER_CITER(citer), &(tcd->citer));
> - edma_writew(edma, EDMA_TCD_DOFF_DOFF(doff), &(tcd->doff));
> - edma_writel(edma, EDMA_TCD_DLAST_SGA_DLAST_SGA(dlast_sga), &(tcd->dlast_sga));
> - edma_writew(edma, EDMA_TCD_BITER_BITER(biter), &(tcd->biter));
> + writel(src, &(tcd->saddr));
> + writel(dst, &(tcd->daddr));
> +
> + writew(attr, &(tcd->attr));
You seem to have another preexisting bug: The tcd pointer actually does not
point to mmio registers here at all, but instead points to memory that
has been returned from dma_pool_alloc. It is not valid to use writel()
on such memory, that is only meant to work on real MMIO registers.
You should use regular assignments to the registers here, e.g.
tcd->saddr = cpu_to_le32(src);
tcd->daddr = cpu_to_le32(dst);
...
Arnd
next prev parent reply other threads:[~2014-09-23 12:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-23 9:15 [PATCH] dmaengine: fsl-edma: fixup reg offset and hw S/G support in big-endian model Jingchang Lu
2014-09-23 10:37 ` Russell King - ARM Linux
2014-09-23 17:21 ` Jingchang Lu
2014-09-23 12:30 ` Arnd Bergmann [this message]
2014-09-23 17:18 ` Jingchang Lu
2014-09-23 18:23 ` Arnd Bergmann
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=45444544.Xl4NeUiTm0@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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).