From: Stefan Agner <stefan@agner.ch>
To: Boris Brezillon <boris.brezillon@bootlin.com>, han.xu@nxp.com
Cc: boris.brezillon@free-electrons.com, max.oss.09@gmail.com,
richard@nod.at, linux-kernel@vger.kernel.org,
marek.vasut@gmail.com, linux-mtd@lists.infradead.org,
cyrille.pitchen@wedev4u.fr, dwmw2@infradead.org
Subject: Re: [PATCH v2 1/2] mtd: rawnand: gpmi: add support for specific ECC strength
Date: Thu, 12 Apr 2018 08:56:45 +0200 [thread overview]
Message-ID: <cc054c7e3c924e87864bdfec33d83dbd@agner.ch> (raw)
In-Reply-To: <C8FA1701-52CE-46B6-9A3E-3249D1BDA4AC@agner.ch>
Han,
On 15.03.2018 16:39, Stefan Agner wrote:
> On March 15, 2018 4:36:20 PM GMT+01:00, Boris Brezillon
> <boris.brezillon@bootlin.com> wrote:
>>Hi,
>>
>>On Sun, 4 Mar 2018 21:06:01 +0100
>>Stefan Agner <stefan@agner.ch> wrote:
>>
>>> Add support for specified ECC strength/size using device tree
>>> properties nand-ecc-strength/nand-ecc-step-size.
>>
>>Han, we didn't hear back from you on that. Are you okay with adding
>>these new properties? IIRC, you feared there would be a delta between
>>u-boot and linux support.
Any comment on this?
U-Boot support for device tree support and the same properties is
underway.
--
Stefan
>>
>>Stephan, there's no changelog. Has anything changed in this version or
>>is this just a RESEND?
>
> Sorry forgot that. I just split documentation and driver changes.
>
> --
> Stefan
>
>>
>>Regards,
>>
>>Boris
>>
>>>
>>> Signed-off-by: Stefan Agner <stefan@agner.ch>
>>> ---
>>> drivers/mtd/nand/gpmi-nand/gpmi-nand.c | 30
>>++++++++++++++++++++----------
>>> 1 file changed, 20 insertions(+), 10 deletions(-)
>>>
>>> diff --git a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>>b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>>> index 61fdd733492f..d04754289c03 100644
>>> --- a/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>>> +++ b/drivers/mtd/nand/gpmi-nand/gpmi-nand.c
>>> @@ -198,17 +198,16 @@ static inline bool gpmi_check_ecc(struct
>>gpmi_nand_data *this)
>>> *
>>> * We may have available oob space in this case.
>>> */
>>> -static int set_geometry_by_ecc_info(struct gpmi_nand_data *this)
>>> +static int set_geometry_by_ecc_info(struct gpmi_nand_data *this,
>>> + unsigned int ecc_strength,
>>> + unsigned int ecc_step)
>>> {
>>> struct bch_geometry *geo = &this->bch_geometry;
>>> struct nand_chip *chip = &this->nand;
>>> struct mtd_info *mtd = nand_to_mtd(chip);
>>> unsigned int block_mark_bit_offset;
>>>
>>> - if (!(chip->ecc_strength_ds > 0 && chip->ecc_step_ds > 0))
>>> - return -EINVAL;
>>> -
>>> - switch (chip->ecc_step_ds) {
>>> + switch (ecc_step) {
>>> case SZ_512:
>>> geo->gf_len = 13;
>>> break;
>>> @@ -221,8 +220,8 @@ static int set_geometry_by_ecc_info(struct
>>gpmi_nand_data *this)
>>> chip->ecc_strength_ds, chip->ecc_step_ds);
>>> return -EINVAL;
>>> }
>>> - geo->ecc_chunk_size = chip->ecc_step_ds;
>>> - geo->ecc_strength = round_up(chip->ecc_strength_ds, 2);
>>> + geo->ecc_chunk_size = ecc_step;
>>> + geo->ecc_strength = round_up(ecc_strength, 2);
>>> if (!gpmi_check_ecc(this))
>>> return -EINVAL;
>>>
>>> @@ -230,7 +229,7 @@ static int set_geometry_by_ecc_info(struct
>>gpmi_nand_data *this)
>>> if (geo->ecc_chunk_size < mtd->oobsize) {
>>> dev_err(this->dev,
>>> "unsupported nand chip. ecc size: %d, oob size : %d\n",
>>> - chip->ecc_step_ds, mtd->oobsize);
>>> + ecc_step, mtd->oobsize);
>>> return -EINVAL;
>>> }
>>>
>>> @@ -423,9 +422,20 @@ static int legacy_set_geometry(struct
>>gpmi_nand_data *this)
>>>
>>> int common_nfc_set_geometry(struct gpmi_nand_data *this)
>>> {
>>> + struct nand_chip *chip = &this->nand;
>>> +
>>> + if (chip->ecc.strength > 0 && chip->ecc.size > 0)
>>> + return set_geometry_by_ecc_info(this, chip->ecc.strength,
>>> + chip->ecc.size);
>>> +
>>> if ((of_property_read_bool(this->dev->of_node,
>>"fsl,use-minimum-ecc"))
>>> - || legacy_set_geometry(this))
>>> - return set_geometry_by_ecc_info(this);
>>> + || legacy_set_geometry(this)) {
>>> + if (!(chip->ecc_strength_ds > 0 && chip->ecc_step_ds > 0))
>>> + return -EINVAL;
>>> +
>>> + return set_geometry_by_ecc_info(this, chip->ecc_strength_ds,
>>> + chip->ecc_step_ds);
>>> + }
>>>
>>> return 0;
>>> }
next prev parent reply other threads:[~2018-04-12 6:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-04 20:06 [PATCH v2 1/2] mtd: rawnand: gpmi: add support for specific ECC strength Stefan Agner
2018-03-04 20:06 ` [PATCH v2 2/2] dt-bindings: mtd: rawnand: gpmi: document " Stefan Agner
2018-04-13 21:57 ` Han Xu
2018-03-15 15:36 ` [PATCH v2 1/2] mtd: rawnand: gpmi: add support for " Boris Brezillon
2018-03-15 15:39 ` Stefan Agner
2018-04-12 6:56 ` Stefan Agner [this message]
2018-04-13 21:57 ` Han Xu
2018-04-22 17:24 ` 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=cc054c7e3c924e87864bdfec33d83dbd@agner.ch \
--to=stefan@agner.ch \
--cc=boris.brezillon@bootlin.com \
--cc=boris.brezillon@free-electrons.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=han.xu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=max.oss.09@gmail.com \
--cc=richard@nod.at \
/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