From: Stephen Street <stephen@streetfiresound.com>
To: Nicolas Pitre <nico@cam.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
dvrabel@arcom.com, David Brownell <david-b@pacbell.net>,
spi-devel-general@lists.sourceforge.net,
Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH] spi: Updated PXA2xx SSP SPI Driver
Date: Fri, 10 Feb 2006 15:22:48 -0800 [thread overview]
Message-ID: <1139613768.30189.139.camel@ststephen.streetfiresound.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0602101732590.5397@localhost.localdomain>
On Fri, 2006-02-10 at 17:45 -0500, Nicolas Pitre wrote:
>
> Actually, it will do almost the same as you originally did if you look
> at its definition. However, because a solution needs to be implemented
> to support multiple ports then using __raw_readl() at the driver level
> is more familiar to other kernel people.
>
Yea, I did notice that also. I just wanted to make sure I understood
what is going on so that I do not make the same mistake for the third
time.
> In fact, if there was only one SSP port, I'd have asked you to use
> SSPCR0, SSPDR, etc. directly. But the fact that the driver can handle
> multiple ports makes it rather messy (and the SSP*_P() macros in
> pxa-regs.h are an abomination IMHO).
>
I did not use the SSP*_P functions because of the mess. Actually at one
point the driver implemented register accesses in similar manner as
SSP*_P but David Brownell got me straightened out. Thus the original
question.
Stephen
next prev parent reply other threads:[~2006-02-10 23:22 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-07 3:06 [PATCH] spi: Add " stephen
2006-02-07 4:22 ` [PATCH] pxa2xx_spi, board support for Lubbock David Brownell
2006-02-07 11:50 ` [PATCH] spi: Add PXA2xx SSP SPI Driver David Vrabel
2006-02-07 15:05 ` David Vrabel
2006-02-07 21:27 ` Stephen Street
2006-02-07 21:17 ` Stephen Street
2006-02-10 1:38 ` [PATCH] spi: Updated " Stephen Street
2006-02-10 2:18 ` Andrew Morton
2006-02-10 23:07 ` Stephen Street
2006-02-10 23:49 ` Andrew Morton
2006-02-10 17:40 ` Nicolas Pitre
2006-02-10 22:19 ` Stephen Street
2006-02-10 22:45 ` Nicolas Pitre
2006-02-10 23:22 ` Stephen Street [this message]
2006-02-14 1:35 ` [PATCH] spi: Code Review " Stephen Street
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=1139613768.30189.139.camel@ststephen.streetfiresound.com \
--to=stephen@streetfiresound.com \
--cc=akpm@osdl.org \
--cc=david-b@pacbell.net \
--cc=dvrabel@arcom.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.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
all inboxes | Powered by JetHome®