From: Mike Rapoport <mike@compulab.co.il>
To: tglx@linutronix.de
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] CM-x2xx NAND flash support
Date: Tue, 11 Jul 2006 10:46:27 +0200 [thread overview]
Message-ID: <44B36563.9050103@compulab.co.il> (raw)
In-Reply-To: <1152437179.24611.376.camel@localhost.localdomain>
Thomas Gleixner wrote:
>On Thu, 2006-07-06 at 14:48 +0200, Mike Rapoport wrote:
>
>
>>This patch provides MTD support for NAND flash devices on CM-x2xx modules.
>>
>>Signed-off-by: Mike Rapoport <mike@compulab.co.il>
>>
>>
>
>
>
>
>
>>+#define DRAIN_WB() \
>>+ do { \
>>+ unsigned char dummy; \
>>+ asm volatile ("mcr p15, 0, r0, c7, c10, 4":::"r0"); \
>>+ dummy=*((unsigned char*)UNCACHED_ADDR); \
>>+ } while(0);
>>
>>
>
>stray semicolon ----^
>
>I bet xscale has this functionality somewhere as a macro / inline already
>
>
I found none. Even md() on xscale will not drain write buffer.
>
>
>>+ unsigned int nandaddr = (unsigned int)this->IO_ADDR_W;
>>
>>
>
>what the hell is this type cast for ?
>
> void __iomem *nandaddr =
>
>
you can't do |= and &= with void __iomem*
>Can you please combine both drivers into one and make it a platform
>device. There is no need to keep lots of duplicate functionality around.
>
>
>
I'm dropping cm-x255 support (management decision) so there's only one
platform that can use this driver. What's the point then?
> tglx
>
>
>
>______________________________________________________
>Linux MTD discussion mailing list
>http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
--
Sincerely yours,
Mike Rapoport
next prev parent reply other threads:[~2006-07-11 7:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-06 12:48 [PATCH] CM-x2xx NAND flash support Mike Rapoport
2006-07-09 9:26 ` Thomas Gleixner
2006-07-11 8:46 ` Mike Rapoport [this message]
2006-07-11 8:10 ` Wolfgang Mües
2006-07-11 11:32 ` Mike Rapoport
2006-07-11 8:23 ` Thomas Gleixner
2006-07-11 12:36 ` Mike Rapoport
2006-07-12 13:21 ` Mike Rapoport
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=44B36563.9050103@compulab.co.il \
--to=mike@compulab.co.il \
--cc=linux-mtd@lists.infradead.org \
--cc=tglx@linutronix.de \
/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