[Added Steven Sakoman to the CC list]
Hi,
We're seeing timeout errors with SanDisk MMC cards and a 2.6.32
kernel (BeagleBoard Rev C5).
The suggested fix of setting dto timeout to 14
(http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42214.html)
doesn't help. Any other suggestions with
Hi,
We're seeing MMC timeout errors with SanDisk MMC cards and a 2.6.32
kernel (BeagleBoard Rev C5).
The suggested fix of setting dto timeout to 14
(http://www.mail-archive.com/linux-omap@vger.kernel.org/msg42214.html)
doesn't help. Any other suggestions with any familiar with this issue?
The
Op 18 jul 2011, om 08:30 heeft Joel A Fernandes het volgende geschreven:
Hi,
We're seeing MMC timeout errors with SanDisk MMC cards and a 2.6.32
kernel (BeagleBoard Rev C5).
Does the same happen with a more recent, e.g. 2.6.39 kernel?
--
To unsubscribe from this list: send the line
-Original Message-
From: Jassi Brar [mailto:jassisinghb...@gmail.com]
Sent: Tuesday, July 12, 2011 6:15 PM
To: Raju, Sundaram
Cc: Linus Walleij; linux-arm-ker...@lists.infradead.org; linux-
ker...@vger.kernel.org; davinci-linux-open-sou...@linux.davincidsp.com;
* Arnd Bergmann a...@arndb.de [110717 14:36]:
Hi Paul and Tomi,
I'm trying to get the arm-soc tree integrated into linux-next, but right
now that fails because of lots of conflicts in the
arch/arm/mach-omap2/clock44xx_data.c
and arch/arm/mach-omap2/omap_hwmod_44xx_data.c files.
I've
* Tero Kristo t-kri...@ti.com [110713 06:56]:
Hello,
Based on the comments for the previous version of this set, I implemented
a regulator driver for the OMAP SMPS now. It could actually be moved under
arch/arm/mach-omap2/ directory instead of drivers/regulator, I think it
should work from
* Jan Weitzel j.weit...@phytec.de [110715 09:01]:
First try to join both boards. Only compile testet.
basis for discusson
Jan Weitzel (2):
omap4: board-omap4panda: prepare for join
omap4: board-omap4panda: join Phytec phyCORE-OMAP4
arch/arm/mach-omap2/Kconfig |6
* Grant Likely grant.lik...@secretlab.ca [110716 22:08]:
The way I see it, you've got two options:
1) modify the of_platform_bus_create() to call some kind of
of_platform_bus_create_omap() for devices that match ti,omap3-device
or something.
2) Leave of_platform_bus_create(), and
Hi Grant,
On 17 July 2011 10:43, Grant Likely grant.lik...@secretlab.ca wrote:
Hi Manjunath,
Comments below. I left in a lot of context for the new folks that
I've cc'd (Tony and Kevin).
On Sat, Jul 16, 2011 at 2:07 PM, G, Manjunath Kondaiah manj...@ti.com wrote:
On Thu, Jul 14, 2011 at
On Fri, 2011-07-15 at 18:40 +0200, Todd Poynor wrote:
On Tue, Jul 05, 2011 at 01:27:47PM +0300, Tero Kristo wrote:
Introduce a chained interrupt handler mechanism for the PRCM
interrupt, so that individual PRCM event can cleanly be handled by
handlers in separate drivers. We do this by
Axel Lin axel@gmail.com writes:
2011/6/28 Kevin Hilman khil...@ti.com:
Axel Lin axel@gmail.com writes:
The gpio-omap driver has been converted to use generic IRQ chip.
Thus select GENERIC_IRQ_CHIP for TI OMAP1 to fix below build error.
LD vmlinux
drivers/built-in.o: In
Hello,
Main changes compared to v2:
- cleanup should now work better
- register all available regulators always, if no initdata = readonly
- added board init support functionality to twl-common
- constraints not touched by the driver anymore
Tested on omap3 beagle.
-Tero
Texas Instruments
This is needed so that these include files can be accessed from drivers.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/voltage.h | 180 -
arch/arm/mach-omap2/vp.h | 128
These are now under plat-omap/include/plat.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/io.c |2 +-
arch/arm/mach-omap2/omap_opp_data.h |3 +--
arch/arm/mach-omap2/omap_twl.c|2 +-
arch/arm/mach-omap2/pm.c
OMAP SMPS regulator driver provides access to OMAP voltage processor
controlled regulators. These include VDD_MPU and VDD_CORE for OMAP3 and
additionally VDD_IVA for OMAP4. SMPS regulators use the OMAP voltage
layer for the actual voltage regulation operations.
Signed-off-by: Tero Kristo
This is using the common API defined in twl-common.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
omap3_pmic_get_smps_config can now be used to get regulator configuration
for MPU and CORE SMPS regulators. This should be expanded later to add IVA
SMPS regulator for OMAP4.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/twl-common.c | 62
Beagleboard rev-c4 has a speed sorted OMAP3530 chip which can run at 720MHz.
This is a temporary patch for supporting this set only, do not integrate.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/board-omap3beagle.c | 32 +++
On Mon, 2011-07-18 at 19:35 +0200, Kristo, Tero wrote:
Hello,
Main changes compared to v2:
- cleanup should now work better
- register all available regulators always, if no initdata = readonly
- added board init support functionality to twl-common
- constraints not touched by the driver
Hi,
On Mon, Jul 18, 2011 at 08:35:17PM +0300, Tero Kristo wrote:
This is needed so that these include files can be accessed from drivers.
Signed-off-by: Tero Kristo t-kri...@ti.com
---
arch/arm/mach-omap2/voltage.h | 180
-
Hi,
On Mon, Jul 18, 2011 at 08:35:18PM +0300, Tero Kristo wrote:
These are now under plat-omap/include/plat.
Signed-off-by: Tero Kristo t-kri...@ti.com
this has to be folded into previous patch, otherwise we will have a
broken bisection point.
--
balbi
signature.asc
Description: Digital
Hi,
On Mon, Jul 18, 2011 at 08:35:19PM +0300, Tero Kristo wrote:
diff --git a/drivers/regulator/omap-smps-regulator.c
b/drivers/regulator/omap-smps-regulator.c
new file mode 100644
index 000..8b56e4f
--- /dev/null
+++ b/drivers/regulator/omap-smps-regulator.c
@@ -0,0 +1,179 @@
+/*
+
Hi,
On Mon, Jul 18, 2011 at 08:35:20PM +0300, Tero Kristo wrote:
diff --git a/arch/arm/mach-omap2/twl-common.h
b/arch/arm/mach-omap2/twl-common.h
index 5e83a5b..fde8467 100644
--- a/arch/arm/mach-omap2/twl-common.h
+++ b/arch/arm/mach-omap2/twl-common.h
@@ -25,6 +25,11 @@
#define
On 7/15/2011 9:34, Jon Hunter wrote:
2). The ocp_abe_iclk is an interface clock and is not a parent to any
other functional clock and therefore, is not driving any internal logic
in a peripheral which would have a direct impact of the speed of that
peripheral. However, there does appear to be
On 7/18/2011 15:57, Jon Hunter wrote:
On further inspection of the clock44xx_data.c, it appears that all
interface clocks are called xxx_fck and not xxx_ick. I will ask Benoit
about this. However, this particular clock we are dealing with here is
an interface clock.
Actually, the above it not
Hi!
@@ -0,0 +1,75 @@
+What:/sys/bus/rpmsg/devices/.../name
+Date:June 2011
+KernelVersion: 3.2
+Contact: Ohad Ben-Cohen o...@wizery.com
+Description:
+ Every rpmsg device is a communication channel with a remote
+
On Thu, Jul 14, 2011 at 10:37 PM, Govindraj govindraj...@gmail.com wrote:
On Fri, Jul 15, 2011 at 12:19 AM, Nick Pelly npe...@google.com wrote:
Fixes logic bug that software flow control cannot be disabled, because
serial_omap_configure_xonxoff() is not called if both IXON and IXOFF bits
On Sat, Jul 16, 2011 at 4:22 AM, Sergei Shtylyov sshtyl...@mvista.com wrote:
Hello.
On 16-07-2011 3:44, Vikram Pandita wrote:
From: Vikram Pandita vikram.pand...@ti.com
This patch enables the DMA mode1 RX support.
This feature is enabled based on the short_not_ok flag passed from
gadget
Felipe Balbi ba...@ti.com writes:
On Mon, Jul 18, 2011 at 08:35:19PM +0300, Tero Kristo wrote:
diff --git a/drivers/regulator/omap-smps-regulator.c
b/drivers/regulator/omap-smps-regulator.c
new file mode 100644
index 000..8b56e4f
--- /dev/null
+++
Tero Kristo t-kri...@ti.com writes:
This is needed so that these include files can be accessed from drivers.
I think you can get by with a plat/voltage.h with simply an opaque
struct voltagedomain, and the definitions of the functions needed by the
regulator driver (currently only voltdm_scale,
From: Vikram Pandita vikram.pand...@ti.com
This patch enables the DMA mode1 RX support.
This feature is enabled based on the short_not_ok flag passed from
gadget drivers.
This will result in a thruput performance gain of around
40% for USB mass-storage/mtp use cases.
Based on Original work by
:
This is a test message.
Best Regards,
Smart Williams
wsmar...@yahoo.nl
Sent on 2011-07-18
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
Hi Pavel,
On Thu, Jun 9, 2011 at 8:12 PM, Pavel Machek pa...@ucw.cz wrote:
So this is basically networking... right? Why not implement it as
sockets? (accept, connect, read, write)?
This patch focuses on adding the core rpmsg kernel infrastructure. The
next step, after getting the basic stuff
Grant/Kevin,
On Sun, Jul 17, 2011 at 10:43 AM, Grant Likely
grant.lik...@secretlab.ca wrote:
Hi Manjunath,
Comments below. I left in a lot of context for the new folks that
I've cc'd (Tony and Kevin).
On Sat, Jul 16, 2011 at 2:07 PM, G, Manjunath Kondaiah manj...@ti.com wrote:
On Thu, Jul
34 matches
Mail list logo
