From: Grant Likely <grant.likely@secretlab.ca>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: "Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
David Brownell <david-b@pacbell.net>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
David Woodhouse <dwmw2@infradead.org>
Subject: Re: [PATCH] mtd: sst25l: fix reads with broken spi-masters
Date: Fri, 14 Jan 2011 15:24:01 -0700 [thread overview]
Message-ID: <20110114222401.GA10504@angua.secretlab.ca> (raw)
In-Reply-To: <0D753D10438DA54287A00B027084269764CDF41635@AUSP01VMBX24.collaborationhost.net>
On Mon, Jan 10, 2011 at 04:36:50PM -0600, H Hartley Sweeten wrote:
> On Monday, January 10, 2011 3:20 PM, David Brownell wrote:
> > --- On Mon, 1/10/11, H Hartley Sweeten <hartleys@visionengravers.com> wrote:
> > NAK. I'm surprised you even thought to submit
> > such a clearly-wrong patch.
> >
> > The bug is in the SPI master driver, and thus
> > so should the fix be. Or make your system use
> > the GPIO based SPI master driver.
>
> Sorry.
>
> The bug _is_ in the spi peripheral on the ep93xx.
>
> Unfortunately, hardware does exist that uses the SFRMOUT signal as part of
> the chip select to access the device. The only way to get this signal to
> do anything is by using the spi peripheral. The SFRMOUT signal cannot be
> accessed using GPIO so the GPIO based SPI master driver is not an option.
No, David is correct. The fault is in the master driver. It is perfectly valid (and common) for spi peripherals to required the SS line to remain asserted over the entire transfer. Unfortunately, it is also as common for spi master devices to not support this mode in hardware.
However, the fault is with the spi master hardware, and therefore it is the responsibility of the master driver to handle the buffering and magic required so that the transfer proceeds correctly.
g.
next prev parent reply other threads:[~2011-01-14 22:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-10 21:21 [PATCH] mtd: sst25l: fix reads with broken spi-masters H Hartley Sweeten
2011-01-10 22:20 ` David Brownell
2011-01-10 22:36 ` H Hartley Sweeten
2011-01-14 22:24 ` Grant Likely [this message]
2011-01-14 22:34 ` David Brownell
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=20110114222401.GA10504@angua.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=Artem.Bityutskiy@nokia.com \
--cc=david-b@pacbell.net \
--cc=dwmw2@infradead.org \
--cc=hartleys@visionengravers.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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