All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Roese <ml@stefan-roese.de>
To: Sergei Shtylyov <sshtylyov@ru.mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] [MTD] physmap: Add support for 64 bit resources on PPC44x
Date: Thu, 18 Jan 2007 18:46:03 +0100 (MET)	[thread overview]
Message-ID: <200701181846.21776.ml@stefan-roese.de> (raw)
In-Reply-To: <45AFAD41.4030801@ru.mvista.com>

Hi Sergei,

On Thursday 18 January 2007 18:24, Sergei Shtylyov wrote:
> > This patch adds support for 64 bit resources and can be used on
> > PPC440 platforms to pass the complete 64 bit address from the
> > platform file to the physmap driver. This is first used on the
> > AMCC Taishan 440GX evaluation board.
>
>     Is this board support in arch/ppc/ or arch/powerpc/?

Not yet in the kernel.org repository. It's right now in the denx repository 
but I plan to sent the board support patches to the lists, even if I know, 
that it most likely won't get included right now, because of the ppc->powerpc 
merge.

And yes, it's still an "arch->ppc" port.

> > Signed-off-by: Stefan Roese <sr@denx.de>
> >
> > ---
> > commit 428858620a600f991662969be6d6b3e3720da1ac
> > tree cf3c861fbdddd841401a1e66f441623f0b3fb83c
> > parent d637c5644df789f15dfe06550fab1dddb87083ca
> > author Stefan Roese <sr@denx.de> Thu, 18 Jan 2007 14:40:53 +0100
> > committer Stefan Roese <sr@denx.de> Thu, 18 Jan 2007 14:40:53 +0100
> >
> >  drivers/mtd/maps/physmap.c |    7 +++++++
> >  1 files changed, 7 insertions(+), 0 deletions(-)
> >
> > diff --git a/drivers/mtd/maps/physmap.c b/drivers/mtd/maps/physmap.c
> > index d171776..23072e3 100644
> > --- a/drivers/mtd/maps/physmap.c
> > +++ b/drivers/mtd/maps/physmap.c
> > @@ -116,7 +116,14 @@ static int physmap_flash_probe(struct
> > platform_device *dev)
>
>     And what do you assign to info->map.phys, a meaninglessly truncated
> 64-bit address?
>     I think that 'phys' field's type should be changed to a more
> appropriate one, like resource_size_t, instead...

Yes, this makes sense.

> >  	info->map.bankwidth = physmap_data->width;
> >  	info->map.set_vpp = physmap_data->set_vpp;
> >
> > +#ifdef CONFIG_44x
>
>     Don't think we need this #ifdef at all.
>
> > +	if (sizeof(dev->resource->start) == 4)
> > +		info->map.virt = ioremap(info->map.phys, info->map.size);
>
>     This line is meaningless duplication of the existing one (below #else).
>
> > +	else
> > +		info->map.virt = ioremap64(dev->resource->start, info->map.size);
>
>     I see -- this is arch/ppc/... :-)
>     Wait, ioremap() takes phys_addr_t which should be 64-bit in your case.
> Is there the need to call ioremap64()?

Yes, but ioremap() first call fixup_bigphys_addr() and this unfortunately 
corrupts my addresses.

I know this patch is far from perfect, so any suggestions are very welcome.

Thanks.

Best regards,
Stefan

  reply	other threads:[~2007-01-18 17:46 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-18 17:07 [PATCH] [MTD] physmap: Add support for 64 bit resources on PPC44x Stefan Roese
2007-01-18 17:24 ` Sergei Shtylyov
2007-01-18 17:46   ` Stefan Roese [this message]
2007-01-18 23:59 ` Lennert Buytenhek
2007-01-19  1:29   ` Josh Boyer
2007-01-19  7:35     ` Stefan Roese

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=200701181846.21776.ml@stefan-roese.de \
    --to=ml@stefan-roese.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=sshtylyov@ru.mvista.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.