public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: alex@digriz•org.uk (Alexander Clouter)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH] TS-78xxx NAND resource type should be IORESOURCE_MEM
Date: Fri, 5 Nov 2010 20:28:34 +0000	[thread overview]
Message-ID: <i06eq7-6va.ln1@chipmunk.wormnet.eu> (raw)
In-Reply-To: 1288977280-5674-1-git-send-email-mspang@csclub.uwaterloo.ca

In gmane.linux.kernel Michael Spang <mspang@csclub•uwaterloo.ca> wrote:
>
> The type was IORESOURCE_IO which is not what is expected by
> plat_nand_probe(). This device has not worked since 2d098a72
> ("mtd: plat_nand: request memory resource before doing ioremap").
> 
> Signed-off-by: Michael Spang <mspang@csclub•uwaterloo.ca>
>
Acked-by: Alexander Clouter <alex@digriz•org.uk>

Cheers

> ---
> arch/arm/mach-orion5x/ts78xx-setup.c |    2 +-
> 1 files changed, 1 insertions(+), 1 deletions(-)
> 
> diff --git a/arch/arm/mach-orion5x/ts78xx-setup.c b/arch/arm/mach-orion5x/ts78xx-setup.c
> index 16f1bd5..c1c1cd0 100644
> --- a/arch/arm/mach-orion5x/ts78xx-setup.c
> +++ b/arch/arm/mach-orion5x/ts78xx-setup.c
> @@ -239,7 +239,7 @@ static struct platform_nand_data ts78xx_ts_nand_data = {
> static struct resource ts78xx_ts_nand_resources = {
>        .start          = TS_NAND_DATA,
>        .end            = TS_NAND_DATA + 4,
> -       .flags          = IORESOURCE_IO,
> +       .flags          = IORESOURCE_MEM,
> };
> 
> static struct platform_device ts78xx_ts_nand_device = {
> -- 
> 1.7.1

-- 
Alexander Clouter
.sigmonster says: 98% lean.

      reply	other threads:[~2010-11-05 20:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-05 17:14 [PATCH] TS-78xxx NAND resource type should be IORESOURCE_MEM Michael Spang
2010-11-05 20:28 ` Alexander Clouter [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=i06eq7-6va.ln1@chipmunk.wormnet.eu \
    --to=alex@digriz$(echo .)org.uk \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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