[SPAM] Английский язык за 2 месяца!
Alltime scvelrypdgcwxodul stxroasqqlfdkdcvsxz -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] PATCH[V2 1/3]: Update Platform files for SPI
On Tue, Feb 9, 2010 at 4:07 PM, Tony Lindgren wrote: > * Grant Likely [100209 14:38]: >> On Tue, Feb 9, 2010 at 3:25 PM, Tony Lindgren wrote: >> > * Hemanth V [100203 02:19]: >> >> From ee48142ddc43129a21676dbb56a83e3e7d8063de Mon Sep 17 00:00:00 2001 >> >> From: Hemanth V >> >> Date: Fri, 27 Nov 2009 14:22:30 +0530 >> >> Subject: [PATCH] Update platform files >> >> >> >> This patch updates platform files for >> >> fifo, slave support >> >> >> >> Signed-off-by: Hemanth V >> > >> > This should get merged via the spi-devel list with the other patches. >> > >> > Acked-by: Tony Lindgren >> >> Personally, I prefer not to carry arch/* changes in my next-spi >> branch, since it means that my pull requests are less obvious for >> Linus and there is greater chance of conflict. >> >> But if you still really want me to merge it through my tree, (or if >> getting the patches out of order will break things) then I'll pick it >> up. Just let me know. > > OK, if you ack it, I'll add the header into omap for-next. That > might break git bisect for some configurations depending in which > order the patches get pulled by Linus.. git bisect breakage is breakage enough. :-) You're right. I should pick this one up. I can see that now that I've had my tea and I'm no longer grumpy. > I guess eventually this header should not live under plat. Any reason the header cannot be moved to include/linux/spi/ now? g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] PATCH[V2 1/3]: Update Platform files for SPI
* Grant Likely [100209 14:38]: > On Tue, Feb 9, 2010 at 3:25 PM, Tony Lindgren wrote: > > * Hemanth V [100203 02:19]: > >> From ee48142ddc43129a21676dbb56a83e3e7d8063de Mon Sep 17 00:00:00 2001 > >> From: Hemanth V > >> Date: Fri, 27 Nov 2009 14:22:30 +0530 > >> Subject: [PATCH] Update platform files > >> > >> This patch updates platform files for > >> fifo, slave support > >> > >> Signed-off-by: Hemanth V > > > > This should get merged via the spi-devel list with the other patches. > > > > Acked-by: Tony Lindgren > > Personally, I prefer not to carry arch/* changes in my next-spi > branch, since it means that my pull requests are less obvious for > Linus and there is greater chance of conflict. > > But if you still really want me to merge it through my tree, (or if > getting the patches out of order will break things) then I'll pick it > up. Just let me know. OK, if you ack it, I'll add the header into omap for-next. That might break git bisect for some configurations depending in which order the patches get pulled by Linus.. I guess eventually this header should not live under plat. Regards, Tony -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] PATCH[V2 1/3]: Update Platform files for SPI
On Tue, Feb 9, 2010 at 3:25 PM, Tony Lindgren wrote: > * Hemanth V [100203 02:19]: >> From ee48142ddc43129a21676dbb56a83e3e7d8063de Mon Sep 17 00:00:00 2001 >> From: Hemanth V >> Date: Fri, 27 Nov 2009 14:22:30 +0530 >> Subject: [PATCH] Update platform files >> >> This patch updates platform files for >> fifo, slave support >> >> Signed-off-by: Hemanth V > > This should get merged via the spi-devel list with the other patches. > > Acked-by: Tony Lindgren Personally, I prefer not to carry arch/* changes in my next-spi branch, since it means that my pull requests are less obvious for Linus and there is greater chance of conflict. But if you still really want me to merge it through my tree, (or if getting the patches out of order will break things) then I'll pick it up. Just let me know. g. -- Grant Likely, B.Sc., P.Eng. Secret Lab Technologies Ltd. -- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] PATCH[V2 1/3]: Update Platform files for SPI
* Hemanth V [100203 02:19]:
> From ee48142ddc43129a21676dbb56a83e3e7d8063de Mon Sep 17 00:00:00 2001
> From: Hemanth V
> Date: Fri, 27 Nov 2009 14:22:30 +0530
> Subject: [PATCH] Update platform files
>
> This patch updates platform files for
> fifo, slave support
>
> Signed-off-by: Hemanth V
This should get merged via the spi-devel list with the other patches.
Acked-by: Tony Lindgren
> ---
> arch/arm/mach-omap2/devices.c |5 +
> arch/arm/plat-omap/include/plat/mcspi.h | 29 -
> 2
> files changed, 33 insertions(+), 1 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
> index 733d3dc..79b5396 100644
> --- a/arch/arm/mach-omap2/devices.c
> +++ b/arch/arm/mach-omap2/devices.c
> @@ -282,6 +282,7 @@ static inline void omap_init_sti(void) {}
>
> static struct omap2_mcspi_platform_config omap2_mcspi1_config = {
> .num_cs = 4,
> + .force_cs_mode = 1,
> };
>
> static struct resource omap2_mcspi1_resources[] = {
> @@ -304,6 +305,10 @@ static struct platform_device omap2_mcspi1 = {
>
> static struct omap2_mcspi_platform_config omap2_mcspi2_config = {
> .num_cs = 2,
> + .mode = OMAP2_MCSPI_MASTER,
> + .dma_mode = 0,
> + .force_cs_mode = 0,
> + .fifo_depth = 0,
> };
>
> static struct resource omap2_mcspi2_resources[] = {
> diff --git a/arch/arm/plat-omap/include/plat/mcspi.h
> b/arch/arm/plat-omap/include/plat/mcspi.h
> index 1254e49..ffda0a1 100644
> --- a/arch/arm/plat-omap/include/plat/mcspi.h
> +++ b/arch/arm/plat-omap/include/plat/mcspi.h
> @@ -1,8 +1,35 @@
> #ifndef _OMAP2_MCSPI_H
> #define _OMAP2_MCSPI_H
>
> +#define OMAP2_MCSPI_MASTER 0
> +#define OMAP2_MCSPI_SLAVE1
> +
> +/**
> + * struct omap2_mcspi_platform_config - McSPI controller configuration + *
> @num_cs: Number of chip selects or channels supported
> + * @mode: SPI is master or slave
> + * @dma_mode: Use only DMA for data transfers
> + * @force_cs_mode: Use force chip select mode or auto chip select mode + *
> @fifo_depth: FIFO depth in bytes, max value 64
> + *
> + * @dma_mode when set to 1 uses only dma for data transfers
> + * else the default behaviour is to use PIO mode for transfer
> + * size of 8 bytes or less. This mode is useful when mcspi
> + * is configured as slave
> + *
> + * @force_cs_mode when set to 1 allows continuous transfer of multiple + *
> spi
> words without toggling the chip select line.
> + *
> + * @fifo_depth when set to non zero values enables FIFO. fifo_depth + *
> should
> be set as a multiple of buffer size used for read/write. + */
> +
> struct omap2_mcspi_platform_config {
> - unsigned short num_cs;
> + u8 num_cs;
> + u8 mode;
> + u8 dma_mode;
> + u8 force_cs_mode;
> + unsigned short fifo_depth;
> };
>
> struct omap2_mcspi_device_config {
> --
> 1.5.6.3
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majord...@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
http://p.sf.net/sfu/solaris-dev2dev
___
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
[spi-devel-general] Decouvrez vos chiffres de chance, c'est gratuit!
-- SOLARIS 10 is the OS for Data Centers - provides features such as DTrace, Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW http://p.sf.net/sfu/solaris-dev2dev___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
[spi-devel-general] [SPAM]
<>-- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] OMAP3 Slave McSPI driver
Thanks Hemanth, I'll give it a try with 2.6.29 kernel. Do the patches support McSPI RX interrupt? Or McSPI FIFO full interrupt? Upon receipt of such interrupts, slave client could issue a spi_read. Thanks gilles Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920 -Original Message- From: V, Hemanth Sent: Tuesday, February 09, 2010 1:59 PM To: Talis, Gilles; linux-o...@vger.kernel.org Cc: spi-devel-general@lists.sourceforge.net Subject: Re: OMAP3 Slave McSPI driver - Original Message - From: "Talis, Gilles" To: Sent: Tuesday, February 09, 2010 3:06 PM Subject: OMAP3 Slave McSPI driver > Hi, > > My customer is using Android 2.6.29 kernel from OMAPZOOM and is looking > for support for slave mode on the SPI driver. > I saw there were patches for this feature sent to this list, but I was > wondering if those patches were tested on 2.6.29. > These patches have not been specifically tested on 29 kernel, but you could give it a shot. Pl also look at the latest patches (V2) posted. > I am also looking for some kind of API usage guidelines. How to setup the > slave mode and how is OMAP notified that data have been received from > external master device? My customer plans to use this driver in interrupt > mode (no DMA needed). > To set any mcspi controller to slave mode, you need to modify arch/arm/mach-omap2/devices.c file and set mode to OMAP2_MCSPI_SLAVE. Typically gpio is used by master to notify the slave that it is ready to transfer data. On gpio interrupt slave client could issue spi_read/spi_write commands. Two modes are supported i.e PIO and DMA. Any specific reason not to use DMA mode. Thanks Hemanth > Thanks > Gilels. > > > > Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve > Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920 > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] OMAP3 Slave McSPI driver
- Original Message - From: "Talis, Gilles" To: Sent: Tuesday, February 09, 2010 3:06 PM Subject: OMAP3 Slave McSPI driver > Hi, > > My customer is using Android 2.6.29 kernel from OMAPZOOM and is looking > for support for slave mode on the SPI driver. > I saw there were patches for this feature sent to this list, but I was > wondering if those patches were tested on 2.6.29. > These patches have not been specifically tested on 29 kernel, but you could give it a shot. Pl also look at the latest patches (V2) posted. > I am also looking for some kind of API usage guidelines. How to setup the > slave mode and how is OMAP notified that data have been received from > external master device? My customer plans to use this driver in interrupt > mode (no DMA needed). > To set any mcspi controller to slave mode, you need to modify arch/arm/mach-omap2/devices.c file and set mode to OMAP2_MCSPI_SLAVE. Typically gpio is used by master to notify the slave that it is ready to transfer data. On gpio interrupt slave client could issue spi_read/spi_write commands. Two modes are supported i.e PIO and DMA. Any specific reason not to use DMA mode. Thanks Hemanth > Thanks > Gilels. > > > > Texas Instruments France SA, 821 Avenue Jack Kilby, 06270 Villeneuve > Loubet. 036 420 040 R.C.S Antibes. Capital de EUR 753.920 > > > > -- > To unsubscribe from this list: send the line "unsubscribe linux-omap" in > the body of a message to majord...@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- The Planet: dedicated and managed hosting, cloud storage, colocation Stay online with enterprise data centers and the best network in the business Choose flexible plans and management services without long-term contracts Personal 24x7 support from experience hosting pros just a phone call away. http://p.sf.net/sfu/theplanet-com ___ spi-devel-general mailing list spi-devel-general@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/spi-devel-general
Re: [spi-devel-general] [RFC][PATCH v2] serial: spi: add spi-uart driver for Maxim 3110
> > + for (i = 0; i < len; i++) {
> > + obuf[i] = (u8)xmit->buf[xmit->tail] | WD_TAG;
> > + xmit->tail = (xmit->tail + 1) &
> > + (UART_XMIT_SIZE - 1);
>
> Could this driver use include/linux/kfifo.h, rather than open-coding it?
The circ buffer stuff comes from the serial layer. The whole serial layer
wants switching to kfifo (as and when we know why the kfifo changes seem
to have broken USB serial) but the driver can't do that itself and use
the serial core code until then.
(Actually most of the serial_core code wants a rewrite but having had a
couple of goes at doing it I've not figured out any way to do it without
simply breaking all sorts of embedded platform serial drivers that need
specific hardware to fix).
> > + }
> > + max3110_write_then_read(max, (u8 *)obuf,
> > + (u8 *)ibuf, len * 2, 0);
>
> Error codes are ignored.
The drivers/serial midlayer has no provision for reporting them.
Alan
--
The Planet: dedicated and managed hosting, cloud storage, colocation
Stay online with enterprise data centers and the best network in the business
Choose flexible plans and management services without long-term contracts
Personal 24x7 support from experience hosting pros just a phone call away.
http://p.sf.net/sfu/theplanet-com
___
spi-devel-general mailing list
spi-devel-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/spi-devel-general
