linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mindentropy@gmail.com (mind entropy)
To: linux-arm-kernel@lists.infradead.org
Subject: On mini2440 IO mappings.
Date: Wed, 5 Jun 2013 12:52:32 +0530	[thread overview]
Message-ID: <CAM2a4uxAs31ba7q9UaYTKJJLvRGeFw3TmE36vbGZYbC0j1OWEA@mail.gmail.com> (raw)
In-Reply-To: <5390072.c6vttxqWyK@wuerfel>

> I don't think it does. The mappings are
>
> static struct map_desc s3c_iodesc[] __initdata = {
>         IODESC_ENT(GPIO),
>         IODESC_ENT(IRQ),
>         IODESC_ENT(MEMCTRL),
>         IODESC_ENT(UART)
> };
>
> using these virtual addresses:
>
> #define S3C_ADDR_BASE   0xF6000000
> #define S3C_ADDR(x)     ((void __iomem __force *)S3C_ADDR_BASE + (x))
> #define S3C_VA_IRQ      S3C_ADDR(0x00000000)    /* irq controller(s) */
> #define S3C_VA_SYS      S3C_ADDR(0x00100000)    /* system control */
> #define S3C_VA_MEM      S3C_ADDR(0x00200000)    /* memory control */
> #define S3C_VA_UART     S3C_ADDR(0x01000000)    /* UART */
> #define S3C24XX_VA_GPIO   ((S3C24XX_PA_GPIO - S3C24XX_PA_UART) + S3C24XX_VA_UART)
>
> and these physical addresses
>
> #define S3C2410_PA_UART         (0x50000000)
> #define S3C2410_PA_GPIO         (0x56000000)
> #define S3C2410_PA_IRQ          (0x4A000000)
> #define S3C2410_PA_MEMCTRL      (0x48000000)
>
> Everything is aligned to full megabytes.

You are right. Sorry I misread the virtual addresses. Now in this
scheme would there be unused holes in the virtual address space (For
eg. IRQ address space is not 1 MB big)?

-Gautam

      reply	other threads:[~2013-06-05  7:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-04  7:41 On mini2440 IO mappings mind entropy
2013-06-04  8:52 ` Arnd Bergmann
2013-06-04  9:29   ` mind entropy
2013-06-04  9:47     ` Arnd Bergmann
2013-06-05  7:22       ` mind entropy [this message]

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=CAM2a4uxAs31ba7q9UaYTKJJLvRGeFw3TmE36vbGZYbC0j1OWEA@mail.gmail.com \
    --to=mindentropy@gmail.com \
    --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).