From: Marek Vasut <marex@denx.de>
To: Huang Shijie <shijie8@gmail.com>
Cc: Huang Shijie <b32955@freescale.com>, Gerhard Sittig <gsi@denx.de>,
computersforpeace@gmail.com, linux-mtd@lists.infradead.org,
dwmw2@infradead.org
Subject: Re: [PATCH] mtd: spi-nor: fix the wrong dummy value
Date: Thu, 17 Apr 2014 16:15:12 +0200 [thread overview]
Message-ID: <201404171615.12880.marex@denx.de> (raw)
In-Reply-To: <20140417134127.GA3980@localhost.localdomain>
On Thursday, April 17, 2014 at 03:41:29 PM, Huang Shijie wrote:
> On Wed, Apr 16, 2014 at 10:08:49PM +0200, Gerhard Sittig wrote:
> > On Wed, 2014-04-16 at 16:18 +0800, Huang Shijie wrote:
> > > The dummy cycles is actually 8 for SPI fast/dual/quad read.
> > >
> > > This patch fixes the wrong dummy value for both the spi-nor.c and
> > > m25p80.c.
> > >
> > > Signed-off-by: Huang Shijie <b32955@freescale.com>
> > > ---
> > >
> > > drivers/mtd/devices/m25p80.c | 3 +++
> > > drivers/mtd/spi-nor/spi-nor.c | 2 +-
> > > 2 files changed, 4 insertions(+), 1 deletions(-)
> > >
> > > diff --git a/drivers/mtd/devices/m25p80.c
> > > b/drivers/mtd/devices/m25p80.c index 1557d8f..112ca8b 100644
> > > --- a/drivers/mtd/devices/m25p80.c
> > > +++ b/drivers/mtd/devices/m25p80.c
> > > @@ -131,6 +131,9 @@ static int m25p80_read(struct spi_nor *nor, loff_t
> > > from, size_t len,
> > >
> > > int dummy = nor->read_dummy;
> > > int ret;
> > >
> > > + /* convert the dummy cycles to the number of byte */
> > > + dummy >>= 3;
> > > +
> >
> > "dummy /= 8" to match the comment / commit message, and for
> > better mental association with a byte's width and the below
> > return value?
>
> The disassemble code for "int dummy = 8; dummy /= 8;" is:
> --------------------------------------------------
> 83a6: 2308 movs r3, #8
> 83a8: 607b str r3, [r7, #4]
> 83aa: 687b ldr r3, [r7, #4]
> 83ac: 1dda adds r2, r3, #7
> 83ae: 2b00 cmp r3, #0
> 83b0: bfb4 ite lt
> 83b2: 4613 movlt r3, r2
> 83b4: 461b movge r3, r3
> 83b6: 10db asrs r3, r3, #3
> 83b8: 607b str r3, [r7, #4]
> --------------------------------------------------
>
> The disassemble code for "int dummy = 8; dummy >>= 3;" is:
> --------------------------------------------------
> 83a6: 2308 movs r3, #8
> 83a8: 607b str r3, [r7, #4]
> 83aa: 687b ldr r3, [r7, #4]
> 83ac: 10db asrs r3, r3, #3
> 83ae: 607b str r3, [r7, #4]
> --------------------------------------------------
>
> Obviously, the "dummy >>= 3" is faster then "dummy /= 8".
Which GCC compiler is that please ? I'm surprised GCC doesn't optimize it.
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-04-17 15:45 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-16 8:18 [PATCH] mtd: spi-nor: fix the wrong dummy value Huang Shijie
2014-04-16 20:08 ` Gerhard Sittig
2014-04-17 4:59 ` Huang Shijie
2014-04-17 11:30 ` Marek Vasut
2014-04-17 13:41 ` Huang Shijie
2014-04-17 14:15 ` Marek Vasut [this message]
2014-04-17 15:55 ` Gerhard Sittig
2014-04-17 15:57 ` Huang Shijie
2014-04-17 18:12 ` Marek Vasut
2014-04-16 23:40 ` Marek Vasut
2014-04-17 5:01 ` Huang Shijie
2014-04-17 11:32 ` Marek Vasut
2014-04-17 12:59 ` Huang Shijie
2014-04-17 14:15 ` 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=201404171615.12880.marex@denx.de \
--to=marex@denx.de \
--cc=b32955@freescale.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=gsi@denx.de \
--cc=linux-mtd@lists.infradead.org \
--cc=shijie8@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox