From: Artem Bityutskiy <dedekind1@gmail.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
"ryan@bluewatersys.com" <ryan@bluewatersys.com>,
"andre@bluewatersys.com" <andre@bluewatersys.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] sst25l.c: simplify reading the device ManID/DevID
Date: Thu, 29 Apr 2010 08:36:38 +0300 [thread overview]
Message-ID: <1272519398.7750.67.camel@localhost> (raw)
In-Reply-To: <0D753D10438DA54287A00B0270842697636D85BD7C@AUSP01VMBX24.collaborationhost.net>
On Tue, 2010-04-20 at 18:17 -0500, H Hartley Sweeten wrote:
> The Read-ID command will continuously output the Manufacture ID and Device ID
> until the command is terminated by a low to high transition on the CE# pin.
> We can take advantage of this in the sst25l_match_device routine by reading
> both bytes in one spi_write_then_read transaction.
>
> Signed-off-by: H Hartley Sweeten <hsweeten@visionengravers.com>
> Cc: David Woodhouse <dwmw2@infradead.org>
> Cc: Andre Renaud <andre@bluewatersys.com>
> Cc: Ryan Mallon <ryan@bluewatersys.com>
Pushed to l2-mtd-2.6.git / dunno.
--
Best Regards,
Artem Bityutskiy (Артём Битюцкий)
next prev parent reply other threads:[~2010-04-29 5:36 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-20 23:17 [PATCH] sst25l.c: simplify reading the device ManID/DevID H Hartley Sweeten
2010-04-20 23:17 ` H Hartley Sweeten
2010-04-29 5:36 ` Artem Bityutskiy [this message]
2010-04-29 17:11 ` H Hartley Sweeten
2010-04-29 17:11 ` H Hartley Sweeten
2010-04-29 18:07 ` Artem Bityutskiy
2010-04-29 18:07 ` Artem Bityutskiy
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=1272519398.7750.67.camel@localhost \
--to=dedekind1@gmail.com \
--cc=andre@bluewatersys.com \
--cc=dwmw2@infradead.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=ryan@bluewatersys.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.