Hi Charu,
On Wed, Aug 12, 2009 at 9:15 PM, ch...@ti.com wrote:
Triton2 RTC code changes for fixing periodic interrupt feature in RTC.
rtc-twlcore.c does initialisation of the msecure gpio pin.
Board files indicate msecure gpio line through twl4030 platform data.
twl4030-core.c passes this
Hi
I would like to add these tree patches to recent set:
[PATCHv5 00/20] OMAP ASoC changes in DMA utilization
http://mailman.alsa-project.org/pipermail/alsa-devel/2009-August/020619.html
These are actually independent patches but probably easier to handle as with
the set above since some of the
Use more descriptive than numerical value when showing and storing the
McBSP DMA operating mode. Show function is using similar syntax than e.g.
the led triggers so that all possible values for store function are
printed but with current value surrounded with square brackets.
Signed-off-by:
Commit ca6e2ce08679c094878d7f39a0349a7db1d13675 is setting up few XCCR and
RCCR bits for I2S and DPS_A formats. Part of the bits are already set
for all formats and I believe that XDISABLE and RDISABLE bits are
format independent.
As XCCR and RCCR are found only from OMAP2430 and OMAP34xx, I move
Functionality of functions omap_mcbsp_xmit_enable and omap_mcbsp_recv_enable
can be merged into omap_mcbsp_start and omap_mcbsp_stop since API of
those omap_mcbsp_start and omap_mcbsp_stop was changed recently allowing
to start and stop individually the transmitter and receiver.
This cleans up
All,
This patch series is intended to free up the kernel IO address space for
OMAP2XXX, OMAP3XXX and OMAP4430. It is generated against Tony's
omap-headers (2.6.31-rc6) branch and boot tested on OMAP3430 SDP and OMAP4430
platform.
Some more combinations are possible but to make it uniform
This patch splits OMAP2_IO_ADDRESS to OMAP2_L3_IO_ADDRESS and
OMAP2_L4_IO_ADDRESS to reclaim more IO space.
The omap_read*() and omap_write*() functions will work only over
L4 address space. Current omap kernel stack uses these functions
only to access registers over L4 io address space
This patch remap L3 and L4 io space to get more kernel address space.
With this patch, 512 MB of IO space is reclaimed.
Some more combinations are possible but to make it uniform across
OMAP24XX, OMAP34XX and OMAP4430, these io combinations are chosen
Once this is reviewed and tested
This patch moves SRAM map to free up more kernel address io space.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/plat-omap/sram.c |6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm/plat-omap/sram.c b/arch/arm/plat-omap/sram.c
index
This patch adds few necessary peripherals for OMAP4.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/io.c | 18 +
arch/arm/plat-omap/include/mach/io.h | 29 +--
This patch fixes the low level debug UART io address as per this series.
The change is essential to have CONFIG_DEBUG_LL working.
Signed-off-by: Santosh Shilimkar santosh.shilim...@ti.com
---
arch/arm/mach-omap2/board-2430sdp.c |2 +-
arch/arm/mach-omap2/board-3430sdp.c |
On Fri, 2009-08-21 at 00:39 +0530, Anuj Aggarwal wrote:
Adding support for TI TPS65023 regulator driver
Signed-off-by: Anuj Aggarwal anuj.aggar...@ti.com
---
drivers/regulator/tps65023-regulator.c | 631
1 files changed, 631 insertions(+), 0 deletions(-)
Santosh
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of
Shilimkar, Santosh
Sent: Sunday, August 23, 2009 8:35 AM
To: t...@atomide.com; khil...@deeprootsystems.com
Cc: linux-omap@vger.kernel.org; Shilimkar, Santosh
Subject:
Implement DMA channel self linking on OMAP1510 using AUTO_INIT and REPEAT
flags of the DMA CCR register.
Created against linux-2.6.31-rc5.
Tested on Amstrad Delta.
Signed-off-by: Janusz Krzysztofik jkrzy...@tis.icnet.pl
---
I'm sorry, but the original patch appears to have an issue. To be
On Sun, Aug 23, 2009 at 05:56:12PM +0200, Janusz Krzysztofik wrote:
I know it's not very fair to change the patch after others that depend on it
have already been applied, but I hope there will be no problems with accepting
the way I have reimplemented it. In any case, I'll appreciate any
Sunday 23 August 2009 19:03:59 Mark Brown wrote:
It's not that it's not fair, at this point it's not possible - please
make any changes you feel are required against current ASoC. The patch
has been applied for a little while now and is buried quite deep in the
already published history.
On Sun, Aug 23, 2009 at 07:45:39PM +0200, Janusz Krzysztofik wrote:
If I missed something and my original patch has really been applied, I'll be
happy to prepare a new version that reverts previos changes and makes those
proposed in patch v2, if those are acceptable.
If none of your patches
Tar Gz wrote:
hi all
i try to develop linux 2.6.26 kernel with omap patch but when i'm
booting, i'm enter busybox and running /etc/init.d/rcS
but failed to mount proc filesystem...i have enabled kernel /rpoc
filesystems support but it's still can't mounting..any idea?
You should not be
because my kernel booting and enter the busybox manually
how to enter to shell like bash?
On 8/23/09, Gary Thomas g...@mlbassoc.com wrote:
Tar Gz wrote:
hi all
i try to develop linux 2.6.26 kernel with omap patch but when i'm
booting, i'm enter busybox and running /etc/init.d/rcS
but
Sunday 23 August 2009 20:05:43 Mark Brown wrote:
If none of your patches have been applied
Mark,
I did not say that. You have applied patches 2/3 [1] and 3/3 [2] from the
series.
then what are the other
patches that depend on this? Nobody reported any issues in testing with
the other
Tar Gz wrote:
because my kernel booting and enter the busybox manually
how to enter to shell like bash?
The busybox shell is already running. It's more like 'sh' than 'bash'
What do you want to do that you don't think you can??
On 8/23/09, Gary Thomas g...@mlbassoc.com wrote:
Tar Gz
hemmm you're right...
if i want to run bash, i must declare bash shell in the /etc/inittab ?
On 8/23/09, Gary Thomas g...@mlbassoc.com wrote:
Tar Gz wrote:
because my kernel booting and enter the busybox manually
how to enter to shell like bash?
The busybox shell is already running. It's
On Sun, Aug 23, 2009 at 08:38:05PM +0200, Janusz Krzysztofik wrote:
Sunday 23 August 2009 20:05:43 Mark Brown wrote:
then what are the other
patches that depend on this? Nobody reported any issues in testing with
the other OMAP patches.
Dependency on patch 1/3 is not compile time, but
Tar Gz wrote:
hemmm you're right...
if i want to run bash, i must declare bash shell in the /etc/inittab ?
No, you'd have to build 'bash' and include it in your file system.
What's wrong with the busybox shell? What are you trying to do that it can't?
On 8/23/09, Gary Thomas
oke..i try it
i try to porting gnome / KDE to run under omap...
On 8/23/09, Gary Thomas g...@mlbassoc.com wrote:
Tar Gz wrote:
hemmm you're right...
if i want to run bash, i must declare bash shell in the /etc/inittab ?
No, you'd have to build 'bash' and include it in your file system.
Santosh Shilimkar santosh.shilim...@ti.com writes:
After the patch series [PATCH 00/14] OMAP PM fixes for .31-rc
merge in 2.6.31-rc5, the kernel crashed during boot on OMAP4430.
This patch fixes it by adding UART4 support and related code.
Without this patch omap_serial_init() would produce
Drop UART platform_data which decides which UARTs to enable during
boot. This is no longer necessary since serial core code disables
clocks after inactivity. Previously, the only reason for boards to
select UARTs was to ensure clocks are not disabled for PM reasons.
With automatic clock
updates from v1
- update 'Add PRCM register dump support' to use SoC specific
registers. Currenly only OMAP3 supported.
- drop debug observability support for now, needs some updates as pointed
out by Tony
Peter 'p2' De Schrijver (5):
OMAP: PM counter infrastructure.
OMAP: PM: Hook into
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
This patch provides the infrastructure to count how many times a
powerdomain entered a given power state (on, inactive, retention,
off). A number of functions are provided which will be called by the
chip specific powerdomain and
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
This patch modifies the clock, clockdomain and OMAP3 specific
powerdomain code to call the PM counter infrastructure whenever one or
more powerdomains might have changed state.
Signed-off-by: Peter 'p2' De Schrijver
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
Add some infrastructure to easily iterate over clock and power
domains.
Signed-off-by: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
arch/arm/mach-omap2/clockdomain.c
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
This patch provides the debugfs entries and a function which will be
called by the PM code to register the time spent per domain per
state. Also some new fields are added to the powerdomain struct to
keep the time information.
NOTE: As
From: Tero Kristo tero.kri...@nokia.com
Allows dumping out current register contents from the debug filesystem, and
also allows user to add arbitrary register save points into code. Current
register contents are available under debugfs at:
[debugfs]/pm_debug/registers/current
To add a save
From: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
Make the powerdomain code call the new hook for updating the time.
Also implement the updated pwrdm_for_each.
Signed-off-by: Peter 'p2' De Schrijver peter.de-schrij...@nokia.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
From: Tero Kristo tero.kri...@nokia.com
Target state can be read / programmed via files under:
[debugfs]/pm_debug/[pwrdm]/suspend
Signed-off-by: Tero Kristo tero.kri...@nokia.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
arch/arm/mach-omap2/pm-debug.c | 31
On Fri, Aug 21, 2009 at 04:34:33PM +0200, ext Peter Barada wrote:
On Fri, 2009-08-21 at 15:10 +0200, Kevin Hilman wrote:
Tim Bird tim.b...@am.sony.com writes:
Paul Walmsley wrote:
Hi Peter,
On Wed, 19 Aug 2009, Peter Barada wrote:
1) Does anyone have a URL of the format
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of
Shilimkar, Santosh
Sent: Sunday, August 23, 2009 8:35 AM
To: t...@atomide.com; khil...@deeprootsystems.com
Cc: linux-omap@vger.kernel.org; Shilimkar, Santosh
Subject:
After the patch series [PATCH 00/14] OMAP PM fixes for .31-rc
merge in 2.6.31-rc5, the kernel crashed during boot on OMAP4430.
This patch fixes it by adding UART4 support and related code.
Without this patch omap_serial_init() would produce NULL pointer
dereference and kernel crashes in the
On Sun, 23 Aug 2009 19:49:43 +0100
Mark Brown broo...@opensource.wolfsonmicro.com wrote:
On Sun, Aug 23, 2009 at 08:38:05PM +0200, Janusz Krzysztofik wrote:
Sunday 23 August 2009 20:05:43 Mark Brown wrote:
then what are the other
patches that depend on this? Nobody reported any issues
39 matches
Mail list logo
