From: Daniel Mack <zonque@gmail.com>
To: Peter Korsgaard <jacmet@sunsite.dk>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
jon-hunter@ti.com, avinashphilip@ti.com, x0148406@ti.com,
tony@atomide.com, paul@pwsan.com, nsekhar@ti.com
Subject: Re: [PATCH v4 3/3] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND
Date: Fri, 23 Nov 2012 11:55:12 +0100 [thread overview]
Message-ID: <50AF5610.7010505@gmail.com> (raw)
In-Reply-To: <87vccwegu2.fsf@dell.be.48ers.dk>
On 23.11.2012 11:47, Peter Korsgaard wrote:
>>>>>> "Daniel" == Daniel Mack <zonque@gmail.com> writes:
>
> Hi,
>
> D> + Layouts for 1-bit ecc: stored at beginning of spare area as romcode:
> D> +
> D> + "hw-romcode" gpmc method & romcode layout
> D> + "bch4" 4-bit BCH ecc code
> D> + "bch8" 8-bit BCH ecc code
> D> +
> >>
> >> These are not 1-bit - Well, romcode might be depending on SoC. Looking at
> >> omap2.c it seems to be an alias for hw, so that isn't really helpful on
> >> E.G. am33xx where you should select bch8 to have something compatible
> >> with the romcode.
>
> Daniel> Not sure whether I follow you here. drivers/mtd/nand/omap2.c handles
> Daniel> cases for pdata->ecc_opt == OMAP_ECC_BCH8_CODE_HW, so the DT bindings
> Daniel> need to offer a way to set it.
>
> Daniel> Or are you purely referring to the comments only?
>
> Yes, but the document states (the first line I'm quotinge) 'Layouts for
> 1-bit ecc'.
Ok, I guess I'll just remove these comments then.
> The other comment was about hw-romcode not being a very good
> name, as it apparently means the 1bit hamming code and ECC layout used
> on the older omap3, and not E.G. the bch8/elm layout used by
> E.G. am335x.
So which name would you pick? "bch1"?
> As discussed elsewhere, the elm also changes the ECC layout, so why not
> just have bchN (software bchN layout) / bchN-elm selections instead of
> the seperate ti,nand-ecc-use-elm?
Avinash - what do you think?
Thanks for the feedback - I'd also like to get these bindings right in
the first place.
Daniel
next prev parent reply other threads:[~2012-11-23 10:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-19 15:29 [PATCH v4 0/3] OMAP GPMC DT bindings Daniel Mack
2012-11-19 15:29 ` [PATCH v4 1/3] mtd: omap-nand: pass device_node in platform data Daniel Mack
2012-11-19 15:29 ` [PATCH v4 2/3] ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs Daniel Mack
2012-11-19 15:29 ` [PATCH v4 3/3] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND Daniel Mack
2012-11-19 20:52 ` Peter Korsgaard
2012-11-23 10:36 ` Daniel Mack
2012-11-23 10:47 ` Peter Korsgaard
2012-11-23 10:55 ` Daniel Mack [this message]
2012-11-23 11:06 ` Peter Korsgaard
2012-11-20 11:26 ` Philip, Avinash
2012-11-19 16:48 ` [PATCH v4 0/3] OMAP GPMC DT bindings Jon Hunter
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=50AF5610.7010505@gmail.com \
--to=zonque@gmail.com \
--cc=avinashphilip@ti.com \
--cc=jacmet@sunsite.dk \
--cc=jon-hunter@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nsekhar@ti.com \
--cc=paul@pwsan.com \
--cc=tony@atomide.com \
--cc=x0148406@ti.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 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).