From: zonque@gmail.com (Daniel Mack)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND
Date: Wed, 21 Nov 2012 11:15:23 +0100 [thread overview]
Message-ID: <50ACA9BB.7090106@gmail.com> (raw)
In-Reply-To: <87mwycjmdn.fsf@dell.be.48ers.dk>
On 20.11.2012 16:59, Peter Korsgaard wrote:
>>>>>> "Daniel" == Daniel Mack <zonque@gmail.com> writes:
>
> Hi,
>
> >>>> In omap2 driver NAND_ECC_HW ecc mode supports 3 ecc layout
> >>>> OMAP_ECC_HAMMING_CODE_HW_ROMCODE
> >>>> OMAP_ECC_BCH4_CODE_HW
> >>>> OMAP_ECC_BCH8_CODE_HW
> >>>>
> >>>> So selection of ecc layout data should come from DT not ecc mode.
> >>>
> >>> Ok, I see. I would still like to set them by string rather than magic
> >>> numbers that map to enum entries. Valid values would be "none", "hw",
> >>> "hw-romcode", "bch4" and "bch8". Are you ok with that?
> >>
> >> Ok, that's nice. Better use ecc_opt instead of ecc_mode.
>
> Daniel> I did some more extensive tests that include reading the same
> Daniel> nand pages from both U-Boot and the kernel with BCH8 ECC, and
> Daniel> it turns out that -> is_elm_used needs to be set in the pdata
> Daniel> in order to make this work.
>
> So what you're saying is that the choice of ELM or not is not just an
> optimization, it really changes the ECC layout? Perhaps it should be
> treated as a seperate layout (E.G. bch8-elm) then?
That is what I experienced, yes. The kernel was unable to parse NAND
pages that were written from U-Boot with bch8 hardware mode when the elm
module was not active. Maybe someone from TI can explain that? Giving it
a dedicated name would also solve the problem with the extra DT property.
I'll wait until this is decided before I resend a new set that also
fixes the issue with the errornousely forgotten Documentation file.
Thanks,
Daniel
next prev parent reply other threads:[~2012-11-21 10:15 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 15:25 [PATCH v3 0/4] RFC: OMAP GPMC DT bindings Daniel Mack
2012-11-02 15:25 ` [PATCH v3 1/4] mtd: omap-nand: pass device_node in platform data Daniel Mack
2012-11-02 15:25 ` [PATCH v3 2/4] ARM: OMAP: gpmc: enable hwecc for AM33xx SoCs Daniel Mack
2012-11-05 10:57 ` Philip, Avinash
2012-11-02 15:25 ` [PATCH v3 3/4] ARM: OMAP: gpmc: don't create devices from initcall on DT Daniel Mack
2012-11-02 15:25 ` [PATCH v3 4/4] ARM: OMAP: gpmc: add DT bindings for GPMC timings and NAND Daniel Mack
2012-11-05 11:03 ` Philip, Avinash
2012-11-05 12:58 ` Daniel Mack
2012-11-05 13:29 ` Philip, Avinash
2012-11-05 23:03 ` Murali Karicheri
2012-11-07 9:48 ` Daniel Mack
2012-11-07 15:37 ` Philip, Avinash
2012-11-10 18:56 ` Daniel Mack
2012-11-15 0:26 ` Daniel Mack
2012-11-19 6:06 ` Philip, Avinash
2012-11-20 15:59 ` Peter Korsgaard
2012-11-21 10:15 ` Daniel Mack [this message]
2012-11-23 10:43 ` Philip, Avinash
2012-11-27 14:00 ` Daniel Mack
2012-11-28 5:01 ` Philip, Avinash
2012-12-01 21:50 ` Ivan Djelic
2012-12-05 5:15 ` Philip, Avinash
2012-12-06 10:15 ` Ivan Djelic
2012-12-06 13:12 ` Philip, Avinash
2012-11-02 19:29 ` [PATCH v3 0/4] RFC: 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=50ACA9BB.7090106@gmail.com \
--to=zonque@gmail.com \
--cc=linux-arm-kernel@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;
as well as URLs for NNTP newsgroup(s).