All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Wu <josh.wu@atmel.com>
To: Brian Norris <computersforpeace@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: [PATCH] mtd: atmel_nand: NFC: fix mtd_nandbiterrs.ko test fail when using sram write
Date: Tue, 5 Aug 2014 18:41:37 +0800	[thread overview]
Message-ID: <53E0B4E1.10504@atmel.com> (raw)
In-Reply-To: <20140804212259.GA3711@ld-irv-0074>

On 8/5/2014 5:22 AM, Brian Norris wrote:
> On Tue, Jul 22, 2014 at 05:25:38PM +0800, Josh Wu wrote:
>> diff --git a/drivers/mtd/nand/atmel_nand.c b/drivers/mtd/nand/atmel_nand.c
>> index 33826a0..012d687 100644
>> --- a/drivers/mtd/nand/atmel_nand.c
>> +++ b/drivers/mtd/nand/atmel_nand.c
>> @@ -1913,15 +1913,13 @@ static int nfc_sram_write_page(struct mtd_info *mtd, struct nand_chip *chip,
>>   	if (offset || (data_len < mtd->writesize))
>>   		return -EINVAL;
>>   
>> -	cfg = nfc_readl(host->nfc->hsmc_regs, CFG);
>> -	len = mtd->writesize;
>> -
>> -	if (unlikely(raw)) {
>> -		len += mtd->oobsize;
>> -		nfc_writel(host->nfc->hsmc_regs, CFG, cfg | NFC_CFG_WSPARE);
>> -	} else
>> -		nfc_writel(host->nfc->hsmc_regs, CFG, cfg & ~NFC_CFG_WSPARE);
>> +	if (data_len > mtd->writesize) {
>> +		dev_err(host->dev, "data_len: %d should not bigger than mtd->writesize: %d!\n",
> "should not be"
>
>> +				data_len, mtd->writesize);
>> +		return -EINVAL;
>> +	}
> The NAND layer guarantees that 'write_page' will never have to write
> more than 1 page (mtd->writesize), so the above block seems unnecessary.
> Drop it?

you are right. I sent a v2 version which drops this check. Thanks.

Best Regards,
Josh Wu
>
>>   
>> +	len = mtd->writesize;
>>   	/* Copy page data to sram that will write to nand via NFC */
>>   	if (use_dma) {
>>   		if (atmel_nand_dma_op(mtd, (void *)buf, len, 0) != 0)
>> @@ -1931,6 +1929,15 @@ static int nfc_sram_write_page(struct mtd_info *mtd, struct nand_chip *chip,
>>   		memcpy32_toio(sram, buf, len);
>>   	}
>>   
>> +	cfg = nfc_readl(host->nfc->hsmc_regs, CFG);
>> +	if (unlikely(raw) && oob_required) {
>> +		memcpy32_toio(sram + len, chip->oob_poi, mtd->oobsize);
>> +		len += mtd->oobsize;
>> +		nfc_writel(host->nfc->hsmc_regs, CFG, cfg | NFC_CFG_WSPARE);
>> +	} else {
>> +		nfc_writel(host->nfc->hsmc_regs, CFG, cfg & ~NFC_CFG_WSPARE);
>> +	}
>> +
>>   	if (chip->ecc.mode == NAND_ECC_HW && host->has_pmecc)
>>   		/*
>>   		 * When use NFC sram, need set up PMECC before send
> Brian

      reply	other threads:[~2014-08-05 10:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-22  9:25 [PATCH] mtd: atmel_nand: NFC: fix mtd_nandbiterrs.ko test fail when using sram write Josh Wu
2014-08-04 21:22 ` Brian Norris
2014-08-05 10:41   ` Josh Wu [this message]

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=53E0B4E1.10504@atmel.com \
    --to=josh.wu@atmel.com \
    --cc=computersforpeace@gmail.com \
    --cc=linux-mtd@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 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.