Since we need to reconfigure Reset time for OMAP4, we found the OMAP4
register definition for reset time is wrong according to spec of
OMAP4. And we verified this by reading default value of register. We
found the offset definition of Reset time and Reset Test register
should be switched. After
On Mon, Dec 06, 2010 at 11:27:45AM -0700, Paul Walmsley wrote:
On Mon, 6 Dec 2010, Tony Lindgren wrote:
* Russell King - ARM Linux li...@arm.linux.org.uk [101206 04:45]:
NET: Registered protocol family 16
[ cut here ]
WARNING: at
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of MING ZHOU
Sent: Tuesday, December 07, 2010 1:04 PM
To: linux-omap@vger.kernel.org
Cc: Tony Lindgren; Paul Walmsley
Subject: [PATCH] Correct definition of register of
thanks
On 02/12/10 10:37, ext Herbert Xu wrote:
On Tue, Nov 30, 2010 at 10:13:26AM +0200, Dmitry Kasatkin wrote:
Changes to v1:
- omap type specific handling removed
- fixed backlog handling bug in redundunt locking is removed
- aes module initialized once per request instead of dma
Hi
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2, but I'm getting no connection - neither over
the SMSC chip, nor over usb-device in gadget mode, nor can I power on the
on-board hub to plug in a usb-to-eth dongle. What's the catch? How do I
Hi Paul,
On Mon, Dec 06, 2010 at 06:40:38PM -0700, Paul Walmsley wrote:
On Tue, 7 Dec 2010, Bryan Wu wrote:
On Tue, Dec 7, 2010 at 8:35 AM, Paul Walmsley p...@pwsan.com wrote:
Fix the following section mismatch warning when building
omap2plus_defconfig:
WARNING:
Hi,
On Tue, Dec 07, 2010 at 10:42:45AM +0100, Guennadi Liakhovetski wrote:
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2, but I'm getting no connection - neither over
the SMSC chip, nor over usb-device in gadget mode, nor can I power on the
Hi Felipe
On Tue, 7 Dec 2010, Felipe Balbi wrote:
Hi,
On Tue, Dec 07, 2010 at 10:42:45AM +0100, Guennadi Liakhovetski wrote:
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2, but I'm getting no connection - neither over
the SMSC chip, nor
Hi,
On Tue, Dec 07, 2010 at 10:56:45AM +0100, Guennadi Liakhovetski wrote:
On Tue, Dec 07, 2010 at 10:42:45AM +0100, Guennadi Liakhovetski wrote:
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2, but I'm getting no connection - neither over
the
On Tue, Dec 7, 2010 at 6:31 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Dave,
-Original Message-
From: linaro-dev-boun...@lists.linaro.org [mailto:linaro-dev-
boun...@lists.linaro.org] On Behalf Of Dave Martin
Sent: Monday, December 06, 2010 11:06 PM
To:
On Tue, 7 Dec 2010, Felipe Balbi wrote:
Hi,
On Tue, Dec 07, 2010 at 10:56:45AM +0100, Guennadi Liakhovetski wrote:
On Tue, Dec 07, 2010 at 10:42:45AM +0100, Guennadi Liakhovetski wrote:
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2,
Luca Ceresoli wrote:
While I thank you for you proposed solution, I see it does not work here.
In fact I commented the #define CONFIG_MTD_NAND_OMAP_HWECC and left
MTD_NAND_OMAP_PREFETCH disabled as it previously was, and got compilation
errors:
Wrong, sorry. Your solution compiles and works.
Op 7 dec 2010, om 10:42 heeft Guennadi Liakhovetski het volgende geschreven:
Hi
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2, but I'm getting no connection - neither over
the SMSC chip, nor over usb-device in gadget mode, nor can I power
On Tue, Dec 07, 2010 at 11:17:18AM +0100, Guennadi Liakhovetski wrote:
On Tue, 7 Dec 2010, Felipe Balbi wrote:
Hi,
On Tue, Dec 07, 2010 at 10:56:45AM +0100, Guennadi Liakhovetski wrote:
On Tue, Dec 07, 2010 at 10:42:45AM +0100, Guennadi Liakhovetski wrote:
I managed to bring a mainline
-Original Message-
From: Taneja, Archit
Sent: Thursday, November 04, 2010 1:26 PM
To: Hiremath, Vaibhav
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org; Taneja,
Archit
Subject: [PATCH v3 0/3] V4L/DVB: OMAP_VOUT: Allow omap_vout to build
without VRFB
[Hiremath,
-Original Message-
From: Taneja, Archit
Sent: Thursday, November 04, 2010 1:26 PM
To: Hiremath, Vaibhav
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org; Taneja,
Archit
Subject: [PATCH v3 2/3] V4L/DVB: OMAP_VOUT: Create a seperate vrfb
[Hiremath, Vaibhav] Spelling
-Original Message-
From: Taneja, Archit
Sent: Thursday, November 04, 2010 1:26 PM
To: Hiremath, Vaibhav
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org; Taneja,
Archit
Subject: [PATCH v3 1/3] V4L/DVB: OMAP_VOUT: Move some functions and
preprocessor defines from
-Original Message-
From: Taneja, Archit
Sent: Thursday, November 04, 2010 1:26 PM
To: Hiremath, Vaibhav
Cc: linux-me...@vger.kernel.org; linux-omap@vger.kernel.org; Taneja,
Archit
Subject: [PATCH v3 3/3] V4L/DVB: OMAP_VOUT: Use rotation_type to choose
between vrfb rotation and no
Hi Tony,
* G, Manjunath Kondaiah manj...@ti.com [2010-12-04 09:13:57 +0530]:
Patch series to convert DMA library into platform driver using platform
device model and adapting hwmod for omap2+.
The original patch series :
http://comments.gmane.org/gmane.linux.ports.arm.omap/46953
has been
From: Jean Pihet j-pi...@ti.com
Clean up of the ASM code:
- reorganized the code in logical sections: defines, API
functions, internal functions and variables,
- reworked and simplified the execution paths, for better
readability and to avoid duplication of code,
- added comments on the
On Tue, 7 Dec 2010, Koen Kooi wrote:
Op 7 dec 2010, om 10:42 heeft Guennadi Liakhovetski het volgende geschreven:
Hi
I managed to bring a mainline 2.6.36 kinda kernel to run on my bbxm,
Debian rootfs in mmcblk0p2, but I'm getting no connection - neither over
the SMSC chip, nor
Hi Dave,
On Tue, Dec 7, 2010 at 11:16 AM, Dave Martin dave.mar...@linaro.org wrote:
On Tue, Dec 7, 2010 at 6:31 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Dave,
-Original Message-
From: linaro-dev-boun...@lists.linaro.org [mailto:linaro-dev-
boun...@lists.linaro.org] On
Fix the following build error by including linux/err.h
arch/arm/plat-omap/counter_32k.c: In function 'omap_init_clocksource_32k':
arch/arm/plat-omap/counter_32k.c:167: error: implicit declaration of
function 'IS_ERR'
The above error is due to the following
On Tue, Dec 07, 2010 at 05:39:37PM +0530, Sourav Poddar wrote:
Fix the following build error by including linux/err.h
arch/arm/plat-omap/counter_32k.c: In function 'omap_init_clocksource_32k':
arch/arm/plat-omap/counter_32k.c:167: error: implicit declaration of
The .gpio_cd member of omap2_hsmmc_info is not initialized. This
will default to zero. On Pandaboard this interferes with gpio line
assigned for powering TFP410 DVI chip.
This fix was missed out in the previous commit bf56f0a6668cd, from
Nishanth Menon
Signed-off-by: Kishore Kadiyala
This patch adds omap_reserve functionality to board-omap4panda.c.
Helps in the reserving boot time memory in SDRAM, used here for
framebuffer allocation.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
Signed-off-by: Raghuveer Murthy raghuveer.mur...@ti.com
---
From: Koen Kooi k...@dominion.thruhere.net
Signed-off-by: Koen Kooi k...@beagleboard.org
---
arch/arm/mach-omap2/board-omap3beagle.c | 27 +++
1 files changed, 23 insertions(+), 4 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
Op 7 dec 2010, om 13:40 heeft Koen Kooi het volgende geschreven:
+ /* Power on camera interface on P7/P8 or DVI on A2 and beyond */
+ if (omap3_beagle_get_rev() == OMAP3BEAGLE_BOARD_XM) {
+ gpio_request(gpio + 2, CAM_EN);
+ gpio_direction_output(gpio + 2, 1);
-Original Message-
From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
Sent: Thursday, December 02, 2010 4:24 PM
To: Cousson, Benoit
Cc: Basak, Partha; ABRAHAM, KISHON VIJAY; Paul Walmsley; linux-
o...@vger.kernel.org; Kamat, Nishant; Varadarajan, Charulatha; Datta,
Hello.
On 06-12-2010 20:54, Tony Lindgren wrote:
As the control.h have been moved to new location and it's
uses are not allowed to drivers directly so moving the phy
control, interrupt clear and reset functionality to board
files.
I'm not fond of the whole approach. I'm not sure why
On Mon, Dec 06, 2010 at 06:25:17PM -0700, Paul Walmsley wrote:
In preparation for adding OMAP4-specific PRCM accessor/mutator
functions, split the existing OMAP2/3 PRCM code into OMAP2/3-specific
files. Most of what was in mach-omap2/{cm,prm}.{c,h} has now been
moved into
This patch series has the support for TWL6030-usb
transceiver driver and changes in the musb driver to make it functional
with OMAP4430.
OMAP4 musb support UTMI and ULPI transceiver interfaces.
In UTMI mode, the transceiver functionality is split between
the TWL6030 PMIC chip and OMAP4 embedded
With TWL6030-usb, VBUS SESS_VLD and SESS_END events are not generated
as expected. When these interrupts are enabled, charger VBUS detection
interrupt does not get generated. So USBOTG has to be dependent on charger
VBUS interrupts.
So added one bit for USBOTG and changed the handler to call the
Adding the twl6030-usb transceiver support for OMAP4 musb driver.
OMAP4 supports 2 types of transceiver interface.
1. UTMI: The PHY is embedded within OMAP4. The transceiver functionality
is split between the twl6030 PMIC chip and OMAP4430. The VBUS, ID pin
sensing and OTG SRP generation part
Added the TWL6030-usb transceiver option in the Kconfig
Signed-off-by: Hema HK hem...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: David Brownell dbrown...@users.sourceforge.net
---
drivers/usb/otg/Kconfig | 12
1 file changed, 12 insertions(+)
Index:
Registering the twl6030-usb transceiver device as a child to twl6030 core.
Removed the NOP transceiver init call from board file.
Populated twl4030_usb_data platform data structure with the function
pointers for OMAP4430 internal PHY operation to be used twl630-usb driver.
Signed-off-by: Hema
Selecting the twl6030-usb for OMAP4430SDP and OMAP4 PANDA board and
adding OMAP4 internal phy code for compilation
Signed-off-by: Hema HK hem...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/Makefile |1 +
drivers/usb/musb/Kconfig |1
OMAP4430 supports UTMI and ULPI types of transceiver interface.
In UTMI mode: The PHY is embedded within OMAP4430. The transceiver functionality
is split between the twl6030 PMIC chip and OMAP4430. The VBUS, ID pin
sensing and OTG SRP generation part is integrated in TWL6030 and UTMI PHY
musb device registration during board initialization of OMAP4430SDP
and OMAP4430 PANDA.Enable the musb OTG mode.
Signed-off-by: Hema HK hem...@ti.com
Cc: Felipe Balbi ba...@ti.com
Cc: Tony Lindgren t...@atomide.com
---
arch/arm/mach-omap2/board-4430sdp.c|6 ++
Raghuveer Murthy had written, on 12/07/2010 06:25 AM, the following:
This patch adds omap_reserve functionality to board-omap4panda.c.
Helps in the reserving boot time memory in SDRAM, used here for
framebuffer allocation.
Signed-off-by: Russell King rmk+ker...@arm.linux.org.uk
Since Russell
Hi,
Is AM35x that different ? Can't you just write to MUSB_INTRRX
MUSB_INTRTX and MUSB_INTRUSB ??
Writing to MUSB_INTRRX/TX/USB wouldn't help. We have to clear interrupt
Bit in control register INTR_LVL_CLR.
I see, thanks for the info :-)
Felipe,
I have recreated this patch (attached)
Hi,
On Tue, Dec 7, 2010 at 11:59 AM, Jean Pihet jean.pi...@newoldbits.com wrote:
Hi Dave,
On Tue, Dec 7, 2010 at 11:16 AM, Dave Martin dave.mar...@linaro.org wrote:
On Tue, Dec 7, 2010 at 6:31 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Dave,
-Original Message-
From:
On Tue, Dec 7, 2010 at 2:53 PM, Dave Martin dave.mar...@linaro.org wrote:
[...]
Note that converting to C doesn't mean that code which attempts to
copy function bodies will work: you still need to handle the fact that
if f() is a C function symbol, then the value of the symbol f is
actually
Hello,
On Tue, 7 Dec 2010, MING ZHOU wrote:
Since we need to reconfigure Reset time for OMAP4, we found the OMAP4
register definition for reset time is wrong according to spec of
OMAP4. And we verified this by reading default value of register. We
found the offset definition of Reset time
Hello Samuel,
On Tue, 7 Dec 2010, Samuel Ortiz wrote:
On Mon, Dec 06, 2010 at 06:40:38PM -0700, Paul Walmsley wrote:
That's fine with me. Samuel et al, Bryan's already done a patch
for this stuff:
https://patchwork.kernel.org/patch/367011/
so we should use that instead, if
Hi Paul,
On 12/7/2010 5:04 PM, Paul Walmsley wrote:
Hello,
On Tue, 7 Dec 2010, MING ZHOU wrote:
Since we need to reconfigure Reset time for OMAP4, we found the OMAP4
register definition for reset time is wrong according to spec of
OMAP4. And we verified this by reading default value of
On Tue, Dec 07, 2010 at 07:25:12PM +0530, Gupta, Ajay Kumar wrote:
Hi,
Is AM35x that different ? Can't you just write to MUSB_INTRRX
MUSB_INTRTX and MUSB_INTRUSB ??
Writing to MUSB_INTRRX/TX/USB wouldn't help. We have to clear interrupt
Bit in control register INTR_LVL_CLR.
I see, thanks for
Hi,
On Tue, Dec 7, 2010 at 6:28 AM, Santosh Shilimkar
santosh.shilim...@ti.com wrote:
Dave,
-Original Message-
From: linaro-dev-boun...@lists.linaro.org [mailto:linaro-dev-
boun...@lists.linaro.org] On Behalf Of Dave Martin
Sent: Monday, December 06, 2010 11:06 PM
To:
This makes sense, because Thumb-2 code can't execute on anything
prior to ARMv7.
This will avoid accidentally configuring a broken kernel where the
config otherwise would allow multiple architecture versions to
coexist in the same kernel.
Not adding !CPU_V5 etc., because the chance of anyone
On Friday, December 03, 2010 15:54:08 Mark Brown wrote:
On Fri, Dec 03, 2010 at 02:50:58PM +0100, Laurent Pinchart wrote:
On Friday 03 December 2010 13:06:18 Hans Verkuil wrote:
Just to confirm thinks, Mark's proposal is to replace 'connected' by
'linked' and 'active' by 'connected'.
On Tue, Dec 07, 2010 at 06:13:35PM +0100, Hans Verkuil wrote:
Personally I think this is perfectly clear. The original confusion came from
the word 'active', which I understand means 'streaming' in alsa. By adding
a 'streaming' flag in addition to the active flag I think it will be clear
that
On Tuesday, December 07, 2010 18:55:05 Mark Brown wrote:
On Tue, Dec 07, 2010 at 06:13:35PM +0100, Hans Verkuil wrote:
Personally I think this is perfectly clear. The original confusion came from
the word 'active', which I understand means 'streaming' in alsa. By adding
a 'streaming' flag
Madhusudhan,
On my OMAP35xx BeagleBoard here, HSMMC is non-functional after returning
from dynamic off-mode. The MMC LED turns on and stays on, and the process
hangs, although the rest of the system still seems to run. Looks like
you're listed as the maintainer for this code. Do you know
Paul,
Last I tested OFF mode was after Adrian's power saving series was merged. I
tested it on Kevin PM branch then and it was functional on my omap3 board.
I need to check on the latest commit.
Did you see this problem in suspend/resume path or the cpuidle path?
Regards,
Madhu
On Tue, Dec 7,
Hello Madhusudhan,
On Tue, 7 Dec 2010, Chikkature Rajashekar, Madhusudhan wrote:
Last I tested OFF mode was after Adrian's power saving series was merged. I
tested it on Kevin PM branch then and it was functional on my omap3 board.
I need to check on the latest commit.
Did you see this
On Tue, Dec 07, 2010 at 07:11:39PM +0100, Hans Verkuil wrote:
Ah, now I understand what you mean. Would 'activated' be better than 'active'?
Better, yes, though it still sounds a bit like something should be
actively (IYSWIM) happening. In the absence of better ideas I could go
with this.
On Tue, 7 Dec 2010, Dave Martin wrote:
On Tue, Dec 7, 2010 at 2:53 PM, Dave Martin dave.mar...@linaro.org wrote:
[...]
Note that converting to C doesn't mean that code which attempts to
copy function bodies will work: you still need to handle the fact that
if f() is a C function symbol,
On Tue, Dec 07, 2010 at 04:50:50PM +, Dave Martin wrote:
I'll follow up shortly with a patch to the generic ARM Kconfig to make
this explicit, so that ARCH_OMAP2 and THUMB2_KERNEL can't accidentally
be configured together.
That's a rubbish dependency. You may have an ARCH_OMAP2 platform
On 07/12/10 20:21, ext Paul Walmsley wrote:
Madhusudhan,
On my OMAP35xx BeagleBoard here, HSMMC is non-functional after returning
from dynamic off-mode. The MMC LED turns on and stays on, and the process
hangs, although the rest of the system still seems to run. Looks like
you're listed as
On Fri, Nov 05, 2010 at 02:29:02PM -0700, Tony Lindgren wrote:
Hi Greg,
Considering below..
* Peter Ujfalusi peter.ujfal...@nokia.com [101021 02:56]:
Sorry, I did missed this mail...
On Saturday 09 October 2010 01:17:46 ext Tony Lindgren wrote:
Guys, as we're so late into
On 12/7/2010 2:25 AM, Paul Walmsley wrote:
[...]
+ *
+ * XXX This file needs to be updated to align on one of OMAP4, OMAP44XX,
+ * or OMAP4430.
Yep, I was thinking to change that as well. My first thought was OMAP4
to get a shorter name, but when we will introduce OMAP4440, we might
commit 0d8e2d0dad98a693bad88aea6876ac8b94ad95c6 (OMAP2+: PM/serial:
hold console semaphore while OMAP UARTs are disabled) added use of the
console semaphore to protect UARTs from being accessed after disabled
during idle, but this causes problems in suspend.
During suspend, the console semaphore
On Tue, Dec 7, 2010 at 1:51 PM, Adrian Hunter adrian.hun...@nokia.com wrote:
On 07/12/10 20:21, ext Paul Walmsley wrote:
Madhusudhan,
On my OMAP35xx BeagleBoard here, HSMMC is non-functional after returning
from dynamic off-mode. The MMC LED turns on and stays on, and the process
hangs,
Tony Lindgren t...@atomide.com writes:
* Kevin Hilman khil...@deeprootsystems.com [101124 16:32]:
Paul Walmsley p...@pwsan.com writes:
snip
Acked-by: Kevin Hilman khil...@deeprootsystems.com
Very nice. I've been exploring various solutions to this problem as
well, but this one is much
Hi,
What should I do to change the output frequency of mmc2_clk signal to
48Mhz for the OMAP35xx processor?
Right now it is giving an output of 96MHz and the signal output looks more like
a sine wave than a square wave clock output signal.
Elvis Dowson
--
To unsubscribe from this
Sourav Poddar sourav.pod...@ti.com writes:
Fix the following build error by including linux/err.h
arch/arm/plat-omap/counter_32k.c: In function 'omap_init_clocksource_32k':
arch/arm/plat-omap/counter_32k.c:167: error: implicit declaration of
function
On Tue, Dec 7, 2010 at 9:50 PM, Kevin Hilman
khil...@deeprootsystems.com wrote:
commit 0d8e2d0dad98a693bad88aea6876ac8b94ad95c6 (OMAP2+: PM/serial:
hold console semaphore while OMAP UARTs are disabled) added use of the
console semaphore to protect UARTs from being accessed after disabled
On Tue, 7 Dec 2010, Kevin Hilman wrote:
commit 0d8e2d0dad98a693bad88aea6876ac8b94ad95c6 (OMAP2+: PM/serial:
hold console semaphore while OMAP UARTs are disabled) added use of the
console semaphore to protect UARTs from being accessed after disabled
during idle, but this causes problems in
Paul Walmsley p...@pwsan.com writes:
Hi Kevin
On Thu, 2 Dec 2010, Kevin Hilman wrote:
I guess this hasn't been seen before since we haven't tested the sysfs
wakeup interface for the omap-serial driver. For on-chip OMAP UARTs,
using the sysfs interface isn't needed as the serial core is
Paul Walmsley p...@pwsan.com writes:
On Mon, 22 Nov 2010, Kevin Hilman wrote:
Paul Walmsley p...@pwsan.com writes:
On Tue, 16 Nov 2010, Paul Walmsley wrote:
This patch series contains upgrades for the OMAP2+ hwmod core
code, intended for 2.6.38. Most of these patches were developed
* Varadarajan, Charulatha ch...@ti.com [101206 22:58]:
On Tue, Dec 7, 2010 at 11:05, Varadarajan, Charulatha ch...@ti.com wrote:
On Tue, Dec 7, 2010 at 10:49, Cory Maccarrone darkstar6...@gmail.com
wrote:
omap_gpio omap_gpio.5: Could not get gpio dbck
omap_gpio omap_gpio.6:
Benoit Cousson b-cous...@ti.com writes:
Hi All,
In order to enforce a little bit of consistency in the omap devices name,
the convention for omap devices name will be now omap_XXX. All the drivers
adapted to hwmod will be named like that during the on-going adaptations.
The I2C and UART
Marek Belisko marek.beli...@open-nandra.com writes:
Fix following compilation warning:
arch/arm/mach-omap1/pm_bus.c: In function 'omap1_pm_runtime_resume':
arch/arm/mach-omap1/pm_bus.c:51: warning: unused variable 'ret'
Signed-off-by: Marek Belisko marek.beli...@open-nandra.com
Acked-by:
Hi,
Two comments:
On Tue, 7 Dec 2010, Kevin Hilman wrote:
commit 0d8e2d0dad98a693bad88aea6876ac8b94ad95c6 (OMAP2+: PM/serial:
hold console semaphore while OMAP UARTs are disabled) added use of the
console semaphore to protect UARTs from being accessed after disabled
during idle, but this
Hi,
On Tue, 7 Dec 2010, Chikkature Rajashekar, Madhusudhan wrote:
On Tue, Dec 7, 2010 at 1:51 PM, Adrian Hunter adrian.hun...@nokia.com wrote:
It is at least because omap_pm_get_dev_context_loss_count() is not
implemented. Tero Kristo was looking at that recently.
Yes. I agree that
* Tony Lindgren t...@atomide.com [101204 13:16]:
* Varadarajan, Charulatha ch...@ti.com [101202 06:08]:
On Thu, Dec 2, 2010 at 15:28, Kevin Hilman khil...@deeprootsystems.com
wrote:
Tony, you can also add
Acked-by: Kevin Hilman khil...@deeprootsystems.com
OK, updated. Also
In the OMAP HSMMC driver, the code path entered via mmc_host_enable() can
include register accesses to the HSMMC IP block. For this to work, both
the device interface clock and functional clock need to be enabled before
mmc_host_enable() is called. However, omap_hsmmc_probe() calls
Hi,
Looks like 0xfa09c014 is the MMC SYSSTATUS register... maybe there's
something wrong with the clock control.
Just sent a patch for this one, it's relatively minor.
After applying it and the 'brutal context save/restore test' patch, HSMMC
off-mode indeed seems to work much better.
Are
commit 0d8e2d0dad98a693bad88aea6876ac8b94ad95c6 (OMAP2+: PM/serial:
hold console semaphore while OMAP UARTs are disabled) added use of the
console semaphore to protect UARTs from being accessed after disabled
during idle, but this causes problems in suspend.
During suspend, the console semaphore
On Sun, 5 Dec 2010 12:06:03 +0200
Ohad Ben-Cohen o...@wizery.com wrote:
Introduce BUG_ON_MAPPABLE_NULL in order to eliminate redundant BUG_ON
code, checking for NULL addresses, on architectures where the zero
address can never be mapped.
Originally proposed by Russell King
On Tuesday 07 December 2010 23:29:59 Luca Ceresoli wrote:
Luca Ceresoli wrote:
While I thank you for you proposed solution, I see it does not work here.
In fact I commented the #define CONFIG_MTD_NAND_OMAP_HWECC and left
MTD_NAND_OMAP_PREFETCH disabled as it previously was, and got
Paul Walmsley p...@pwsan.com writes:
This patch series, intended for 2.6.38:
[...]
Kevin, I'd appreciate review and acks, if appropriate, on the patches
that touch code that you maintain.
Reviewed-by: Kevin Hilman khil...@deeprootsystems.com
Tested-by: Kevin Hilman
On Tue, 7 Dec 2010, Russell King - ARM Linux wrote:
So LDP will remain unusable until after the 2.6.38 merge window?
I don't think that Tony or I realized that LDP3430 was broken until your
E-mail. Usually I use a BeagleBoard 35xx for OMAP3430 testing, and I
think Tony uses an Overo. The
* Varadarajan, Charulatha ch...@ti.com [101125 04:39]:
Implement OMAP GPIO module in platform device model. OMAP2+ specific GPIO
module uses hwmod FW.
I'll add the following patch underneath this series as otherwise some
gpio_request calls will fail after this series.
Regards,
Tony
From:
* Tony Lindgren t...@atomide.com [101207 15:13]:
Note that this will cause omap-keypad.c driver to not work on 7xx.
However, the right fix there is to move over to gpio-keys instead as
suggested by Cory Maccarrone darkstar6...@gmail.com and
Janusz Krzysztofik jkrzy...@tis.icnet.pl.
Updated
Hi Jean,
Jean Pihet jean.pi...@newoldbits.com writes:
Some bad interaction between the idle and the suspend paths has been
noticed: the idle code is called during the suspend enter and exit
sequences. This could cause corruption or lock-up of resources.
The solution is to move the call to
Kernel was failing to boot on omap1611 based OSK boards due to
mis-configured SRAM size. Existing code was using a hard-coded value
for 250k, which was then rounded down by PAGE_SIZE. Increasing this to
256k allows kernel to boot on omap1611 SoCs.
Problem reported by and initial fix suggested
* Tony Lindgren t...@atomide.com [101204 13:27]:
These should be now long gone and break multi-omap support for omap1
as the cpu_class_is_omap1() won't work until the SOC is detected.
So just disable and warn for omap2+ in case somebody still attampts
to use these.
Heh this was totally not
On Wed, Dec 8, 2010 at 12:12 AM, Paul Walmsley p...@pwsan.com wrote:
Hello Samuel,
On Tue, 7 Dec 2010, Samuel Ortiz wrote:
On Mon, Dec 06, 2010 at 06:40:38PM -0700, Paul Walmsley wrote:
That's fine with me. Samuel et al, Bryan's already done a patch
for this stuff:
* Tony Lindgren t...@atomide.com [101204 19:00]:
* Nicolas Pitre n...@fluxnic.net [101204 18:26]:
On Sat, 4 Dec 2010, Tony Lindgren wrote:
My only problem with your approach is the global addition of
asm_irq_base and asm_irq_flags in generic code which might not be useful
and/or
This way we can use the generic omap SoC detection code instead.
Signed-off-by: Tony Lindgren t...@atomide.com
diff --git a/arch/arm/mach-omap2/include/mach/entry-macro.S
b/arch/arm/mach-omap2/include/mach/entry-macro.S
index 06e64e1..6032941 100644
---
This saves some cycles for multiple interrupts case.
Signed-off-by: Tony Lindgren t...@atomide.com
diff --git a/arch/arm/mach-omap1/include/mach/entry-macro.S
b/arch/arm/mach-omap1/include/mach/entry-macro.S
index c9be6d4..584bf7b 100644
--- a/arch/arm/mach-omap1/include/mach/entry-macro.S
+++
Initialize asm_irq_flags in omap_init_irq and use it in
get_irqnr_and_base to detect between omap7xx and omap15xx/16xx.
Note that both INT_1510_IH2_IRQ and INT_1510_IH2_IRQ are defined
as 0, so use INT_1510_IH2_IRQ for both of them.
Signed-off-by: Tony Lindgren t...@atomide.com
diff --git
* Felipe Contreras felipe.contre...@gmail.com [101207 04:28]:
On Sat, Dec 4, 2010 at 11:36 PM, Tony Lindgren t...@atomide.com wrote:
The omap1_defconfig this should be eventually usable for booting
all omap1 machines. Generated based on:
$ grep ARCH_OMAP1=y arch/arm/configs/* | cut -d:
Hema,
On Tue, Dec 7, 2010 at 6:11 PM, Hema HK hem...@ti.com wrote:
Adding the twl6030-usb transceiver support for OMAP4 musb driver.
OMAP4 supports 2 types of transceiver interface.
+}
+
+int omap4430_phy_set_clk(struct device *dev, int on)
+{
+ static int state;
probably good to
This patch will kill following section mismatch warnings:
WARNING: vmlinux.o(.text+0x24a00): Section mismatch in reference from the
function zoom_twl_gpio_setup() to the (unknown reference) .init.data:(unknown)
The function zoom_twl_gpio_setup() references
the (unknown reference) __initdata
Fix the following section mismatch warning when building omap2plus_defconfig:
WARNING: vmlinux.o(.data+0x47d7c): Section mismatch in reference from the
variable twl_driver to the function .init.text:twl_probe()
Signed-off-by: Bryan Wu bryan...@canonical.com
Signed-off-by: Paul Walmsley
On Tue, 7 Dec 2010, Paul Walmsley wrote:
I do have a LDP3430 here though. It doesn't boot past:
[0.00] Linux version 2.6.37-rc5 (p...@twilight) (gcc version 4.3.2
(Sourcery G++ Lite 2008q3-72) ) #68 SMP Tue Dec 7 17:42:20
[0.00] CPU: ARMv7 Processor [411fc083] revision 3
* Tony Lindgren t...@atomide.com [101207 17:32]:
* Tony Lindgren t...@atomide.com [101204 13:27]:
These should be now long gone and break multi-omap support for omap1
as the cpu_class_is_omap1() won't work until the SOC is detected.
So just disable and warn for omap2+ in case somebody
This patch series has the support for TWL6030-usb
transceiver driver and changes in the musb driver to make it functional
with OMAP4430.
OMAP4 musb support UTMI and ULPI transceiver interfaces.
In UTMI mode, the transceiver functionality is split between
the TWL6030 PMIC chip and OMAP4 embedded
1 - 100 of 124 matches
Mail list logo
