13:14:06--
LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial
Remotely access PCs and mobile devices and provide instant support
Improve your efficiency, and focus on delivering more value-add service
On Thu, Dec 06, 2012 at 11:35:47PM +, Grant Likely wrote:
> Fix problem discovered with sparse:
> + drivers/spi/spi.c:1554:37: sparse: incompatible types in comparison
> expression (different signedness)
> drivers/spi/spi.c: In function 'spi_write_then_read':
> drivers/spi/spi.c:1554:23: warni
On Thu, Dec 06, 2012 at 02:04:27PM +, Grant Likely wrote:
> Alright, applied. I've also merged in your spi-next tree. Let me know if
> that causes problems because it needs to be rebased.
No problem - do you just want to take over the SPI tree again or should
I carry on applying things?
On Thu, Dec 06, 2012 at 05:14:33PM -0700, Jason Gunthorpe wrote:
> On Thu, Dec 06, 2012 at 06:53:11PM -0500, Jason Cooper wrote:
> > On Thu, Dec 06, 2012 at 04:49:17PM -0700, Jason Gunthorpe wrote:
> > > Jason: Do you have any of these possibly affected boards with a SPI
> > > flash to test linux-n
On Thu, Dec 06, 2012 at 06:53:11PM -0500, Jason Cooper wrote:
> On Thu, Dec 06, 2012 at 04:49:17PM -0700, Jason Gunthorpe wrote:
> > Jason: Do you have any of these possibly affected boards with a SPI
> > flash to test linux-next? dove, dreamplug, ts219 and lsxl
>
> Yep, dreamplug ought to do.
Hm
On Thu, Dec 06, 2012 at 04:49:17PM -0700, Jason Gunthorpe wrote:
> Jason: Do you have any of these possibly affected boards with a SPI
> flash to test linux-next? dove, dreamplug, ts219 and lsxl
Yep, dreamplug ought to do.
thx,
Jason.
On Thu, Dec 06, 2012 at 11:23:05PM +, Grant Likely wrote:
> > This will likely switch all current users from using 'whatever the
> > firmware left behind' to 'whatever the kernel default is' - which will
> > surely break something here and there??
>
> Hmmm. Hard to say. Just the fact that exi
Fix problem discovered with sparse:
+ drivers/spi/spi.c:1554:37: sparse: incompatible types in comparison
expression (different signedness)
drivers/spi/spi.c: In function 'spi_write_then_read':
drivers/spi/spi.c:1554:23: warning: comparison of distinct pointer types lacks
a cast [enabled by defau
On Thu, 6 Dec 2012 10:25:04 -0700, Jason Gunthorpe
wrote:
> On Thu, Dec 06, 2012 at 02:25:21PM +, Grant Likely wrote:
> > On Wed, 21 Nov 2012 12:23:35 -0700, Jason Gunthorpe
> > wrote:
> > > Support these transfer modes from the SPI layer by setting
> > > the appropriate register bits befor
On Thu, Dec 06, 2012 at 02:25:21PM +, Grant Likely wrote:
> On Wed, 21 Nov 2012 12:23:35 -0700, Jason Gunthorpe
> wrote:
> > Support these transfer modes from the SPI layer by setting
> > the appropriate register bits before doing the transfer.
> >
> > This was tested on the Marvell kirkwood
This patch allows to specify that a SPI device is connected in 3-wire mode via
device tree.
Signed-off-by: Lars-Peter Clausen
Acked-by: Rob Herring
---
Documentation/devicetree/bindings/spi/spi-bus.txt | 2 ++
drivers/spi/spi.c | 2 ++
2 files changed, 4 insertio
On 12/06/2012 03:37 PM, Grant Likely wrote:
> On Mon, 26 Nov 2012 11:09:47 +0100, Stefan Roese wrote:
>> By setting bus_num to 0 the resulting device is named "spi0". Otherwise
>> the name was "spi32766" (dynamic numbering) which was a bit confusing.
>>
>> Using 0 is correct as this driver (and th
On Mon, 26 Nov 2012 11:09:47 +0100, Stefan Roese wrote:
> By setting bus_num to 0 the resulting device is named "spi0". Otherwise
> the name was "spi32766" (dynamic numbering) which was a bit confusing.
>
> Using 0 is correct as this driver (and the MPC5200 SPI controller) only
> supports one SPI
On Fri, 23 Nov 2012 14:46:24 +, Phil Edworthy
wrote:
> The driver attempts to read the received data immediately after
> writing to the transmit buffer. If no data is available, the driver
> currently waits 20ms until trying again. Since the hardware needs
> to shift out the transmitted data,
On Thu, 22 Nov 2012 10:26:15 +0100, Andreas Larsson wrote:
> I am looking into writing a driver for a core running on sparc that is mostly
> but not entirely compatible with the cpu mode of spi-fsl-spi. I am thinking of
> what could be the best approach for realizing this. Any comments on a
> pre
On Wed, 21 Nov 2012 12:23:35 -0700, Jason Gunthorpe
wrote:
> Support these transfer modes from the SPI layer by setting
> the appropriate register bits before doing the transfer.
>
> This was tested on the Marvell kirkwood SOC that uses this driver.
Woo! a note about how it was tested. I can't
> I think I've asked this question before, but I can't remember if I've
> gotten an answer. How is this different from the designware spi
> controller that is already in the tree for medfield and moorestown MID
> platforms? (drivers/spi/spi-dw-mid.c).
Different devices.
> ... Okay, so I just wen
On Mon, 12 Nov 2012 11:03:56 +0100, Jonas Gorski wrote:
> Hi,
>
> On 9 November 2012 10:06, Laxman Dewangan wrote:
> > When spi client does the spi transfer and does not sets
> > the bits_per_word for each transfer then set it as default
> > of spi device in spi core before calling low level tra
On Wed, 7 Nov 2012 12:40:06 +0100, Bastian Hecht wrote:
> This adds the capability to retrieve setup data from the device tree
> node. The usage of platform data is still available.
>
> Signed-off-by: Bastian Hecht
Aside from the binding issues I've pointed out on patch 4, this change
looks fi
On Thu, Dec 6, 2012 at 2:08 PM, Grant Likely wrote:
> On Wed, 7 Nov 2012 12:40:07 +0100, Bastian Hecht wrote:
>> Add binding documentation for Renesas' MSIOF SPI controller.
>>
>> Signed-off-by: Bastian Hecht
>> ---
>> Documentation/devicetree/bindings/spi/sh-msiof.txt | 12
>>
On Wed, 7 Nov 2012 12:40:07 +0100, Bastian Hecht wrote:
> Add binding documentation for Renesas' MSIOF SPI controller.
>
> Signed-off-by: Bastian Hecht
> ---
> Documentation/devicetree/bindings/spi/sh-msiof.txt | 12
> 1 files changed, 12 insertions(+), 0 deletions(-)
> create
On Wed, 7 Nov 2012 12:40:04 +0100, Bastian Hecht wrote:
> clk_get() no longer needs a character string for associating the right
> clock as this is done via the device struct now.
>
> Signed-off-by: Bastian Hecht
Applied, thanks.
g.
> ---
> drivers/spi/spi-sh-msiof.c |6 ++
> 1 file
On Thu, 6 Dec 2012 14:37:33 +0900, Mark Brown
wrote:
> On Thu, Dec 06, 2012 at 12:00:26AM +, Grant Likely wrote:
>
> > Looks good to me. Probably 3.9 material though.
>
> > Acked-by: Grant Likely
>
> Hrm, I'd be inclined to apply it now - it's isolated enough that it can
> be reverted if
On Wed, 21 Nov 2012 10:16:43 +0800, chao bi wrote:
>
> This patch is to implement SSP SPI controller driver, which has been applied
> and
> validated on intel Moorestown & Medfield platform. The patch are originated by
> Ken Mills and Sylvain Centelles
> ,
> and to be further developed by Chan
24 matches
Mail list logo
