public inbox for linux-sh@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh: pass through ioremap() for non-mmu processors
Date: Tue, 28 Apr 2009 08:49:03 +0000	[thread overview]
Message-ID: <20090428084903.GB15695@linux-sh.org> (raw)
In-Reply-To: <20090428075934.16285.38017.sendpatchset@rx1.opensource.se>

On Tue, Apr 28, 2009 at 04:59:34PM +0900, Magnus Damm wrote:
> From: Magnus Damm <damm@igel.co.jp>
> 
> This patch modifies the ioremap() handling for CONFIG_MMU=n.
> 
> All 32-bit SuperH processors currently go through __ioremap_mode()
> and check for IO_TRAPPED and directly mapped segments. With this
> patch we simplify the MMU less case with a pass through version of
>  __ioremap_mode() which just returns the physical address.
> 
> The effects of this is change are:
>  - fix non-MMU ioremap() of high address hardware blocks (sh7203 CMT)
>  - IO_TRAPPED is never checked for
> 
> Signed-off-by: Magnus Damm <damm@igel.co.jp>
> ---
> 
>  arch/sh/Kconfig          |    1 +
>  arch/sh/include/asm/io.h |   13 +++++++------
>  2 files changed, 8 insertions(+), 6 deletions(-)
> 
> --- 0001/arch/sh/Kconfig
> +++ work/arch/sh/Kconfig	2009-04-21 15:54:59.000000000 +0900
> @@ -136,6 +136,7 @@ config ARCH_HAS_DEFAULT_IDLE
>  
>  config IO_TRAPPED
>  	bool
> +	depends on MMU
>  
You have failed at Kconfig. select trumps depends, so this has no impact
for platforms that select IO_TRAPPED. You will have to switch the
platforms that select this over to handling the dependency properly on
their own.

  reply	other threads:[~2009-04-28  8:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-28  7:59 [PATCH] sh: pass through ioremap() for non-mmu processors Magnus Damm
2009-04-28  8:49 ` Paul Mundt [this message]
2009-04-29 14:44 ` [PATCH] sh: pass through ioremap() for non-mmu processors V2 Magnus Damm
2009-04-30  3:53 ` Paul Mundt

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=20090428084903.GB15695@linux-sh.org \
    --to=lethal@linux-sh.org \
    --cc=linux-sh@vger.kernel.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