From: Marek Vasut <marex@denx.de>
To: bpqw <bpqw@micron.com>
Cc: "dwmw2@infradead.org" <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
"shijie8@gmail.com" <shijie8@gmail.com>,
"geert+renesas@glider.be" <geert+renesas@glider.be>,
"grmoore@altera.com" <grmoore@altera.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/1] driver:mtd:spi-nor: Add Micron quad I/O support
Date: Fri, 26 Sep 2014 10:46:07 +0200 [thread overview]
Message-ID: <201409261046.07132.marex@denx.de> (raw)
In-Reply-To: <A765B125120D1346A63912DDE6D8B6315DCDF1@NTXXIAMBX02.xacn.micron.com>
On Friday, September 26, 2014 at 10:39:38 AM, bpqw wrote:
> >> + /* set EVCR ,enable quad I/O */
> >> + nor->cmd_buf[0] = val & ~EVCR_QUAD_EN_MICRON;
> >> + ret = nor->write_reg(nor, SPINOR_OP_WD_EVCR, nor->cmd_buf, 1, 0);
> >> + if (ret < 0) {
> >> + dev_err(nor->dev,
> >> + "error while writing EVCR register\n");
> >> + return -EINVAL;
> >> + }
> >> +
> >> + if (wait_till_ready(nor))
> >> + return 1;
> >
> >Why does this not return proper error code or even better, return value
> >from wait_till_ready() ?
> >
> >Other than that, there's nothing wrong with the patch I think.
>
> Hi,Marek
> Thanks for your review,you can find the same usage in the spi-nor.c.
> Below method is OK? Or you can give me some suggestion.
>
> if (wait_till_ready(nor))
> return - EINVAL;
ret = wait_till_readynor()
if (ret)
return ret;
But all right, this means the subsystem isn't perfect. Well, others, what do you
think ?
Best regards,
Marek Vasut
next prev parent reply other threads:[~2014-09-26 8:46 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 6:20 [PATCH 1/1] driver:mtd:spi-nor: Add Micron quad I/O support bpqw
2014-09-25 10:11 ` Marek Vasut
2014-09-26 8:39 ` bpqw
2014-09-26 8:46 ` Marek Vasut [this message]
2014-09-28 1:59 ` [PATCH 1/1 v2] " bpqw
2014-09-28 22:43 ` Marek Vasut
2014-09-29 0:30 ` bpqw
2014-09-29 18:57 ` Marek Vasut
2014-09-30 2:47 ` [PATCH 1/1 v3] " Bean Huo 霍斌斌 (beanhuo)
2014-09-30 13:38 ` Marek Vasut
2014-10-01 14:24 ` Bean Huo 霍斌斌 (beanhuo)
2014-10-01 14:32 ` Marek Vasut
2014-10-01 14:28 ` bpqw
2014-10-01 14:33 ` Marek Vasut
2014-10-04 5:55 ` bpqw
2014-10-16 1:53 ` bpqw
2014-10-17 0:37 ` Bean Huo 霍斌斌 (beanhuo)
2014-10-20 1:24 ` bpqw
2014-10-23 0:58 ` Bean Huo 霍斌斌 (beanhuo)
2014-10-24 0:31 ` Bean Huo 霍斌斌 (beanhuo)
2014-10-27 0:09 ` [PATCH 1/1 v3] driver:mtd:spi-nor: Add quad I/O support for Micron spi nor bpqw
2014-10-30 14:31 ` bpqw
2014-11-12 20:59 ` Jagan Teki
2014-11-04 13:25 ` [PATCH 1/1 v4] " bpqw
2014-11-05 11:26 ` Brian Norris
2014-11-06 2:56 ` bpqw
2014-11-06 3:09 ` [V5 PATCH 1/1] " bpqw
[not found] ` <54613259.4070903@opensource.altera.com>
2014-11-11 19:41 ` Graham Moore
2014-11-11 21:55 ` Jagan Teki
2014-11-12 1:19 ` bpqw
2014-11-12 0:58 ` bpqw
2014-11-13 16:26 ` Graham Moore
2014-11-14 2:06 ` bpqw
2014-11-26 4:06 ` Brian Norris
2014-11-26 16:08 ` bpqw
2014-11-26 21:12 ` Brian Norris
2014-11-27 5:55 ` bpqw
2014-11-27 9:14 ` Brian Norris
2014-11-30 16:11 ` Bean Huo 霍斌斌 (beanhuo)
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=201409261046.07132.marex@denx.de \
--to=marex@denx.de \
--cc=bpqw@micron.com \
--cc=computersforpeace@gmail.com \
--cc=dwmw2@infradead.org \
--cc=geert+renesas@glider.be \
--cc=grmoore@altera.com \
--cc=linux-kernel@vger.kernel.org \
--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