From: Boris BREZILLON <b.brezillon.dev@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: linux-mtd@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mtd: add per NAND partition ECC config
Date: Tue, 11 Feb 2014 15:22:29 +0100 [thread overview]
Message-ID: <52FA3225.5010203@gmail.com> (raw)
In-Reply-To: <20140211140102.GB23150@localhost>
Hi Ezequiel,
On 11/02/2014 15:01, Ezequiel Garcia wrote:
> Hi Boris,
>
> On Sat, Feb 08, 2014 at 11:26:46AM +0100, Boris BREZILLON wrote:
>> This patch aims to add per partition ECC config for NAND devices.
>> It defines a new field in the mtd struct to store the mtd ECC config and
>> thus each mtd partition device can store its config instead of using the
>> default NAND chip config.
>>
>> This feature is needed to support the sunxi boot0 paritition case:
>> Allwinner boot code (BROM) requires a specific HW ECC for its boot code
>> that may not fit the HW NAND requirements for the entire NAND chip.
>>
>> Signed-off-by: Boris BREZILLON <b.brezillon.dev@gmail.com>
>> ---
>> Hello,
>>
>> This patch is just a draft that implement per partition ECC config.
>> It's currently not properly splitted (it should be separated in several
>> patches) and not documented either.
>>
> Ah, ah...
>
>> There's at least one point that bother me in the current implementation:
>> I introduced DT notions in the nand core code by the mean of the get_ecc_ctrl
>> callback, and so far this was kept out of mtd/nand core code (I guess it was
>> on purpose).
>>
>> Please let me know if you see other drawbacks.
>>
>> If you think per partition ECC should not be implemented, could you help me
>> find a way to handle sunxi specific case decribed above ?
>>
>> drivers/mtd/mtdpart.c | 23 ++-
>> drivers/mtd/nand/nand_base.c | 428 ++++++++++++++++++++++++----------------
> I really appreciate your effort, but 428 changed lines is a too big and
> intrusive change. I must admit I'm not smart enough to review such patches.
>
> I honestly think you'll have better luck getting feedback if you take the time
> to properly split and document this.
>
> Yeah, it's annoying and time-consuming, but it's globally cheaper for you to
> invest time on making it easier for reviewers and maintainers, than for each
> of us to invest the time deciphering this :-)
Fair enough.
Anyway, this proposal does not work.
If nobody objects to this ECC per partition concept, I'll propose
something else soon.
And this time I'll make a proper documentation and patch separation ;-).
Best Regards,
Boris
>
> Just my point of view, of course.
WARNING: multiple messages have this Message-ID (diff)
From: Boris BREZILLON <b.brezillon.dev@gmail.com>
To: Ezequiel Garcia <ezequiel.garcia@free-electrons.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Maxime Ripard <maxime.ripard@free-electrons.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH] mtd: add per NAND partition ECC config
Date: Tue, 11 Feb 2014 15:22:29 +0100 [thread overview]
Message-ID: <52FA3225.5010203@gmail.com> (raw)
In-Reply-To: <20140211140102.GB23150@localhost>
Hi Ezequiel,
On 11/02/2014 15:01, Ezequiel Garcia wrote:
> Hi Boris,
>
> On Sat, Feb 08, 2014 at 11:26:46AM +0100, Boris BREZILLON wrote:
>> This patch aims to add per partition ECC config for NAND devices.
>> It defines a new field in the mtd struct to store the mtd ECC config and
>> thus each mtd partition device can store its config instead of using the
>> default NAND chip config.
>>
>> This feature is needed to support the sunxi boot0 paritition case:
>> Allwinner boot code (BROM) requires a specific HW ECC for its boot code
>> that may not fit the HW NAND requirements for the entire NAND chip.
>>
>> Signed-off-by: Boris BREZILLON <b.brezillon.dev@gmail.com>
>> ---
>> Hello,
>>
>> This patch is just a draft that implement per partition ECC config.
>> It's currently not properly splitted (it should be separated in several
>> patches) and not documented either.
>>
> Ah, ah...
>
>> There's at least one point that bother me in the current implementation:
>> I introduced DT notions in the nand core code by the mean of the get_ecc_ctrl
>> callback, and so far this was kept out of mtd/nand core code (I guess it was
>> on purpose).
>>
>> Please let me know if you see other drawbacks.
>>
>> If you think per partition ECC should not be implemented, could you help me
>> find a way to handle sunxi specific case decribed above ?
>>
>> drivers/mtd/mtdpart.c | 23 ++-
>> drivers/mtd/nand/nand_base.c | 428 ++++++++++++++++++++++++----------------
> I really appreciate your effort, but 428 changed lines is a too big and
> intrusive change. I must admit I'm not smart enough to review such patches.
>
> I honestly think you'll have better luck getting feedback if you take the time
> to properly split and document this.
>
> Yeah, it's annoying and time-consuming, but it's globally cheaper for you to
> invest time on making it easier for reviewers and maintainers, than for each
> of us to invest the time deciphering this :-)
Fair enough.
Anyway, this proposal does not work.
If nobody objects to this ECC per partition concept, I'll propose
something else soon.
And this time I'll make a proper documentation and patch separation ;-).
Best Regards,
Boris
>
> Just my point of view, of course.
next prev parent reply other threads:[~2014-02-11 14:22 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-08 10:26 [RFC PATCH] mtd: add per NAND partition ECC config Boris BREZILLON
2014-02-08 10:26 ` Boris BREZILLON
2014-02-08 10:36 ` Boris BREZILLON
2014-02-08 10:36 ` Boris BREZILLON
2014-02-10 11:55 ` Gupta, Pekon
2014-02-10 12:28 ` Boris BREZILLON
2014-02-10 18:11 ` Boris BREZILLON
2014-02-10 18:11 ` Boris BREZILLON
2014-02-11 14:01 ` Ezequiel Garcia
2014-02-11 14:01 ` Ezequiel Garcia
2014-02-11 14:22 ` Boris BREZILLON [this message]
2014-02-11 14:22 ` Boris BREZILLON
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=52FA3225.5010203@gmail.com \
--to=b.brezillon.dev@gmail.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=ezequiel.garcia@free-electrons.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=maxime.ripard@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.