From: Marek Vasut <marex@denx.de>
To: grmoore@altera.com
Cc: ggrahammoore@gmail.com,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Jingoo Han <jg1.han@samsung.com>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
linux-kernel@vger.kernel.org,
Yves Vandervennet <rocket.yvanderv@gmail.com>,
linux-mtd@lists.infradead.org,
Insop Song <insop.song@gainspeed.com>,
Alan Tull <atull@altera.com>,
Sourav Poddar <sourav.poddar@ti.com>,
Brian Norris <computersforpeace@gmail.com>,
David Woodhouse <dwmw2@infradead.org>,
Dinh Nguyen <dinguyen@altera.com>
Subject: Re: [PATCH V2] Add support for flag status register on Micron chips.
Date: Sun, 13 Apr 2014 19:18:45 +0200 [thread overview]
Message-ID: <201404131918.45753.marex@denx.de> (raw)
In-Reply-To: <1397228593-17996-1-git-send-email-grmoore@altera.com>
On Friday, April 11, 2014 at 05:03:13 PM, grmoore@altera.com wrote:
[...]
> diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
> index ad19139..4cddbc8 100644
> --- a/drivers/mtd/devices/m25p80.c
> +++ b/drivers/mtd/devices/m25p80.c
> @@ -39,6 +39,7 @@
> #define OPCODE_WREN 0x06 /* Write enable */
> #define OPCODE_RDSR 0x05 /* Read status register */
> #define OPCODE_WRSR 0x01 /* Write status register 1 byte
*/
> +#define OPCODE_RDFSR 0x70 /* read flag status register */
I know this is not your fault, but can you please indent this properly with
tabs?
> #define OPCODE_NORM_READ 0x03 /* Read data bytes (low
frequency) */
> #define OPCODE_FAST_READ 0x0b /* Read data bytes (high
frequency) */
> #define OPCODE_QUAD_READ 0x6b /* Read data bytes */
And fix this one in a separate patch to use tabs as well please ?
[...]
> @@ -790,7 +847,7 @@ static int m25p80_unlock(struct mtd_info *mtd, loff_t
> ofs, uint64_t len)
>
> mutex_lock(&flash->lock);
> /* Wait until finished previous command */
> - if (wait_till_ready(flash)) {
> + if (flash->wait_till_ready(flash)) {
I wonder, can't wait_till_ready() be made a wrapper that will check the USE_FSR
flag and call correct wait-function ? This would avoid adding a new member to
*flash and also would avoid so many changes throughout the code. What do you
think?
[...]
Best regards,
Marek Vasut
WARNING: multiple messages have this Message-ID (diff)
From: Marek Vasut <marex@denx.de>
To: grmoore@altera.com
Cc: ggrahammoore@gmail.com, David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
Sourav Poddar <sourav.poddar@ti.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Geert Uytterhoeven <geert+renesas@linux-m68k.org>,
Jingoo Han <jg1.han@samsung.com>,
Insop Song <insop.song@gainspeed.com>,
linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org,
Alan Tull <atull@altera.com>, Dinh Nguyen <dinguyen@altera.com>,
Yves Vandervennet <rocket.yvanderv@gmail.com>
Subject: Re: [PATCH V2] Add support for flag status register on Micron chips.
Date: Sun, 13 Apr 2014 19:18:45 +0200 [thread overview]
Message-ID: <201404131918.45753.marex@denx.de> (raw)
In-Reply-To: <1397228593-17996-1-git-send-email-grmoore@altera.com>
On Friday, April 11, 2014 at 05:03:13 PM, grmoore@altera.com wrote:
[...]
> diff --git a/drivers/mtd/devices/m25p80.c b/drivers/mtd/devices/m25p80.c
> index ad19139..4cddbc8 100644
> --- a/drivers/mtd/devices/m25p80.c
> +++ b/drivers/mtd/devices/m25p80.c
> @@ -39,6 +39,7 @@
> #define OPCODE_WREN 0x06 /* Write enable */
> #define OPCODE_RDSR 0x05 /* Read status register */
> #define OPCODE_WRSR 0x01 /* Write status register 1 byte
*/
> +#define OPCODE_RDFSR 0x70 /* read flag status register */
I know this is not your fault, but can you please indent this properly with
tabs?
> #define OPCODE_NORM_READ 0x03 /* Read data bytes (low
frequency) */
> #define OPCODE_FAST_READ 0x0b /* Read data bytes (high
frequency) */
> #define OPCODE_QUAD_READ 0x6b /* Read data bytes */
And fix this one in a separate patch to use tabs as well please ?
[...]
> @@ -790,7 +847,7 @@ static int m25p80_unlock(struct mtd_info *mtd, loff_t
> ofs, uint64_t len)
>
> mutex_lock(&flash->lock);
> /* Wait until finished previous command */
> - if (wait_till_ready(flash)) {
> + if (flash->wait_till_ready(flash)) {
I wonder, can't wait_till_ready() be made a wrapper that will check the USE_FSR
flag and call correct wait-function ? This would avoid adding a new member to
*flash and also would avoid so many changes throughout the code. What do you
think?
[...]
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-13 22:03 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 15:03 [PATCH V2] Add support for flag status register on Micron chips grmoore
2014-04-11 15:03 ` grmoore
2014-04-11 15:57 ` Huang Shijie
2014-04-11 15:57 ` Huang Shijie
2014-04-13 17:18 ` Marek Vasut [this message]
2014-04-13 17:18 ` Marek Vasut
2014-04-14 16:19 ` Graham Moore
2014-04-14 16:19 ` Graham Moore
2014-04-14 18:29 ` Marek Vasut
2014-04-14 18:29 ` Marek Vasut
2014-04-14 15:41 ` Harini Katakam
2014-04-14 15:41 ` Harini Katakam
2014-04-14 18:28 ` Marek Vasut
2014-04-14 18:28 ` Marek Vasut
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=201404131918.45753.marex@denx.de \
--to=marex@denx.de \
--cc=artem.bityutskiy@linux.intel.com \
--cc=atull@altera.com \
--cc=computersforpeace@gmail.com \
--cc=dinguyen@altera.com \
--cc=dwmw2@infradead.org \
--cc=geert+renesas@linux-m68k.org \
--cc=ggrahammoore@gmail.com \
--cc=grmoore@altera.com \
--cc=insop.song@gainspeed.com \
--cc=jg1.han@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=rocket.yvanderv@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sourav.poddar@ti.com \
/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.