From: Stephen Street <stephen@streetfiresound.com>
To: David Brownell <david-b@pacbell.net>
Cc: eemike@gmail.com, Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH/RFC] simple SPI controller on PXA2xx SSP port, refresh
Date: Fri, 04 Nov 2005 10:52:45 -0800 [thread overview]
Message-ID: <1131130365.426.33.camel@localhost.localdomain> (raw)
In-Reply-To: <200511031615.22630.david-b@pacbell.net>
On Thu, 2005-11-03 at 16:15 -0800, David Brownell wrote:
> Stephen persuaded me to add controller_data too, which is stored in
> "struct spi_device". His PXA SPI controller driver uses that for a
> structure holding what I'd call DMA tuning information, plus a function
> that tweaks the GPIO used for a chipselect. Treat it as readonly.
>
> Controller drivers can have two different kinds of state in each
> spi_device: static, and dynamic/runtime. The names used for them
> are IMO very confusing (platform_data and controller_data) since
> they don't mean the same as those names do in board_info. I'd take
> a patch to provide better names for those two. :)
I agree, the names are bad... How about modifying struct spi_board_info
to
struct spi_board_info {
...
void *slave_data;
void *master_data;
...
};
-Stephen
next prev parent reply other threads:[~2005-11-04 18:52 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-04 0:15 [PATCH/RFC] simple SPI controller on PXA2xx SSP port, refresh David Brownell
2005-11-04 18:52 ` Stephen Street [this message]
2005-11-04 20:16 ` David Brownell
2005-11-04 23:38 ` Stephen Street
2005-11-05 0:54 ` David Brownell
2005-11-05 2:28 ` Stephen Street
2005-11-05 20:58 ` David Brownell
-- strict thread matches above, loose matches on Subject: below --
2005-10-25 23:48 stephen
2005-10-27 11:33 ` Mike Lee
2005-10-27 16:41 ` Stephen Street
2005-10-29 18:25 ` Mike Lee
2005-11-01 18:35 ` Stephen Street
2005-11-03 9:37 ` Mike Lee
2005-11-04 18:11 ` Stephen Street
2005-11-04 20:36 ` Mark Underwood
2005-11-07 20:43 ` Mark Underwood
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=1131130365.426.33.camel@localhost.localdomain \
--to=stephen@streetfiresound.com \
--cc=david-b@pacbell.net \
--cc=eemike@gmail.com \
--cc=linux-kernel@vger.kernel.org \
/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