From: Brian Norris <computersforpeace@gmail.com>
To: Pekon Gupta <pekon@ti.com>
Cc: devicetree@vger.kernel.org, arnd@arndb.de, dedekind1@gmail.com,
tony@atomide.com, avinashphilipk@gmail.com, balbi@ti.com,
linux-mtd@lists.infradead.org, olof@lixom.net,
benoit.cousson@linaro.org, linux-omap@vger.kernel.org,
dwmw2@infradead.org
Subject: Re: [PATCH v6 2/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe
Date: Wed, 25 Sep 2013 11:42:21 -0700 [thread overview]
Message-ID: <20130925184221.GC23337@ld-irv-0074.broadcom.com> (raw)
In-Reply-To: <1378986619-26765-3-git-send-email-pekon@ti.com>
Hi Pekon,
On Thu, Sep 12, 2013 at 05:20:17PM +0530, Pekon Gupta wrote:
> OMAP NAND driver support multiple ECC scheme, which can used in following
> different flavours, depending on in-build Hardware engines supported by SoC.
>
> +---------------------------------------+---------------+---------------+
> | ECC scheme |ECC calculation|Error detection|
> +---------------------------------------+---------------+---------------+
> |OMAP_ECC_HAMMING_CODE_HW |H/W (GPMC) |S/W |
> +---------------------------------------+---------------+---------------+
> |OMAP_ECC_BCH8_CODE_HW_DETECTION_SW |H/W (GPMC) |S/W |
> |(requires CONFIG_MTD_NAND_ECC_BCH) | | |
> +---------------------------------------+---------------+---------------+
> |OMAP_ECC_BCH8_CODE_HW |H/W (GPMC) |H/W (ELM) |
> |(requires CONFIG_MTD_NAND_OMAP_BCH && | | |
> | ti,elm-id in DT) | | |
> +---------------------------------------+---------------+---------------+
> To optimize footprint of omap2-nand driver, selection of some ECC schemes
> also require enabling following Kconfigs, in addition to setting appropriate
> DT bindings
> - Kconfig:CONFIG_MTD_NAND_ECC_BCH enables S/W based BCH ECC algorithm
> - Kconfig:CONFIG_MTD_NAND_OMAP_BCH enables H/W based BCH ECC algorithm
>
> This patch
... does too many unrelated things in a single patch. I am not
comfortable taking large amounts of refactoring mixed in with Kconfig
and #ifdef changes. Can you please separate the steps you list below
into multiple patches and describe each one? I think you are doing many
trivial things, but it's difficult to separate the noise out from the
substantial changes.
Or, you can wait even longer until I have more time to kill :)
> - removes OMAP_ECC_HAMMING_CODE_DEFAULT and OMAP_ECC_HAMMING_CODE_HW_ROMCODE
> - separates the configurations for other ECC schemes
> - fixes dependency issues based on Kconfig options
> - updates ELM device detection in is_elm_present()
> - cleans redundant code
Brian
next prev parent reply other threads:[~2013-09-25 18:50 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 11:50 [PATCH v6 0/4] mtd:nand:omap2: clean-up of supported ECC schemes Pekon Gupta
2013-09-12 11:50 ` [PATCH v6 1/4] ARM: OMAP2+: cleaned-up DT support of various " Pekon Gupta
2013-09-24 18:04 ` Gupta, Pekon
2013-09-25 13:46 ` Felipe Balbi
2013-09-25 17:46 ` Brian Norris
2013-09-25 17:55 ` Brian Norris
2013-09-25 19:24 ` Gupta, Pekon
2013-09-25 20:05 ` Brian Norris
2013-09-25 20:33 ` Olof Johansson
2013-09-25 21:29 ` Brian Norris
2013-09-25 21:32 ` Olof Johansson
2013-09-25 22:22 ` Brian Norris
2013-09-26 9:18 ` Mark Rutland
2013-09-26 9:32 ` Gupta, Pekon
2013-09-26 6:15 ` Gupta, Pekon
2013-09-25 18:29 ` Brian Norris
2013-09-25 22:23 ` Rob Herring
2013-09-26 6:08 ` Gupta, Pekon
2013-09-26 10:54 ` Gupta, Pekon
2013-09-26 17:09 ` Mark Rutland
2013-09-27 6:17 ` Gupta, Pekon
2013-09-26 17:27 ` Brian Norris
2013-09-12 11:50 ` [PATCH v6 2/4] mtd:nand:omap2: clean-up BCHx_HW and BCHx_SW ECC configurations in device_probe Pekon Gupta
2013-09-25 18:42 ` Brian Norris [this message]
2013-09-25 19:02 ` Brian Norris
2013-09-12 11:50 ` [PATCH v6 3/4] mtd:nand:omap2: updated support for BCH4 ECC scheme Pekon Gupta
2013-09-25 19:13 ` Brian Norris
2013-09-12 11:50 ` [PATCH v6 4/4] ARM: dts: AM33xx: updated default ECC scheme in nand-ecc-opt Pekon Gupta
2013-09-25 19:15 ` Brian Norris
2013-09-26 11:28 ` Gupta, Pekon
2013-09-26 13:26 ` Javier Martinez Canillas
2013-09-26 10:58 ` [PATCH v6 0/4] mtd:nand:omap2: clean-up of supported ECC schemes Gupta, Pekon
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=20130925184221.GC23337@ld-irv-0074.broadcom.com \
--to=computersforpeace@gmail.com \
--cc=arnd@arndb.de \
--cc=avinashphilipk@gmail.com \
--cc=balbi@ti.com \
--cc=benoit.cousson@linaro.org \
--cc=dedekind1@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dwmw2@infradead.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=olof@lixom.net \
--cc=pekon@ti.com \
--cc=tony@atomide.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