All of lore.kernel.org
 help / color / mirror / Atom feed
From: Josh Wu <josh.wu@atmel.com>
To: <linux-mtd@lists.infradead.org>
Cc: computersforpeace@gmail.com
Subject: Re: [PATCH 1/2] mtd: atmel_nand: remove pmecc_sector_number, use ecc.steps instead
Date: Wed, 17 Sep 2014 16:33:01 +0800	[thread overview]
Message-ID: <5419473D.7060007@atmel.com> (raw)
In-Reply-To: <1407489155-16545-1-git-send-email-josh.wu@atmel.com>

Hi, Brian

Any feedback for this patch series?

Best Regards,
Josh Wu

On 8/8/2014 5:12 PM, Josh Wu wrote:
> For PMECC, the pmecc_sector_number has same meaning as ecc.steps.
> So use ecc.steps to replace the pmecc_sector_number.
>
> Signed-off-by: Josh Wu <josh.wu@atmel.com>
> ---
>   drivers/mtd/nand/atmel_nand.c | 14 ++++++--------
>   1 file changed, 6 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/mtd/nand/atmel_nand.c b/drivers/mtd/nand/atmel_nand.c
> index 9c5f717..1dc3988 100644
> --- a/drivers/mtd/nand/atmel_nand.c
> +++ b/drivers/mtd/nand/atmel_nand.c
> @@ -129,7 +129,6 @@ struct atmel_nand_host {
>   	u32			pmecc_lookup_table_offset_1024;
>   
>   	int			pmecc_bytes_per_sector;
> -	int			pmecc_sector_number;
>   	int			pmecc_degree;	/* Degree of remainders */
>   	int			pmecc_cw_len;	/* Length of codeword */
>   
> @@ -874,7 +873,7 @@ static int pmecc_correction(struct mtd_info *mtd, u32 pmecc_stat, uint8_t *buf,
>   	return 0;
>   
>   normal_check:
> -	for (i = 0; i < host->pmecc_sector_number; i++) {
> +	for (i = 0; i < nand_chip->ecc.steps; i++) {
>   		err_nbr = 0;
>   		if (pmecc_stat & 0x1) {
>   			buf_pos = buf + i * host->pmecc_sector_size;
> @@ -984,7 +983,7 @@ static int atmel_nand_pmecc_write_page(struct mtd_info *mtd,
>   		cpu_relax();
>   	}
>   
> -	for (i = 0; i < host->pmecc_sector_number; i++) {
> +	for (i = 0; i < chip->ecc.steps; i++) {
>   		for (j = 0; j < host->pmecc_bytes_per_sector; j++) {
>   			int pos;
>   
> @@ -1031,7 +1030,7 @@ static void atmel_pmecc_core_init(struct mtd_info *mtd)
>   	else if (host->pmecc_sector_size == 1024)
>   		val |= PMECC_CFG_SECTOR1024;
>   
> -	switch (host->pmecc_sector_number) {
> +	switch (nand_chip->ecc.steps) {
>   	case 1:
>   		val |= PMECC_CFG_PAGE_1SECTOR;
>   		break;
> @@ -1184,18 +1183,17 @@ static int atmel_pmecc_nand_init_params(struct platform_device *pdev,
>   		host->pmecc_degree = (sector_size == 512) ?
>   			PMECC_GF_DIMENSION_13 : PMECC_GF_DIMENSION_14;
>   		host->pmecc_cw_len = (1 << host->pmecc_degree) - 1;
> -		host->pmecc_sector_number = mtd->writesize / sector_size;
>   		host->pmecc_bytes_per_sector = pmecc_get_ecc_bytes(
>   			cap, sector_size);
>   		host->pmecc_alpha_to = pmecc_get_alpha_to(host);
>   		host->pmecc_index_of = host->pmecc_rom_base +
>   			host->pmecc_lookup_table_offset;
>   
> -		nand_chip->ecc.steps = host->pmecc_sector_number;
>   		nand_chip->ecc.strength = cap;
>   		nand_chip->ecc.bytes = host->pmecc_bytes_per_sector;
> -		nand_chip->ecc.total = host->pmecc_bytes_per_sector *
> -				       host->pmecc_sector_number;
> +		nand_chip->ecc.steps = mtd->writesize / sector_size;
> +		nand_chip->ecc.total = nand_chip->ecc.bytes *
> +			nand_chip->ecc.steps;
>   		if (nand_chip->ecc.total > mtd->oobsize - 2) {
>   			dev_err(host->dev, "No room for ECC bytes\n");
>   			err_no = -EINVAL;

  parent reply	other threads:[~2014-09-17  8:33 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-08  9:12 [PATCH 1/2] mtd: atmel_nand: remove pmecc_sector_number, use ecc.steps instead Josh Wu
2014-08-08  9:12 ` [PATCH 2/2] mtd: atmel_nand: remove pmecc_bytes_per_sector, use chip->ecc.bytes instead Josh Wu
2014-09-17  8:33 ` Josh Wu [this message]
2014-09-18  6:12 ` [PATCH 1/2] mtd: atmel_nand: remove pmecc_sector_number, use ecc.steps instead Brian Norris

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=5419473D.7060007@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.