From: Ben Gamari <bgamari@gmail.com>
To: Ben Gamari <bgamari@gmail.com>
Cc: Ben Dooks <ben@simtec.co.uk>,
beagleboard <beagleboard@googlegroups.com>,
linux-omap <linux-omap@vger.kernel.org>,
David Brownell <dbrownell@users.sourceforge.net>,
Eric Miao <eric.miao@marvell.com>,
Michael Hennerich <michael.hennerich@analog.com>,
Grant Likely <grant.likely@secretlab.ca>,
spi-devel-general <spi-devel-general@lists.sourceforge.net>
Subject: Re:
Date: Fri, 22 Jan 2010 10:53:10 -0500 [thread overview]
Message-ID: <1264175450-sup-1219@ben-laptop> (raw)
In-Reply-To: <1264016711-sup-309@ben-laptop>
Excerpts from Ben Gamari's message of Wed Jan 20 14:47:23 -0500 2010:
> Bcc:
> Subject: GPIO chip select support in omap2_mcspi driver
>
> It seems like the rough idea is to add a cs_gpio field to the device
> struct (omap2_mcspi) and add the appropriate code to the
> omap2_mcspi_force_cs() to bring cs_gpio high or low if it is valid. The
> potential problem I can see with this is that omap2_mcspi_set_enable()
> is called to enable the channel before the force_cs() is called (in
> omap2_mcspi_work()). If I'm interpreting the documentation correctly,
> the enable bit starts the clocks, meaning that the chip will begin
> clocking out data before CS is brought high. I must be missing something
> here, no?
Could someone comment on how this ordering works? As I said, it seems to
me like the SPI controller starts sending before CS is brought high.
I would appreciate any feedback. Thanks!
- Ben
next prev parent reply other threads:[~2010-01-22 15:53 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-20 19:47 (no subject) Ben Gamari
2010-01-21 0:04 ` Ben Dooks
2010-01-21 0:04 ` Re: Ben Dooks
2010-01-21 0:04 ` (no subject) Ben Dooks
2010-01-22 15:53 ` Ben Gamari [this message]
2010-01-28 4:10 ` McSPI questions pertaining to GPIO chip select support Ben Gamari
2010-01-28 4:15 ` Bill Gatliff
2010-01-28 4:25 ` Ben Gamari
2010-01-28 4:27 ` Bill Gatliff
2010-01-28 4:33 ` jassi brar
2010-12-21 17:56 ` [RFC PATCH] GPIO chip select support for McSPI Ben Gamari
2010-12-21 17:56 ` [PATCH] mcspi: Add support for GPIO chip select lines Ben Gamari
2010-12-23 19:59 ` Tony Lindgren
2010-12-23 21:38 ` Grant Likely
2010-12-23 23:09 ` Ben Gamari
2010-12-24 0:37 ` Grant Likely
2010-12-24 2:27 ` Ben Gamari
2010-12-24 3:28 ` Grant Likely
2010-12-24 6:05 ` Ben Gamari
2011-02-12 8:33 ` Grant Likely
2011-02-13 22:07 ` Ben Gamari
2011-08-30 10:14 ` McSPI questions pertaining to GPIO chip select support Raju Sana
2011-08-30 13:50 ` Ben Gamari
2011-08-30 13:50 ` [PATCH] mcspi: Add support for GPIO chip select lines Ben Gamari
2011-08-30 13:52 ` [PATCH] beagledaq: Hack in cs_gpios Ben Gamari
[not found] ` <1314712343-27367-1-git-send-email-bgamari.foss-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2011-09-05 12:42 ` Raju Sana
-- strict thread matches above, loose matches on Subject: below --
2020-02-06 2:24 Viviane Jose Pereira
2014-12-06 13:18 Re: Quan Han
2012-07-31 23:52 (unknown), Ricardo Neri
2012-07-31 23:58 ` Ricardo Neri
2011-12-13 2:58 Re: Matt Shaw
2011-02-16 11:53 (unknown), Hema HK
2011-02-16 12:00 ` Sergei Shtylyov
[not found] ` <4D5BBC61.2000905-hkdhdckH98+B+jHODAdFcQ@public.gmane.org>
2011-02-16 12:17 ` Hema Kalliguddi
2010-07-20 0:22 wins
2010-07-07 18:15 Coca Cola Promo
2010-04-29 2:49 RE: ABC MICROFINANCE BANK (NIG)
2009-12-05 22:29 RE: Irish News Center
2009-08-25 10:34 (unknown), Syed Rafiuddin
2009-08-26 11:10 ` Ben Dooks
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=1264175450-sup-1219@ben-laptop \
--to=bgamari@gmail.com \
--cc=beagleboard@googlegroups.com \
--cc=ben@simtec.co.uk \
--cc=dbrownell@users.sourceforge.net \
--cc=eric.miao@marvell.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-omap@vger.kernel.org \
--cc=michael.hennerich@analog.com \
--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