From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] imx21ads : Fix overlapping static i/o mappings
Date: Wed, 9 May 2012 09:29:39 +0200 [thread overview]
Message-ID: <20120509072939.GI27341@pengutronix.de> (raw)
In-Reply-To: <1335779623-30383-1-git-send-email-jaccon.bastiaansen@gmail.com>
On Mon, Apr 30, 2012 at 11:53:43AM +0200, Jaccon Bastiaansen wrote:
> The statically defined I/O memory regions for the i.MX21 on chip
> peripherals and the on board I/O peripherals of the i.MX21ADS board
> overlap. This results in a kernel crash during startup. This is fixed
> by reducing the memory range for the on board I/O peripherals to the
> actually required range.
>
> Signed-off-by: Jaccon Bastiaansen <jaccon.bastiaansen@gmail.com>
Applied, thanks. Please add a ARM i.MX prefix next time to you subject.
Also, added a Cc stable.
Sascha
> ---
> arch/arm/mach-imx/mach-mx21ads.c | 2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-imx/mach-mx21ads.c b/arch/arm/mach-imx/mach-mx21ads.c
> index e432d4a..4460d25 100644
> --- a/arch/arm/mach-imx/mach-mx21ads.c
> +++ b/arch/arm/mach-imx/mach-mx21ads.c
> @@ -32,7 +32,7 @@
> * Memory-mapped I/O on MX21ADS base board
> */
> #define MX21ADS_MMIO_BASE_ADDR 0xf5000000
> -#define MX21ADS_MMIO_SIZE SZ_16M
> +#define MX21ADS_MMIO_SIZE 0xc00000
>
> #define MX21ADS_REG_ADDR(offset) (void __force __iomem *) \
> (MX21ADS_MMIO_BASE_ADDR + (offset))
> --
> 1.7.1
>
>
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2012-05-09 7:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 9:53 [PATCH] imx21ads : Fix overlapping static i/o mappings Jaccon Bastiaansen
2012-05-09 7:29 ` Sascha Hauer [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=20120509072939.GI27341@pengutronix.de \
--to=s.hauer@pengutronix.de \
--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).