spi: controller driver for Designware SPI core
PATCH RESEND v2 1/3 spi: controller driver for Designware SPI core
Quoted 1 line
From
5d87c87105aba522468cabb6fe206a4515dc85e8Mon Sep 17 00:00:00 2001
From: Feng Tang <[email protected]>
Date: Tue, 4 Aug 2009 16:23:47 +0800
Subject: [PATCH 1/3] spi: controller driver for Designware SPI core
Driver for the Designware SPI core, it supports multipul interfaces like PCI/APB etc. User can use "dw_apb_ssi_db.pdf" from Synopsys as HW datasheet.
--- drivers/spi/Kconfig | 6 + drivers/spi/Makefile | 1 + drivers/spi/dw_spi.c | 941 ++++++++++++++++++++++++++++++++++++++++++++ include/linux/spi/dw_spi.h | 212 ++++++++++ 4 files changed, 1160 insertions(+), 0 deletions(-) create mode 100644 drivers/spi/dw_spi.c create mode 100644 include/linux/spi/dw_spi.h
drivers/spi/Kconfig +6 -0
@@ -227,6 +227,12 @@ config SPI_XILINX See the "OPB Serial Peripheral Interface (SPI) (v1.00e)" Product Specification document (DS464) for hardware details. +config SPI_DESIGNWARE + bool "DesignWare SPI controller core support" + depends on SPI_MASTER + help + general driver for SPI controller core from DesignWare + # # Add new SPI master controllers in alphabetical order above this line #
drivers/spi/Makefile +1 -0
@@ -31,6 +31,7 @@ obj-$(CONFIG_SPI_S3C24XX) += spi_s3c24xx.o obj-$(CONFIG_SPI_TXX9) += spi_txx9.o obj-$(CONFIG_SPI_XILINX) += xilinx_spi.o obj-$(CONFIG_SPI_SH_SCI) += spi_sh_sci.o +obj-$(CONFIG_SPI_DESIGNWARE) += dw_spi.o # ... add above this line ... # SPI protocol drivers (device/link on bus)
drivers/spi/dw_spi.c new file +941 -0
941 lines not on this page · raw message
include/linux/spi/dw_spi.h new file +212 -0
212 lines not on this page · raw message
--
1.5.6.3
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
spi-devel-general mailing list spi-devel-general-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
Quoted 8 lines · On Mon, 21 Sep 2009 16:47:29 +0800 Feng Tang…
Quoted 1 line
From
5d87c87105aba522468cabb6fe206a4515dc85e8Mon Sep 17 00:00:00 2001From: Feng Tang <[email protected]>
Date: Tue, 4 Aug 2009 16:23:47 +0800
Subject: [PATCH 1/3] spi: controller driver for Designware SPI coreDriver for the Designware SPI core, it supports multipul interfaces like PCI/APB etc. User can use "dw_apb_ssi_db.pdf" from Synopsys as HW datasheet.
It appears that your email client replaced all the tabs with spaces - I cannot apply these patches.
drivers/spi/dw_spi.c line 81
Quoted 13 lines
...
drivers/spi/dw_spi.c new file +10
-0+#define SPI_REGS_BUFSIZE 1024 +static ssize_t spi_show_regs (struct file *file,char __user *user_buf, +size_t count,loff_t *ppos) +{ +struct dw_spi *dws; +char *buf; +u32 len =0 ; +ssize_t ret; + + dws = (struct dw_spi *)file->private_data;
Unneeded and undesirable cast of void*.
Quoted 51 lines
drivers/spi/dw_spi.c new file +48
-0+ buf =kzalloc (SPI_REGS_BUFSIZE ,GFP_KERNEL ); +if (!buf) +return 0 ; + + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"MRST SPI0 registers:\n" ); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"=================================\n" ); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"CTRL0: \t\t0x%08x\n" ,dw_readl (dws, ctrl0)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"CTRL1: \t\t0x%08x\n" ,dw_readl (dws, ctrl1)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"SSIENR: \t0x%08x\n" ,dw_readl (dws, ssienr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"SER: \t\t0x%08x\n" ,dw_readl (dws, ser)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"BAUDR: \t\t0x%08x\n" ,dw_readl (dws, baudr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"TXFTLR: \t0x%08x\n" ,dw_readl (dws, txfltr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"RXFTLR: \t0x%08x\n" ,dw_readl (dws, rxfltr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"TXFLR: \t\t0x%08x\n" ,dw_readl (dws, txflr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"RXFLR: \t\t0x%08x\n" ,dw_readl (dws, rxflr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"SR: \t\t0x%08x\n" ,dw_readl (dws, sr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"IMR: \t\t0x%08x\n" ,dw_readl (dws, imr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"ISR: \t\t0x%08x\n" ,dw_readl (dws, isr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"DMACR: \t\t0x%08x\n" ,dw_readl (dws, dmacr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"DMATDLR: \t0x%08x\n" ,dw_readl (dws, dmatdlr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"DMARDLR: \t0x%08x\n" ,dw_readl (dws, dmardlr)); + len +=snprintf (buf + len,SPI_REGS_BUFSIZE - len, +"=================================\n" ); + + ret =simple_read_from_buffer (user_buf, count, ppos, buf, len); +kfree (buf); +return ret; +} + +static int flush (struct dw_spi *dws) +{
drivers/spi/dw_spi.c line 173
Quoted 10 lines
drivers/spi/dw_spi.c new file +10
-0+unsigned long limit = loops_per_jiffy <<1 ; + +while (dw_readw (dws, sr) &SR_RF_NOT_EMPT ) { + limit = loops_per_jiffy <<1 ; +while ((dw_readw (dws, sr) &SR_BUSY ) && limit--) + ; +dw_readw (dws, dr); + } +return limit; +}
The duration of this timeout will have little relation to jiffies or anything like that. It'll mainly be dependent upon bus latencies. You may find that the upper bound to this delay is very large indeed.
If you really did intend to set some upper bound on the polling period, it'd be better to do
unsigned long end = jiffies + usecs_to_jiffies(1000);
while (time_before(jiffies, end)) {
...
}or something along those lines.
Quoted 6 lines
...
drivers/spi/dw_spi.c new file +3
-0+static int u16_reader (struct dw_spi *dws) +{ +u16 temp;
drivers/spi/dw_spi.c line 256
Quoted 10 lines
drivers/spi/dw_spi.c new file +10
-0+ +while ((dw_readw (dws, sr) &SR_RF_NOT_EMPT ) + && (dws->rx < dws->rx_end)) { + temp =dw_readw (dws, dr); + *(u16 *)(dws->rx) = temp; + dws->rx +=2 ; + } + +while (dw_readw (dws, sr) &SR_BUSY ) + ;
The code does this a lot.
It's a bit of a worry - if the hardware is misbehaving or gets hot-unplugged or powered off or such, the kernel will silently lock up.
Better practice would be to pull this into a separate function and to at least emit a printk from that function when the hardware has locked up. Even better, handle that error and recover.
drivers/spi/dw_spi.c line 302
Quoted 12 lines
drivers/spi/dw_spi.c new file +9
-0+return dws->rx == dws->rx_end; +} + +static inline void unmap_dma_buffers (struct dw_spi *dws) +{ +if (!dws->dma_mapped) +return ; + dws->dma_mapped =0 ; +}
One would think that a function called unmap_dma_buffers() would unmap dma buffers. But this doesn't do that.
Quoted 3 lines
...
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf