From: Rask Ingemann Lambertsen <rask@formelder.dk>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/9] dm: allow 4GB of DRAM on 32bit systems
Date: Sat, 19 Jan 2019 16:21:07 +0100 [thread overview]
Message-ID: <20190119152107.GB2281@localhost> (raw)
In-Reply-To: <d02acab5-4d42-8e8a-e70d-c9f542b8b360@ti.com>
On 03-09-2018 at 19:59 +0530, Lokesh Vutla wrote:
>
> On Sunday 02 September 2018 11:19 PM, Alexander Graf wrote:
> >
> >> Am 02.09.2018 um 18:04 schrieb Vagrant Cascadian <vagrant@debian.org>:
> >>
> >>> With LPAE available in all modern ARM cores, shouldn't phys_addr_t just
> >>> be u64? And then we'd probably want to use that throughout the code, right?
> >>
> >> Quite a few currently supported boards do not support LPAE, e.g. imx6.
> >
> > What I'm trying to say is that we probably want to make phys_addr_t be u64 when CONFIG_LPAE is set.
>
> That's right. Enabling PHYS_64BIT should be sufficient. Based on this
> phys_addr_t should be set to u32 or u64. arm already does that[1].
That will cause warnings from at least two sunxi drivers. I forgot which one
the other was, but sunxi_mmc is one of them:
$ git grep -F -e '(u32 *)' drivers/mmc/sunxi_mmc.c
drivers/mmc/sunxi_mmc.c: ccu_reg = (u32 *)ofnode_get_addr(args.node);
drivers/mmc/sunxi_mmc.c: mmc_config_clk = (u32 *)ofnode_get_addr(args.node);
becase ofnode_get_addr() is declared like so:
include/dm/ofnode.h:phys_addr_t ofnode_get_addr(ofnode node);
--
Best regards,
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2019-01-19 15:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-26 13:59 [U-Boot] [PATCH 0/9] Support 4GB of memory on 32bit systems Philipp Tomsich
2018-07-26 13:59 ` [U-Boot] [PATCH 1/9] dm: allow 4GB of DRAM " Philipp Tomsich
2018-08-02 20:36 ` Simon Glass
2018-08-02 21:31 ` Dr. Philipp Tomsich
2018-09-02 11:10 ` Alexander Graf
2018-09-02 16:04 ` Vagrant Cascadian
2018-09-02 17:49 ` Alexander Graf
2018-09-03 14:29 ` Lokesh Vutla
2018-09-14 10:53 ` Simon Glass
2018-09-14 11:03 ` Philipp Tomsich
2019-01-19 15:21 ` Rask Ingemann Lambertsen [this message]
2018-07-26 13:59 ` [U-Boot] [PATCH 2/9] rockchip: support 4GB " Philipp Tomsich
2018-07-26 20:05 ` Carlo Caione
2018-07-26 20:08 ` Dr. Philipp Tomsich
2018-07-26 20:09 ` Dr. Philipp Tomsich
2018-07-26 22:54 ` Dr. Philipp Tomsich
2018-07-27 7:50 ` Carlo Caione
2018-07-27 9:12 ` Dr. Philipp Tomsich
2018-07-26 13:59 ` [U-Boot] [PATCH 3/9] common: include <inttypes.h> always Philipp Tomsich
2018-07-31 1:41 ` Masahiro Yamada
2018-08-02 16:56 ` Simon Glass
2018-08-03 15:01 ` Tom Rini
2018-08-06 2:54 ` Masahiro Yamada
2018-08-02 8:46 ` Patrick DELAUNAY
2018-07-26 13:59 ` [U-Boot] [PATCH 4/9] MIPS: use PRIx64 macros for printing ram size Philipp Tomsich
2018-08-02 20:36 ` Simon Glass
2018-08-07 14:41 ` Daniel Schwierzeck
2018-07-26 13:59 ` [U-Boot] [PATCH 5/9] rockchip: rk3368: change type of ram-size field for a min()-calculation Philipp Tomsich
2018-08-02 20:36 ` Simon Glass
2018-07-26 13:59 ` [U-Boot] [PATCH 6/9] ram: stm32mp1: use PRIx64 macros for printing ram size Philipp Tomsich
2018-08-02 8:52 ` Patrick DELAUNAY
2018-08-02 16:56 ` Simon Glass
2018-07-26 13:59 ` [U-Boot] [PATCH 7/9] board: keymile: add explicit cast to truncate the 64bit ram size field Philipp Tomsich
2018-08-02 20:36 ` Simon Glass
2018-07-26 13:59 ` [U-Boot] [PATCH 8/9] board: cm_fx6: use PRIx64 macros for printing ram size Philipp Tomsich
2018-07-31 1:42 ` Masahiro Yamada
2018-08-02 20:36 ` Simon Glass
2018-07-26 13:59 ` [U-Boot] [PATCH 9/9] mpc85xx: add casts for ram size in min() calculation Philipp Tomsich
2018-07-26 16:12 ` York Sun
2018-08-11 1:44 ` [U-Boot] [PATCH 0/9] Support 4GB of memory on 32bit systems Tom Rini
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=20190119152107.GB2281@localhost \
--to=rask@formelder.dk \
--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