All of lore.kernel.org
 help / color / mirror / Atom feed
From: Murali Karicheri <m-karicheri2@ti.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: <dwmw2@infradead.org>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <wsa@the-dreams.de>,
	Hao Zhang <hzhang@ti.com>
Subject: Re: [Patch v2] nand: davinci: add support for 4K page size nand devices
Date: Mon, 20 Jul 2015 14:02:52 -0400	[thread overview]
Message-ID: <55AD37CC.6080308@ti.com> (raw)
In-Reply-To: <20150720173203.GB24125@google.com>

On 07/20/2015 01:32 PM, Brian Norris wrote:
> On Tue, Aug 19, 2014 at 03:31:54PM +0300, Ivan Khoronzhuk wrote:
>> From: Sandeep Paulraj <s-paulraj@ti.com>
>>
>> It is needed for k2l keystone2 EVM which uses NAND flash with 4K page
>> size, hence add support for 4K page size nand devices.
>>
>> Signed-off-by: Sandeep Paulraj <s-paulraj@ti.com>
>> Signed-off-by: Ivan Khoronzhuk <ivan.khoronzhuk@ti.com>
>> ---
>>
>> Based on l2-mtd/master
>>
>> v1..v2:
>> - fixed comment style, no functional changes
>
> This was resurrected Murali Karicheri. Since this one is nearly
> identical and much preceded it, I've pushed it to l2-mtd.git.
>
Brian,

Thanks.

Murali
> Thanks,
> Brian
>
>>   drivers/mtd/nand/davinci_nand.c | 42 ++++++++++++++++++++++++++++++-----------
>>   1 file changed, 31 insertions(+), 11 deletions(-)
>>
>> diff --git a/drivers/mtd/nand/davinci_nand.c b/drivers/mtd/nand/davinci_nand.c
>> index b922c8e..d7df32c 100644
>> --- a/drivers/mtd/nand/davinci_nand.c
>> +++ b/drivers/mtd/nand/davinci_nand.c
>> @@ -520,6 +520,32 @@ static struct nand_ecclayout hwecc4_2048 = {
>>   	},
>>   };
>>
>> +/*
>> + * An ECC layout for using 4-bit ECC with large-page (4096bytes) flash,
>> + * storing ten ECC bytes plus the manufacturer's bad block marker byte,
>> + * and not overlapping the default BBT markers.
>> + */
>> +static struct nand_ecclayout hwecc4_4096 = {
>> +	.eccbytes = 80,
>> +	.eccpos = {
>> +		/* at the end of spare sector */
>> +		48, 49, 50, 51, 52, 53, 54, 55, 56, 57,
>> +		58, 59, 60, 61, 62, 63, 64, 65, 66, 67,
>> +		68, 69, 70, 71, 72, 73, 74, 75, 76, 77,
>> +		78, 79, 80, 81, 82, 83, 84, 85, 86, 87,
>> +		88, 89, 90, 91, 92, 93, 94, 95, 96, 97,
>> +		98, 99, 100, 101, 102, 103, 104, 105, 106, 107,
>> +		108, 109, 110, 111, 112, 113, 114, 115, 116, 117,
>> +		118, 119, 120, 121, 122, 123, 124, 125, 126, 127,
>> +	},
>> +	.oobfree = {
>> +		/* 2 bytes at offset 0 hold manufacturer badblock markers */
>> +		{.offset = 2, .length = 46, },
>> +		/* 5 bytes at offset 8 hold BBT markers */
>> +		/* 8 bytes at offset 16 hold JFFS2 clean markers */
>> +	},
>> +};
>> +
>>   #if defined(CONFIG_OF)
>>   static const struct of_device_id davinci_nand_of_match[] = {
>>   	{.compatible = "ti,davinci-nand", },
>> @@ -796,18 +822,12 @@ static int nand_davinci_probe(struct platform_device *pdev)
>>   			info->chip.ecc.mode = NAND_ECC_HW_OOB_FIRST;
>>   			goto syndrome_done;
>>   		}
>> +		if (chunks == 8) {
>> +			info->ecclayout = hwecc4_4096;
>> +			info->chip.ecc.mode = NAND_ECC_HW_OOB_FIRST;
>> +			goto syndrome_done;
>> +		}
>>
>> -		/* 4KiB page chips are not yet supported. The eccpos from
>> -		 * nand_ecclayout cannot hold 80 bytes and change to eccpos[]
>> -		 * breaks userspace ioctl interface with mtd-utils. Once we
>> -		 * resolve this issue, NAND_ECC_HW_OOB_FIRST mode can be used
>> -		 * for the 4KiB page chips.
>> -		 *
>> -		 * TODO: Note that nand_ecclayout has now been expanded and can
>> -		 *  hold plenty of OOB entries.
>> -		 */
>> -		dev_warn(&pdev->dev, "no 4-bit ECC support yet "
>> -				"for 4KiB-page NAND\n");
>>   		ret = -EIO;
>>   		goto err;
>>
>> --
>> 1.8.3.2
>>
>


-- 
Murali Karicheri
Linux Kernel, Keystone

  reply	other threads:[~2015-07-20 18:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-19 12:31 [Patch v2] nand: davinci: add support for 4K page size nand devices Ivan Khoronzhuk
2014-08-19 12:31 ` Ivan Khoronzhuk
2015-07-20 17:32 ` Brian Norris
2015-07-20 18:02   ` Murali Karicheri [this message]
2015-07-20 18:12   ` Ivan Khoronzhuk

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=55AD37CC.6080308@ti.com \
    --to=m-karicheri2@ti.com \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=hzhang@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=wsa@the-dreams.de \
    /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.