mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nicolas Pitre <nico@cam.org>
To: Stephen Street <stephen@streetfiresound.com>
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 12:40:52 -0500 (EST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0602101102520.5397@localhost.localdomain> (raw)
In-Reply-To: <1139535480.30189.30.camel@ststephen.streetfiresound.com>

On Thu, 9 Feb 2006, Stephen Street wrote:

> Sorry for the delay in posting this.  My workstation crashed on Tuesday
> and I'm still recovering.
> 
> Attached is an updated patch to add SPI master controller for PXA2xx
> boards.  This update includes fixes for the PXA27x CPU to correctly
> handle the differences peripheral clock speeds with in the PXA2xx
> family.
> 
> I have tested the driver extensively on the PXA255 NSSP port.  My
> application includes a 3 slave chip SPI bus configuration which I have
> driven under load (44850+ bytes per second).  Everything appears to work
> great.  I also implemented a sample loopback driver (please e-mail me
> directly if you are interested the loopback driver) for testing purposes
> and used it to test the driver on the PXA255 SSP port.
> 
> It would be nice is additional eyes review my implementation as I only
> have access to a custom PXA255 board.  Any feedback or word of success
> would be greatly appreciated!

[...]

+#define SSP_REG(x) (*((volatile unsigned long *)x))

Don't do that.  Instead, please use:

#define DEFINE_SSP_REG(reg, off) \
static inline u32 read_##reg(void *p) { return __raw_readl(p + (off)); \
static inline void write_##reg(u32 v, void *p) { __raw_writel(v, p + (off)); }

DEFINE_SSP_REG(SSCR0,	0x00)
DEFINE_SSP_REG(SSCR1,	0x04)
DEFINE_SSP_REG(SSSR,	0x08)
DEFINE_SSP_REG(SSITR,	0x0c)
DEFINE_SSP_REG(SSDR,	0x10)
DEFINE_SSP_REG(SSTO,	0x28)
DEFINE_SSP_REG(SSPSP,	0x2c)

[...]
+	/* SSP register addresses */
+	u32 sscr0;
+	u32 sscr1;
+	u32 sssr;
+	u32 ssitr;
+	u32 ssdr;
+	u32 ssdr_physical;
+	u32 ssto;
+	u32 Bsspsp;

And then you'll only need to store the base address for each port:

	void *ioaddr;

[...]
+static inline void flush(struct driver_data *drv_data)
+{
+       u32 sssr = drv_data->sssr;
+       u32 ssdr = drv_data->ssdr;
+
+       do {
+               while (SSP_REG(sssr) & SSSR_RNE) {
+                       (void)SSP_REG(ssdr);
+               }
+       } while (SSP_REG(sssr) & SSSR_BSY);
+       SSP_REG(sssr) = SSSR_ROR ;
+}

Then it would become:

static inline void flush(struct driver_data *drv_data)
{
	void *reg = drv_data->ioaddr;

	do {
		while (read_SSSR(reg) & SSSR_RNE)
			read_SSDR(reg);
       } while (read_SSSR(reg) & SSSR_BSY);
       write_SSSR(SSSR_ROR, reg);
}

This will make your structure smaller, and gcc will be able to produce 
much smaller and better code due to less register pressure and constant 
base offsets.  It also make the source a bit more readable with fewer
possibilities for errors like:

+static void dma_handler(int channel, void *data, struct pt_regs *regs)
+{
+       struct driver_data *drv_data = (struct driver_data *)data;
+       struct spi_message *msg = drv_data->cur_msg;
+       u32 sssr = drv_data->sssr;
+       u32 sscr1 = drv_data->sscr1;
+       u32 ssto = drv_data->sscr1;
        ^^^^^^^^^^^^^^^^^^^^^^^^^^


Nicolas

  parent reply	other threads:[~2006-02-10 17:40 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 [this message]
2006-02-10 22:19     ` Stephen Street
2006-02-10 22:45       ` Nicolas Pitre
2006-02-10 23:22         ` Stephen Street
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=Pine.LNX.4.64.0602101102520.5397@localhost.localdomain \
    --to=nico@cam.org \
    --cc=akpm@osdl.org \
    --cc=david-b@pacbell.net \
    --cc=dvrabel@arcom.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=stephen@streetfiresound.com \
    /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®