From: Artem Bityutskiy <dedekind1@gmail.com>
To: b35362@freescale.com
Cc: linux-mtd@lists.infradead.org, dwmw2@infradead.org
Subject: Re: [PATCH 1/2] Integrated Flash Controller support
Date: Sun, 30 Oct 2011 15:04:41 +0200 [thread overview]
Message-ID: <1319979883.2126.48.camel@koala> (raw)
In-Reply-To: <1319780403-8680-1-git-send-email-b35362@freescale.com>
Probably some PPC mailing list should be CCed? Could you please CC at
least LKML?
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?
> +/*
> + * 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?
next prev parent reply other threads:[~2011-10-30 13:04 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 ` Artem Bityutskiy [this message]
2011-11-01 2:23 ` [PATCH 1/2] Integrated Flash Controller support LiuShuo
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=1319979883.2126.48.camel@koala \
--to=dedekind1@gmail.com \
--cc=b35362@freescale.com \
--cc=dwmw2@infradead.org \
--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