Re: [PATCH 1/1] spi: omap2-mcspi: add option to configure output line for McSPI driver
On Mon, Oct 08, 2012 at 04:39:40PM -0600, Stan Hu wrote: McSPI driver previously assumed that D0 was input (MISO) and D1 was output (MOSI). This forces the hardware designer to wire all SPI peripherals in this way when it should be a software configuration option. I applied a similar patch from Daniel Mack just now; please check if there's anything he's missing. His patch was sent earlier and also adds DT bindings. -- Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [PATCH 1/1] spi: omap2-mcspi: add option to configure output line for McSPI driver
The other configuration is used in the case when you have SPI devices wired opposite to the default case. This was the case for a custom board using the McSPI driver. I tested it by just passing in the parameter in the device config data when registering the device under the spidev driver. I noticed a similar patch was submitted recently: http://sourceforge.net/mailarchive/forum.php?thread_name=1349626784-22035-1-git-send-email-zonque%40gmail.comforum_name=spi-devel-general The reason I put it in the device config because I reasoned you could in theory configure MOSI and MISO differently for each SPI device on the bus. This seems unlikely, though, but it is within the power of a hardware designer to do that. Feel free to use the other patch if it's more complete. On Tue, Oct 9, 2012 at 11:28 AM, Shubhrajyoti Datta omaplinuxker...@gmail.com wrote: On Tue, Oct 9, 2012 at 4:09 AM, Stan Hu sta...@gmail.com wrote: McSPI driver previously assumed that D0 was input (MISO) and D1 was output (MOSI). This forces the hardware designer to wire all SPI peripherals in this way when it should be a software configuration option. Your change looks good. What is the other configuration used for? Also are you using a dt patch to test it? Signed-off-by: Stan Hu sta...@gmail.com --- -- Don't let slow site performance ruin your business. Deploy New Relic APM Deploy New Relic app performance management and know exactly what is happening inside your Ruby, Python, PHP, Java, and .NET app Try New Relic at no cost today and get our sweet Data Nerd shirt too! http://p.sf.net/sfu/newrelic-dev2dev ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
[PATCH 1/1] spi: omap2-mcspi: add option to configure output line for McSPI driver
McSPI driver previously assumed that D0 was input (MISO) and D1 was output
(MOSI).
This forces the hardware designer to wire all SPI peripherals in this way when
it should be a software configuration option.
Signed-off-by: Stan Hu sta...@gmail.com
---
drivers/spi/spi-omap2-mcspi.c | 11 +--
include/linux/platform_data/spi-omap2-mcspi.h |2 ++
2 files changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/spi/spi-omap2-mcspi.c b/drivers/spi/spi-omap2-mcspi.c
index 3542fdc..d7c7e13 100644
--- a/drivers/spi/spi-omap2-mcspi.c
+++ b/drivers/spi/spi-omap2-mcspi.c
@@ -740,6 +740,7 @@ static int omap2_mcspi_setup_transfer(struct spi_device
*spi,
struct spi_transfer *t)
{
struct omap2_mcspi_cs *cs = spi-controller_state;
+ struct omap2_mcspi_device_config *cd = spi-controller_data;
struct omap2_mcspi *mcspi;
struct spi_master *spi_cntrl;
u32 l = 0, div = 0;
@@ -765,8 +766,14 @@ static int omap2_mcspi_setup_transfer(struct spi_device
*spi,
/* standard 4-wire master mode: SCK, MOSI/out, MISO/in, nCS
* REVISIT: this controller could support SPI_3WIRE mode.
*/
- l = ~(OMAP2_MCSPI_CHCONF_IS|OMAP2_MCSPI_CHCONF_DPE1);
- l |= OMAP2_MCSPI_CHCONF_DPE0;
+ l = ~(OMAP2_MCSPI_CHCONF_IS|
+ OMAP2_MCSPI_CHCONF_DPE0|OMAP2_MCSPI_CHCONF_DPE1);
+
+ /* set input selection for D0 and D1 */
+ if (cd-d0_is_output)
+ l |= OMAP2_MCSPI_CHCONF_IS|OMAP2_MCSPI_CHCONF_DPE1;
+ else
+ l |= OMAP2_MCSPI_CHCONF_DPE0;
/* wordlength */
l = ~OMAP2_MCSPI_CHCONF_WL_MASK;
diff --git a/include/linux/platform_data/spi-omap2-mcspi.h
b/include/linux/platform_data/spi-omap2-mcspi.h
index a357eb2..419d08a 100644
--- a/include/linux/platform_data/spi-omap2-mcspi.h
+++ b/include/linux/platform_data/spi-omap2-mcspi.h
@@ -18,6 +18,8 @@ struct omap2_mcspi_dev_attr {
struct omap2_mcspi_device_config {
unsigned turbo_mode:1;
+ /* 0 - [D0 = MISO, D1 = MOSI], 1 - [D0 = MOSI, D1 = MISO] */
+ unsigned d0_is_output:1;
};
#endif
--
1.7.9.5
--
Don't let slow site performance ruin your business. Deploy New Relic APM
Deploy New Relic app performance management and know exactly
what is happening inside your Ruby, Python, PHP, Java, and .NET app
Try New Relic at no cost today and get our sweet Data Nerd shirt too!
http://p.sf.net/sfu/newrelic-dev2dev
___
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
