public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Aneesh Bansal <aneesh.bansal@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3][v2] Data types defined for 64 bit physical address
Date: Mon, 24 Aug 2015 14:44:48 +0530	[thread overview]
Message-ID: <1440407689-12856-2-git-send-email-aneesh.bansal@freescale.com> (raw)
In-Reply-To: <1440407689-12856-1-git-send-email-aneesh.bansal@freescale.com>

Data types and I/O functions have been defined for
64 bit physical addresses in arm.

Signed-off-by: Aneesh Bansal <aneesh.bansal@freescale.com>
---
Changes in v2:
There is no need for defining 64 bit I/O operations.
If an IP needs to do 64 bit access, it will do it by defining
32 bit addr_hi and addr_lo.

 arch/arm/include/asm/types.h | 13 ++++++++-----
 1 file changed, 8 insertions(+), 5 deletions(-)

diff --git a/arch/arm/include/asm/types.h b/arch/arm/include/asm/types.h
index ee77c41..d87f955 100644
--- a/arch/arm/include/asm/types.h
+++ b/arch/arm/include/asm/types.h
@@ -45,12 +45,15 @@ typedef unsigned long long u64;
 #define BITS_PER_LONG 32
 #endif	/* CONFIG_ARM64 */
 
-/* Dma addresses are 32-bits wide.  */
-
+#ifdef CONFIG_PHYS_64BIT
+typedef u64 dma_addr_t;
+typedef u64 phys_addr_t;
+typedef u64 phys_size_t;
+#else
 typedef u32 dma_addr_t;
-
-typedef unsigned long phys_addr_t;
-typedef unsigned long phys_size_t;
+typedef u32 phys_addr_t;
+typedef u32 phys_size_t;
+#endif
 
 #endif /* __KERNEL__ */
 
-- 
1.8.1.4

  reply	other threads:[~2015-08-24  9:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-24  9:14 [U-Boot] [PATCH 1/3][v2] Pointers in ESBC header made 32 bit Aneesh Bansal
2015-08-24  9:14 ` Aneesh Bansal [this message]
2015-08-24  9:14 ` [U-Boot] [PATCH 3/3][v2] crypto/fsl: SEC driver cleanup for 64 bit and endianness Aneesh Bansal

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=1440407689-12856-2-git-send-email-aneesh.bansal@freescale.com \
    --to=aneesh.bansal@freescale.com \
    --cc=u-boot@lists.denx.de \
    /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