Vous recevez ce mail car vous êtes inscrit aux offres de My Ventes Privees avec
l'adresse spi-devel-general@lists.sourceforge.net.
Si vous souhaitez vous désinscrire, consultez le formulaire de désabonnement.
Si vous ne parvenez pas à lire ce message, vous pouvez consulter la version en
ligne.
Je
but also to easily handle the case
where a driver for that particular device is finally implemented, since
we won't have to change the device tree in itself to reflect this.
So I suggest you only add to the "real" compatible string instead of a
generic one.
Maxime
[1] http://comments
unsigned type [-Woverflow]
Signed-off-by: Maxime Ripard
Reported-by: Fengguang Wu
---
include/linux/spi/spi_gpio.h |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/include/linux/spi/spi_gpio.h b/include/linux/spi/spi_gpio.h
index 369b3d7..1634ce3 100644
--- a/include/linux
The bindings assumed that the gpios properties were always there, which
made the NO_TX and NO_RX mode not usable from device tree. Add extra
checks to make sure that the driver can work if either MOSI or MISO is
not used.
Signed-off-by: Maxime Ripard
Cc: Mark Brown
---
drivers/spi/spi-gpio.c
On 09/01/2013 09:37, Maxime Ripard wrote:
> On 27/12/2012 22:54, Maxime Ripard wrote:
>> The bindings assumed that the gpios properties were always there, which
>> made the NO_TX and NO_RX mode not usable from device tree. Add extra
>> checks to make sure that the driver can w
Hi Grant,
On 27/12/2012 22:54, Maxime Ripard wrote:
> The bindings assumed that the gpios properties were always there, which
> made the NO_TX and NO_RX mode not usable from device tree. Add extra
> checks to make sure that the driver can work if either MOSI or MISO is
> not used.
The bindings assumed that the gpios properties were always there, which
made the NO_TX and NO_RX mode not usable from device tree. Add extra
checks to make sure that the driver can work if either MOSI or MISO is
not used.
Signed-off-by: Maxime Ripard
---
drivers/spi/spi-gpio.c | 23
Since we don't have a driver for it yet, use spidev instead.
Signed-off-by: Maxime Ripard
---
drivers/spi/spidev.c |1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 9fc5788..e44abc9 100644
--- a/drivers/spi/spidev.c
+++ b/driver
There is no driver for it yet, so it will use spidev.
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/imx28-cfa10049.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/imx28-cfa10049.dts
b/arch/arm/boot/dts/imx28-cfa10049.dts
index 05c892e..2ef7ce6 100644
This will allow to probe spidev from device tree by adding the
compatible string of each device to this array.
Signed-off-by: Maxime Ripard
---
drivers/spi/spidev.c |9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 830adbe..9fc5788
Hi everyone,
This patchset probes spidev on the SSP3 bus where on the CFA-10049 there is
a Rohm DH2228FV DAC.
It first adds the dt bindings for the spidev driver, and the proper node in
the CFA-10049 device tree file.
Maxime
Changes from v1:
- Removed the linux,spidev compatible string and
Hi Mark,
Le 28/10/2012 00:19, Mark Brown a écrit :
> On Fri, Oct 26, 2012 at 10:07:52AM +0200, Maxime Ripard wrote:
>> This will allow to probe spidev from device tree
>
> So, this isn't really something we should have in DT in this format
> - the fact that we happen to c
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/imx28-cfa10049.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/imx28-cfa10049.dts
b/arch/arm/boot/dts/imx28-cfa10049.dts
index 05c892e..d91d16c 100644
--- a/arch/arm/boot/dts/imx28-cfa10049.dts
+++ b/arch/arm
Hi everyone,
This patchset probes spidev on the SSP3 bus where on the CFA-10049 there is
a DAC.
It first adds the dt bindings for the spidev driver, and the proper node in
the CFA-10049 device tree file.
Maxime
Maxime Ripard (2):
spi: spidev: Add device tree bindings
ARM: dts: cfa10049
This will allow to probe spidev from device tree
Signed-off-by: Maxime Ripard
---
drivers/spi/spidev.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 830adbe..8ae0660 100644
--- a/drivers/spi/spidev.c
+++ b/drivers/spi
This will allow to probe spidev from device tree
Signed-off-by: Maxime Ripard
---
drivers/spi/spidev.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 830adbe..8ae0660 100644
--- a/drivers/spi/spidev.c
+++ b/drivers/spi
Hi everyone,
This patchset probes spidev on the SSP3 bus where on the CFA-10049 there is
a DAC.
It first adds the dt bindings for the spidev driver, and the proper node in
the CFA-10049 device tree file.
Maxime
Maxime Ripard (2):
spi: spidev: Add device tree bindings
ARM: dts: cfa10049
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/imx28-cfa10049.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/imx28-cfa10049.dts
b/arch/arm/boot/dts/imx28-cfa10049.dts
index 05c892e..d91d16c 100644
--- a/arch/arm/boot/dts/imx28-cfa10049.dts
+++ b/arch/arm
Signed-off-by: Maxime Ripard
---
arch/arm/boot/dts/imx28-cfa10049.dts |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm/boot/dts/imx28-cfa10049.dts
b/arch/arm/boot/dts/imx28-cfa10049.dts
index 05c892e..d91d16c 100644
--- a/arch/arm/boot/dts/imx28-cfa10049.dts
+++ b/arch/arm
This will allow to probe spidev from device tree
Signed-off-by: Maxime Ripard
---
drivers/spi/spidev.c | 10 ++
1 file changed, 10 insertions(+)
diff --git a/drivers/spi/spidev.c b/drivers/spi/spidev.c
index 830adbe..8ae0660 100644
--- a/drivers/spi/spidev.c
+++ b/drivers/spi
Hi everyone,
This patchset probes spidev on the SSP3 bus where on the CFA-10049 there is
a DAC.
It first adds the dt bindings for the spidev driver, and the proper node in
the CFA-10049 device tree file.
Maxime
Maxime Ripard (2):
spi: spidev: Add device tree bindings
ARM: dts: cfa10049
Le 03/08/2012 16:43, Shawn Guo a écrit :
> On Fri, Aug 03, 2012 at 04:30:39PM +0200, Maxime Ripard wrote:
>> If you don't do it, the bus number will be a bogus value, possibly used
>> for device file names in drivers like spidev.
>>
> Do you see any problem with that?
If you don't do it, the bus number will be a bogus value, possibly used
for device file names in drivers like spidev.
Signed-off-by: Maxime Ripard
---
drivers/spi/spi-mxs.c |9 +
1 file changed, 9 insertions(+)
diff --git a/drivers/spi/spi-mxs.c b/drivers/spi/spi-mxs.c
ility is arrange that the
transfer happens and its complete() callback is issued. The two
will normally happen later, after other transfers complete, and
if the controller is idle it will need to be kickstarted.
So we cannot do a synchronous wait here, this must be push
24 matches
Mail list logo