* [PATCH] dma: at_hdmac: use __le32 for dma addresses
@ 2015-03-26 18:02 Ben Dooks
2015-04-02 7:43 ` Vinod Koul
0 siblings, 1 reply; 2+ messages in thread
From: Ben Dooks @ 2015-03-26 18:02 UTC (permalink / raw)
To: linux-arm-kernel
The at_dmac uses a lli structure with a mix of dma_addr_t and
__le32 in it. As Russell King pointed out, dma_addr_t could be
a non 32-bit size depending on the kernel configuration. Change
all references of this to __le32 to better match the hardware
representation.
Note, this does nothing to fix the discussion of dma vs physical
addresses also brought up during these discussions.
This patch depends on the __le32 descriptor updates posted
previously.
Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
--
CC: Russell King <linux@arm.linux.org.uk>
CC: Nicolas Ferre <nicolas.ferre@atmel.com>
CC: Dan Williams <dan.j.williams@intel.com>
CC: Vinod Koul <vinod.koul@intel.com>
CC: linux-arm-kernel at lists.infradead.org
CC: dmaengine at vger.kernel.org
---
drivers/dma/at_hdmac_regs.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/at_hdmac_regs.h b/drivers/dma/at_hdmac_regs.h
index bd4d174..b246beb 100644
--- a/drivers/dma/at_hdmac_regs.h
+++ b/drivers/dma/at_hdmac_regs.h
@@ -167,13 +167,13 @@
/* LLI == Linked List Item; aka DMA buffer descriptor */
struct at_lli {
/* values that are not changed by hardware */
- dma_addr_t saddr;
- dma_addr_t daddr;
+ __le32 saddr;
+ __le32 daddr;
/* value that may get written back: */
__le32 ctrla;
/* more values that are not changed by hardware */
__le32 ctrlb;
- dma_addr_t dscr; /* chain to next lli */
+ __le32 dscr; /* chain to next lli */
};
/**
--
2.1.4
^ permalink raw reply related [flat|nested] 2+ messages in thread
* [PATCH] dma: at_hdmac: use __le32 for dma addresses
2015-03-26 18:02 [PATCH] dma: at_hdmac: use __le32 for dma addresses Ben Dooks
@ 2015-04-02 7:43 ` Vinod Koul
0 siblings, 0 replies; 2+ messages in thread
From: Vinod Koul @ 2015-04-02 7:43 UTC (permalink / raw)
To: linux-arm-kernel
On Thu, Mar 26, 2015 at 06:02:09PM +0000, Ben Dooks wrote:
> The at_dmac uses a lli structure with a mix of dma_addr_t and
> __le32 in it. As Russell King pointed out, dma_addr_t could be
> a non 32-bit size depending on the kernel configuration. Change
> all references of this to __le32 to better match the hardware
> representation.
>
> Note, this does nothing to fix the discussion of dma vs physical
> addresses also brought up during these discussions.
>
> This patch depends on the __le32 descriptor updates posted
> previously.
Can you please repost the whole series along with dependecies...
--
~Vinod
>
> Signed-off-by: Ben Dooks <ben.dooks@codethink.co.uk>
> --
> CC: Russell King <linux@arm.linux.org.uk>
> CC: Nicolas Ferre <nicolas.ferre@atmel.com>
> CC: Dan Williams <dan.j.williams@intel.com>
> CC: Vinod Koul <vinod.koul@intel.com>
> CC: linux-arm-kernel at lists.infradead.org
> CC: dmaengine at vger.kernel.org
> ---
> drivers/dma/at_hdmac_regs.h | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/dma/at_hdmac_regs.h b/drivers/dma/at_hdmac_regs.h
> index bd4d174..b246beb 100644
> --- a/drivers/dma/at_hdmac_regs.h
> +++ b/drivers/dma/at_hdmac_regs.h
> @@ -167,13 +167,13 @@
> /* LLI == Linked List Item; aka DMA buffer descriptor */
> struct at_lli {
> /* values that are not changed by hardware */
> - dma_addr_t saddr;
> - dma_addr_t daddr;
> + __le32 saddr;
> + __le32 daddr;
> /* value that may get written back: */
> __le32 ctrla;
> /* more values that are not changed by hardware */
> __le32 ctrlb;
> - dma_addr_t dscr; /* chain to next lli */
> + __le32 dscr; /* chain to next lli */
> };
>
> /**
> --
> 2.1.4
>
--
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2015-04-02 7:43 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-03-26 18:02 [PATCH] dma: at_hdmac: use __le32 for dma addresses Ben Dooks
2015-04-02 7:43 ` Vinod Koul
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).