From: David Brownell <david-b@pacbell.net>
To: Kumar Gala <galak@kernel.crashing.org>
Cc: spi-devel-general@lists.sourceforge.net,
linux kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: [spi-devel-general] Re: question on spi_bitbang
Date: Fri, 31 Mar 2006 13:15:13 -0800 [thread overview]
Message-ID: <200603311315.14408.david-b@pacbell.net> (raw)
In-Reply-To: <A164CF6D-0330-46A7-ABF2-87127753E048@kernel.crashing.org>
On Friday 31 March 2006 12:52 pm, Kumar Gala wrote:
> What I'm looking at is the following:
>
> * use spi_bitbang_setup() as is
> * have my chipselect do:
> if (BITBANG_CS_INACTIVE)
> deassert GPIO pin for CS
> else
> set HW mode register (polarity, phase, bit length)
> assert GPIO pin for CS
> * setup_transfer()
> * set HW mode register (bit length)
> * call bitbang_setup_transfer()
And export bitbang_setup_transfer()? I guess that makes sense,
but you should probably rename it then to match the convention for
the other exported symbols.
Once that's all working, please submit the relevant patch.
- Dave
next prev parent reply other threads:[~2006-03-31 21:15 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-31 17:31 question on spi_bitbang Kumar Gala
2006-03-31 18:11 ` David Brownell
2006-03-31 18:19 ` [spi-devel-general] " Stephen Street
2006-03-31 19:16 ` David Brownell
2006-03-31 19:07 ` Kumar Gala
2006-03-31 19:17 ` Kumar Gala
2006-03-31 19:32 ` [spi-devel-general] " David Brownell
2006-03-31 20:00 ` Kumar Gala
2006-03-31 20:36 ` David Brownell
2006-03-31 20:52 ` Kumar Gala
2006-03-31 21:15 ` David Brownell [this message]
2006-03-31 22:11 ` Kumar Gala
2006-03-31 22:20 ` David Brownell
2006-03-31 23:58 ` Kumar Gala
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=200603311315.14408.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=galak@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.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 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.