From: Paul Mundt <lethal@linux-sh.org>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH] ARM: mach-shmobile: G3EVM FLCTL platform data
Date: Mon, 22 Feb 2010 10:31:38 +0000 [thread overview]
Message-ID: <20100222103138.GB4356@linux-sh.org> (raw)
In-Reply-To: <20100219095406.5206.86934.sendpatchset@t400s>
On Fri, Feb 19, 2010 at 06:54:06PM +0900, Magnus Damm wrote:
> +static struct mtd_partition nand_partition_info[] = {
> + {
> + .name = "system",
> + .offset = 0,
> + .size = 64 * 1024 * 1024,
> + },
> + {
> + .name = "userdata",
> + .offset = MTDPART_OFS_APPEND,
> + .size = 128 * 1024 * 1024,
> + },
> + {
> + .name = "cache",
> + .offset = MTDPART_OFS_APPEND,
> + .size = 64 * 1024 * 1024,
> + },
> +};
> +
You may want to #include <asm/sizes.h> here and use the SZ_ helpers
instead. There is far too much existing ambiguity with sz vs sz - 1 for
resource length that consolidating on common helpers at least makes the
intent more immediately apparent.
> +static struct resource nand_flash_resources[] = {
> + [0] = {
> + .start = 0xe6a30000,
> + .end = 0xe6a3009b,
> + .flags = IORESOURCE_MEM,
> + }
> +};
> +
> +static struct sh_flctl_platform_data nand_flash_data = {
> + .parts = nand_partition_info,
> + .nr_parts = ARRAY_SIZE(nand_partition_info),
> + .flcmncr_val = QTSEL_E | FCKSEL_E | TYPESEL_SET | NANWF_E
> + | SHBUSSEL | SEL_16BIT,
> +};
This is also a bit special, |'s usually are at the end of the previous
line, not the beginning of the second one.
> + /* FOE, FCDE, FSC on dedicated pins */
> + __raw_writel(__raw_readl(0xe6158048) & ~(1 << 15), 0xe6158048);
> +
This looks suspiciously like an obfuscated MSTP toggle that the clock
framework needs to be handling. I thought I was already pretty clear when
I said I wouldn't be applying any more of these sorts of patches until
some basic clock framework support was in place?
next prev parent reply other threads:[~2010-02-22 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-19 9:54 [PATCH] ARM: mach-shmobile: G3EVM FLCTL platform data Magnus Damm
2010-02-22 10:31 ` Paul Mundt [this message]
2010-02-23 5:49 ` Magnus Damm
2010-05-20 3:36 ` 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=20100222103138.GB4356@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;
as well as URLs for NNTP newsgroup(s).