From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: Jean-Louis Thekekara <jeanlouis.thekekara@parrot.com>
Cc: <linux-mtd@lists.infradead.org>
Subject: Re: [PATCH] mtd: nand: remove hard-coded NAND ids length
Date: Fri, 4 Aug 2017 10:31:22 +0200 [thread overview]
Message-ID: <20170804103122.6542fde5@bbrezillon> (raw)
In-Reply-To: <20170629170830.8084-1-jeanlouis.thekekara@parrot.com>
On Thu, 29 Jun 2017 19:08:30 +0200
Jean-Louis Thekekara <jeanlouis.thekekara@parrot.com> wrote:
> This commit removes hard-coded '8' used for looping into
> struct nand_chip.id.data array.
>
> NAND_MAX_ID_LEN has been introduced by Artem Bityutskiy in
> 53552d22bfe1f for defining ids length in nand_flash_ids[] list.
>
> This commit unifies ids length in nand base driver.
>
Applied.
Thanks,
Boris
> Signed-off-by: Jean-Louis Thekekara <jeanlouis.thekekara@parrot.com>
> ---
> drivers/mtd/nand/nand_base.c | 4 ++--
> include/linux/mtd/nand.h | 10 +++++-----
> 2 files changed, 7 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c
> index 85edac9b2bb5..66db2ced87ad 100644
> --- a/drivers/mtd/nand/nand_base.c
> +++ b/drivers/mtd/nand/nand_base.c
> @@ -4056,7 +4056,7 @@ static int nand_detect(struct nand_chip *chip, struct nand_flash_dev *type)
> chip->cmdfunc(mtd, NAND_CMD_READID, 0x00, -1);
>
> /* Read entire ID string */
> - for (i = 0; i < 8; i++)
> + for (i = 0; i < ARRAY_SIZE(chip->id.data); i++)
> id_data[i] = chip->read_byte(mtd);
>
> if (id_data[0] != maf_id || id_data[1] != dev_id) {
> @@ -4065,7 +4065,7 @@ static int nand_detect(struct nand_chip *chip, struct nand_flash_dev *type)
> return -ENODEV;
> }
>
> - chip->id.len = nand_id_len(id_data, 8);
> + chip->id.len = nand_id_len(id_data, ARRAY_SIZE(chip->id.data));
>
> /* Try to identify manufacturer */
> manufacturer = nand_get_manufacturer(maf_id);
> diff --git a/include/linux/mtd/nand.h b/include/linux/mtd/nand.h
> index dc8fbc033442..c3c1a32a5ade 100644
> --- a/include/linux/mtd/nand.h
> +++ b/include/linux/mtd/nand.h
> @@ -449,14 +449,16 @@ struct nand_jedec_params {
> __le16 crc;
> } __packed;
>
> +/* The maximum expected count of bytes in the NAND ID sequence */
> +#define NAND_MAX_ID_LEN 8
> +
> /**
> * struct nand_id - NAND id structure
> - * @data: buffer containing the id bytes. Currently 8 bytes large, but can
> - * be extended if required.
> + * @data: buffer containing the id bytes.
> * @len: ID length.
> */
> struct nand_id {
> - u8 data[8];
> + u8 data[NAND_MAX_ID_LEN];
> int len;
> };
>
> @@ -1028,8 +1030,6 @@ static inline void *nand_get_manufacturer_data(struct nand_chip *chip)
> #define NAND_MFR_ATO 0x9b
> #define NAND_MFR_WINBOND 0xef
>
> -/* The maximum expected count of bytes in the NAND ID sequence */
> -#define NAND_MAX_ID_LEN 8
>
> /*
> * A helper for defining older NAND chips where the second ID byte fully
prev parent reply other threads:[~2017-08-04 8:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-29 17:08 [PATCH] mtd: nand: remove hard-coded NAND ids length Jean-Louis Thekekara
2017-07-02 14:40 ` Boris Brezillon
2017-08-04 8:31 ` Boris Brezillon [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=20170804103122.6542fde5@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=jeanlouis.thekekara@parrot.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox