there are no machines in-tree that still use the driver
name as device name. So save a few bytes and remove it.
Signed-off-by: Uwe Kleine-König u.kleine-koe...@pengutronix.de
---
drivers/spi/spi_imx.c | 30 ++
1 files changed, 2 insertions(+), 28 deletions(-)
diff
The SPI core inside Sodaville is very much the same as in PXA25x.
I Cc the ARM folks because patch 4 reorganizes some files so that they
can be accessed from x86 so you see the whole picture. Yes, Sodaville is
a x86 SoC :)
The SPI device is behind a PCI bus. The PCI probe code simply creates a
It is a simple driver and there is no need to call its init function
at the level of a subsystem.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Signed-off-by: Dirk Brandewie dirk.brande...@gmail.com
---
drivers/spi/pxa2xx_spi.c |2 +-
1 files changed, 1 insertions(+), 1
This is required in case the interrupt line is shared with other
devices.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Signed-off-by: Dirk Brandewie dirk.brande...@gmail.com
---
drivers/spi/pxa2xx_spi.c | 15 ++-
1 files changed, 14 insertions(+), 1 deletions(-)
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Signed-off-by: Dirk Brandewie dirk.brande...@gmail.com
---
arch/arm/plat-pxa/include/plat/ssp.h |3 ++-
drivers/spi/pxa2xx_spi.c |8
2 files changed, 6 insertions(+), 5 deletions(-)
diff --git
The PXA-SPI driver relies on some files / defines which are arm specific
and are within the ARM tree. The CE4100 SoC which is x86 has also the
SPI core.
This patch moves the ssp and spi files from arm/mach-pxa and plat-pxa to
include/linux where the CE4100 can access them.
This move got verified
For PXA the default threshold is FIFO_DEPTH / 2. Adjust this value for
CE4100.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Signed-off-by: Dirk Brandewie dirk.brande...@gmail.com
---
arch/arm/include/asm/pxa2xx_ssp.h | 15 +++
arch/x86/include/asm/pxa2xx_ssp.h |
Sodaville's SPI controller is very much the same as in PXA25x. The
difference:
- The RX/TX FIFO is only 4 words deep instead of 16
- No DMA support
- The SPI controller offers a CS functionality
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
Signed-off-by: Dirk Brandewie
the of_node will auto-publish devices which are added to the device
tree.
Signed-off-by: Sebastian Andrzej Siewior bige...@linutronix.de
---
drivers/spi/pxa2xx_spi.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/drivers/spi/pxa2xx_spi.c b/drivers/spi/pxa2xx_spi.c
After all TX bytes are sent, the driver spins while the SPI core is busy
and then it spins for a short period of time until RX bytes are
available.
On Sodavile the busy flag disappears pretty quick and after that it
takes approx ~130ms (sometimes less but not much) until there are bytes
available
Haojian Zhuang wrote:
Hi Sebastian,
Hi Hoajian,
Actually it's added for cpufreq usage. We can check the commit in below.
pxa2xx_spi: register earlier
Register pxa2xx_spi earlier so it can be used with cpufreq
So I think that this modifcation may cause others brokne.
I've been
Haojian Zhuang wrote:
On Wed, Nov 24, 2010 at 7:13 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
snip
diff --git a/arch/arm/plat-pxa/include/plat/ssp.h
b/include/linux/pxa2xx_ssp.h
similarity index 98%
rename from arch/arm/plat-pxa/include/plat/ssp.h
rename to
On Wed, Nov 24, 2010 at 10:09 PM, Sebastian Andrzej Siewior
bige...@linutronix.de wrote:
Haojian Zhuang wrote:
Hi Sebastian,
Hi Hoajian,
Actually it's added for cpufreq usage. We can check the commit in below.
pxa2xx_spi: register earlier
Register pxa2xx_spi earlier so it can be
On Wed, Nov 24, 2010 at 03:09:25PM +0100, Sebastian Andrzej Siewior wrote:
I've been pointed out to this commit but I don't understand _why_.
The part I don't get is so it can be used with cpufreq. Is it
refered to a driver or the subsystem as it?
We need the regulators for the CPU rails to
On Wed, Nov 24, 2010 at 7:16 AM, Mark Brown
broo...@opensource.wolfsonmicro.com wrote:
On Wed, Nov 24, 2010 at 03:09:25PM +0100, Sebastian Andrzej Siewior wrote:
I've been pointed out to this commit but I don't understand _why_.
The part I don't get is so it can be used with cpufreq. Is it
On Wed, Nov 24, 2010 at 08:30:37AM -0700, Grant Likely wrote:
It would be easy enough to defer cpufreq initialization based on some
platform defined criteria. It's just an initcall. However, I don't
Though it'd be much better to fix the thing where cpufreq doesn't have a
device anyway.
As request by Grant Likely, there is no more cover letter. Full changelog is
following.
I am still reluctant to add this changelog in the patch description, as it adds
no value to
the patch itself: when it was needed I try to updat comments or patch
description.
I understand that Grant Likely
--
Increase Visibility of Your 3D Game App Earn a Chance To Win $500!
Tap into the largest installed PC base get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R)
Gregory CLEMENT gregory.clem...@free-electrons.com writes:
As request by Grant Likely, there is no more cover letter. Full changelog is
following.
I am still reluctant to add this changelog in the patch description, as it
adds no value to
the patch itself: when it was needed I try to updat
--- On Wed, 11/24/10, Kevin Hilman khil...@deeprootsystems.com wrote:
I'm not SPI-aware enough to ack
this patch or
test it thoroughly.
Heh, my excuse is usually not enough time
or sometimes no test setup ... ;)
In this case I can at least ack the fix in
principle. CS active means an
It is reasonable, looks fine to me. :-)
Jason.
Uwe Kleine-König wrote:
there are no machines in-tree that still use the driver
name as device name. So save a few bytes and remove it.
Signed-off-by: Uwe Kleine-König u.kleine-koe...@pengutronix.de
---
drivers/spi/spi_imx.c | 30
21 matches
Mail list logo
