From: LiuShuo <b35362@freescale.com>
To: <dedekind1@gmail.com>
Cc: linux-mtd@lists.infradead.org, Li Yang <leoli@freescale.com>,
dwmw2@infradead.org
Subject: Re: [PATCH 1/2] Integrated Flash Controller support
Date: Tue, 1 Nov 2011 10:23:19 +0800 [thread overview]
Message-ID: <4EAF5817.4070104@freescale.com> (raw)
In-Reply-To: <1319979883.2126.48.camel@koala>
于 2011年10月30日 21:04, Artem Bityutskiy 写道:
> Probably some PPC mailing list should be CCed? Could you please CC at
> least LKML?
Have re-sent.
> On Fri, 2011-10-28 at 13:40 +0800, b35362@freescale.com wrote:
>> +config FSL_IFC
>> + bool "Freescale Integrated Flash Controller support"
>> + depends on FSL_SOC
>> + help
>> + Enables reporting of errors from the Freescale integrated
>> + flash controller. Also contains some common code used by
>> + drivers for specific ifc controller peripherals.
> Why this cannot be a module?
Have changed it to be selected by other drivers only (NAND_FSL_IFC).
>
>> +/*
>> + * IFC Controller NAND Machine registers
>> + */
>> +struct fsl_ifc_nand {
>> + __be32 ncfgr;
>> + u32 res1[0x4];
>> + __be32 nand_fcr0;
>> + __be32 nand_fcr1;
>> + u32 res2[0x8];
>> + __be32 row0;
>> + u32 res3;
>> + __be32 col0;
>> + u32 res4;
>> + __be32 row1;
>> + u32 res5;
>> + __be32 col1;
>> + u32 res6;
>> + __be32 row2;
>> + u32 res7;
>> + __be32 col2;
>> + u32 res8;
>> + __be32 row3;
>> + u32 res9;
>> + __be32 col3;
>> + u32 res10[0x24];
> I do not know the HW, but I wonder why some fields are __be32 and some
> are u32? What is the logic behind that?
>
These u32s are reserved space, I think it should be ok.
-LiuShuo
prev parent reply other threads:[~2011-11-01 2:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-28 5:40 [PATCH 1/2] Integrated Flash Controller support b35362
2011-10-28 5:40 ` [PATCH] mtd/nand : set Nand flash page address to FBAR and FPAR correctly b35362
2011-10-28 5:40 ` [PATCH 2/2] NAND Machine support for Integrated Flash Controller b35362
2011-10-30 13:04 ` [PATCH 1/2] Integrated Flash Controller support Artem Bityutskiy
2011-11-01 2:23 ` LiuShuo [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=4EAF5817.4070104@freescale.com \
--to=b35362@freescale.com \
--cc=dedekind1@gmail.com \
--cc=dwmw2@infradead.org \
--cc=leoli@freescale.com \
--cc=linux-mtd@lists.infradead.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