On Thu, Aug 28, 2014 at 5:53 PM, leroy christophe
wrote:
>
> I've been able to identify the origin of the issue. It happens since the
> below commit.
> Do you know what should be done to fix that ?
>
> Christophe
>
>
Actually, more things are wrong with what the driver is doing.
If inside
I've been able to identify the origin of the issue. It happens since the below
commit.
Do you know what should be done to fix that ?
Christophe
From 7a40054361162d2f78f332aa868fed137beb7901 Mon Sep 17 00:00:00 2001
From: Axel Lin
Date: Sun, 30 Mar 2014 16:42:57 +0800
Subject: spi: fsl-spi:
I've been able to identify the origin of the issue. It happens since the below
commit.
Do you know what should be done to fix that ?
Christophe
From 7a40054361162d2f78f332aa868fed137beb7901 Mon Sep 17 00:00:00 2001
From: Axel Lin axel@ingics.com
Date: Sun, 30 Mar 2014 16:42:57 +0800
On Thu, Aug 28, 2014 at 5:53 PM, leroy christophe
christophe.le...@c-s.fr wrote:
I've been able to identify the origin of the issue. It happens since the
below commit.
Do you know what should be done to fix that ?
Christophe
Actually, more things are wrong with what the driver is doing.
Since Linux 3.16, for all drivers tied to SPI bus, I get the following
warning on a PowerPC 8xx.
It doesn't happen with Linux 3.15
What can be the reason / what should I look at ?
[3.086957] device: 'spi32766.1': device_add
[3.087179] bus: 'spi': add device spi32766.1
[3.087653]
Since Linux 3.16, for all drivers tied to SPI bus, I get the following
warning on a PowerPC 8xx.
It doesn't happen with Linux 3.15
What can be the reason / what should I look at ?
[3.086957] device: 'spi32766.1': device_add
[3.087179] bus: 'spi': add device spi32766.1
[3.087653]
6 matches
Mail list logo
