public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Thomas Chou <thomas@wytron.com.tw>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v3] nios2 : convert altera_pio to driver model
Date: Thu, 1 Oct 2015 08:38:30 +0800	[thread overview]
Message-ID: <560C8086.7010305@wytron.com.tw> (raw)
In-Reply-To: <CAPnjgZ1unQq0Szc+Y8MCwd9LKvqsqr_vLobiR_xk75UxgS9VVA@mail.gmail.com>

Hi Simon,

On 10/01/2015 02:29 AM, Simon Glass wrote:
> Do we need the ioremap() or can we rely on the 'ranges' handling?

Yes, we do need ioremap() at least for mips, nios2 and alike. For these 
archs, the virtual address that CPU sees is not the same as physical 
address on bus. The virtual address space of these CPus are divided to 
cached kernel space, uncached kernel space, and managed user space. For 
main memory, we would use cached kernel space to run u-boot. While for 
peripheral access, we would use uncached kernel space. The device tree 
describes hardware, and the reg address have to be physical address. We 
need to map the reg address to uncached kernel virtual address. This is 
what ioremap() for. It is not related to ranges translation. Though we 
do need the range translation patch from Stefan as there might be 
bridges between the buses.

Thanks a lot for your review.

Best regards,
Thomas Chou

  reply	other threads:[~2015-10-01  0:38 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24  9:15 [U-Boot] [PATCH] nios2 : convert altera_pio to driver model Thomas Chou
2015-09-24 18:04 ` Marek Vasut
2015-09-25  8:05 ` [U-Boot] [PATCH v2] " Thomas Chou
2015-09-26  9:07 ` [U-Boot] [PATCH v3] " Thomas Chou
2015-09-30  1:18   ` Chin Liang See
2015-09-30 18:29   ` Simon Glass
2015-10-01  0:38     ` Thomas Chou [this message]
2015-09-30 13:37 ` [U-Boot] [PATCH v4] " Thomas Chou
2015-10-03 13:10   ` Thomas Chou

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=560C8086.7010305@wytron.com.tw \
    --to=thomas@wytron.com.tw \
    --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