On Fri, Dec 24, 2010 at 01:05:56AM -0500, Ben Gamari wrote:
> On Thu, 23 Dec 2010 20:28:19 -0700, Grant Likely
> wrote:
> > On Thu, Dec 23, 2010 at 09:27:20PM -0500, Ben Gamari wrote:
> > > I understand your concerns, but I'm not sure how to satisfy them without
> > > crippling the design's abili
Tony,
> -Original Message-
> From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
> Sent: Thursday, February 03, 2011 2:13 PM
> To: Tony Lindgren
> Cc: Anand Gadiyar; Russell King - ARM Linux; linux-arm-
> ker...@lists.infradead.org; linux-omap@vger.kernel.org; Keshava
> Munegowda; Fel
On Fri, Feb 11, 2011 at 06:52:14PM -0800, Colin Cross wrote:
> Acked-by: Colin Cross
>
> Tested on Tegra 2.
Thanks, I'll take these as Tested-by's.
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majord...@vger.kernel.org
More majordomo info a
OMAP IOMMU generic layer doesn't need ot print function name during
error messages. Print module name instead which is more useful.
Signed-off-by: David Cohen
---
arch/arm/plat-omap/iommu.c |4 ++--
1 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/plat-omap/iommu.c b/a
On Fri, Feb 4, 2011 at 11:17, Shweta Gulati wrote:
> From: Thara Gopinath
>
Gentle ping - folks after 8 days no comments, does this rev address
all previous comments? if so, it might be good to get some acks ;)
Regards,
Nishanth Menon
> Voltage control on TWL can be done using VMODE/I2C1/I2C_
Hi,
These are RFC patches. They're intended to add fault callback support so
IOMMU users can debug or react when a fault happens.
IOMMU faults might be very difficult to reproduce and then to figure out
the source of the problem. Currently IOMMU driver prints not so useful
debug message and does n
Generic IOMMU errors code are necessary to handle errors on generic
layer.
Signed-off-by: David Cohen
---
arch/arm/plat-omap/include/plat/iommu.h |7 +++
1 files changed, 7 insertions(+), 0 deletions(-)
diff --git a/arch/arm/plat-omap/include/plat/iommu.h
b/arch/arm/plat-omap/include/p
IOMMU upper layer is already printing error message. OMAP2+ specific
layer may print error message only for debug purpose.
Signed-off-by: David Cohen
---
arch/arm/mach-omap2/iommu2.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/iommu2.c b/arch/arm
Add support to register a callback for IOMMU fault situations. Drivers using
IOMMU module might want to be informed when such errors happen in order to
debug it or react.
Signed-off-by: David Cohen
---
arch/arm/mach-omap2/iommu2.c| 21 +--
arch/arm/plat-omap/include/pla
Hi all,
I am using omap 2.6.37 running overo board. I have enabled the following
option in the kernel menunconfig,
CPU Power Management --->
│ │ [*] CPU Frequency scaling
│ │ [ ] Enable CPUfreq debugging
│ │ <*> CPU frequency translation statistics
│ │ [*] CPU frequency translation statistics
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
> ow...@vger.kernel.org] On Behalf Of Mohamed Thalib H
> Sent: Saturday, February 12, 2011 4:20 PM
> To: OMAP-KML
> Subject: How to enable dvfs in omap.
>
> Hi all,
>
> I am using omap 2.6.37 running overo boa
Function declaration 'iopgtable_lookup_entry' is missing from header
file.
Signed-off-by: David Cohen
---
arch/arm/plat-omap/include/plat/iommu.h |2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/arch/arm/plat-omap/include/plat/iommu.h
b/arch/arm/plat-omap/include/plat/i
Hi Santosh,
Thanks for the help .
Regareds,
Mohamed Thalib H.
On Saturday 12 February 2011 04:27 PM, Santosh Shilimkar wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Mohamed Thalib H
Sent: Saturday, February 12,
The omap2plus_defconfig picks default NR_CPU value as 4 which isn't
correct for OMAP4430. Available CPUs are ony 2, so fix the same.
Signed-off-by: Santosh Shilimkar
---
arch/arm/configs/omap2plus_defconfig |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/arch/arm/configs
On OMAP4430 ES1.0 the local timers are gated by security. Enable the
CONFIG_LOCAL_TIMERS for omap2plus build and handle the OMAP4430 es1.0
exception case.
This patch has dependency on the first patch in this series.
ARM: smp: Select local timers vs dummy timer support runtime
Signed-off-b
The omap44xx_sram_init() implements functionality to push some
code on SRAM whenever the code can't be executed from external
memory. The low power and DVFS code can be executed from
external DDR itself thanks to OMAP4 memory controller hardware
support. So on OMAP4, sram_push kind of functionalit
The series mainly does below
- Makes ARM local timers selection runtime instead of compile time.
- Enables the LOCAL_TIMER support for OMAP4430
- Add and enable PL310 Errata for flush by Way
- Fixes the NR_CPU value in omap2plus config
- Removes the un-necess
PL310 implements the Clean & Invalidate by Way L2 cache maintenance
operation (offset 0x7FC). This operation runs in background so that
PL310 can handle normal accesses while it is in progress. Under very
rare circumstances, due to this erratum, write data can be lost when
PL310 treats a cacheable
The current code support of dummy timers in absence of local
timer is compile time. This is an attempt to convert it to runtime
so that on few SOC version if the local timers aren't supported
kernel can switch to dummy timers. OMAP4430 ES1.0 does suffer from
this limitation.
This patch should not
Mohamed Thalib H wrote, on 02/12/2011 04:42 PM:
Hi Santosh,
Thanks for the help .
Regareds,
Mohamed Thalib H.
On Saturday 12 February 2011 04:27 PM, Santosh Shilimkar wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf
On Saturday 12 February 2011 05:21 PM, Nishanth Menon wrote:
Mohamed Thalib H wrote, on 02/12/2011 04:42 PM:
Hi Santosh,
Thanks for the help .
Regareds,
Mohamed Thalib H.
On Saturday 12 February 2011 04:27 PM, Santosh Shilimkar wrote:
-Original Message-
From: linux-omap-ow...@vger.k
Another LDP3430 report...
The LDP3430 seems to be getting there, but:
1. LCD screen seems wrong. The X display looks rather large, and
flickery - looks like the LCD timing parameters are wrong. Some
text disappears off the RHS.
fbset reports:
mode "240x320-510"
On Sat, Feb 12, 2011 at 04:02:16PM +, Russell King - ARM Linux wrote:
> Another LDP3430 report...
>
> The LDP3430 seems to be getting there, but:
>
> 1. LCD screen seems wrong. The X display looks rather large, and
>flickery - looks like the LCD timing parameters are wrong. Some
>te
This series adds a mechanism for specifying a recommended bpp for
generic dss2 dpi panels and adds a panel that uses this feature.
The panel added is the 4.3 inch display that is sold with the
Devkit8000.
Daniel Morsing (2):
omap: dss2: Add recommended bpp option for generic dpi panels
omap3:
Currently, there is no way to specify a recommended bpp for a generic
dpi display. This patch adds a mechanism for doing so.
If no recommended bpp is specified by the driver, we fall back to the
default recommended bpp function
Signed-off-by: Daniel Morsing
---
drivers/video/omap2/displays/pane
This patch adds a generic panel entry for the 4.3 inch display that is
sold with the devkit8000 and modifies the board file to use this
display.
Signed-off-by: Daniel Morsing
---
Note that this patch depends on the previous one in the series.
arch/arm/mach-omap2/board-devkit8000.c |
> -Original Message-
> From: Andrei Warkentin [mailto:andr...@motorola.com]
> Sent: Saturday, February 12, 2011 11:20 PM
> To: Santosh Shilimkar
> Cc: linux-omap@vger.kernel.org; khil...@ti.com; t...@atomide.com;
> linux-arm-ker...@lists.infradead.org; Catalin Marinas
> Subject: Re: [PATCH
On Sat, Feb 12, 2011 at 5:29 AM, Santosh Shilimkar
wrote:
> PL310 implements the Clean & Invalidate by Way L2 cache maintenance
> operation (offset 0x7FC). This operation runs in background so that
> PL310 can handle normal accesses while it is in progress. Under very
> rare circumstances, due to
On Fri, 11 Feb 2011, Rajendra Nayak wrote:
> > Does that sound okay to you?
>
> Yep, that sounds better.
Here's an updated patch for the main code and the OMAP2/3 implementation.
Comments, testing welcome.
The stable integration tag with this change is
'integration-2
Here's the updated OMAP4 version.
The stable integration tag with this change is
'integration-2.6.39-20110212-002' of git://git.pwsan.com/linux-integration
- Paul
From: Rajendra Nayak
Date: Sat, 12 Feb 2011 15:32:47 -0700
Subject: [PATCH] OMAP4: clockdomain: Add wkup/s
is integrated as part of the tag
'tmp-integration-2.6.39-20110212-003' and the branch 'integration-2.6.39'
of git://git.pwsan.com/linux-integration.
- Paul
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to ma
On Sat, Feb 12, 2011 at 11:59 AM, Santosh Shilimkar
wrote:
>> -Original Message-
>> From: Andrei Warkentin [mailto:andr...@motorola.com]
>> Sent: Saturday, February 12, 2011 11:20 PM
>> To: Santosh Shilimkar
>> Cc: linux-omap@vger.kernel.org; khil...@ti.com; t...@atomide.com;
>> linux-arm-
Thanks, queued in branch 'clk_a_2.6.39' of git://git.pwsan.com/linux-2.6.
This patch is integrated as part of the tag
'tmp-integration-2.6.39-20110212-003' and the branch 'integration-2.6.39'
of git://git.pwsan.com/linux-integration.
- Paul
--
To unsubscribe from
Hi Rajendra
On Thu, 10 Feb 2011, Rajendra Nayak wrote:
> diff --git a/arch/arm/plat-omap/clock.c b/arch/arm/plat-omap/clock.c
> index fc62fb5..6889c5a 100644
> --- a/arch/arm/plat-omap/clock.c
> +++ b/arch/arm/plat-omap/clock.c
> @@ -335,6 +335,32 @@ struct clk *omap_clk_get_by_name(const char *n
On Sat, 12 Feb 2011, Paul Walmsley wrote:
> On Thu, 10 Feb 2011, Rajendra Nayak wrote:
>
> > diff --git a/arch/arm/plat-omap/clock.c b/arch/arm/plat-omap/clock.c
> > index fc62fb5..6889c5a 100644
> > --- a/arch/arm/plat-omap/clock.c
> > +++ b/arch/arm/plat-omap/clock.c
> > @@ -335,6 +335,32 @@ st
On Thu, 10 Feb 2011, Rajendra Nayak wrote:
> All OMAP3/4 dpll's support hardware level autogating.
> Populate allow_idle/deny_idle function pointers for all
> DPLL's in clkops.
>
> Signed-off-by: Rajendra Nayak
Thanks, queued for 2.6.39. Two questions though. Was the OMAP4
autogeneration scr
On Thu, 10 Feb 2011, Rajendra Nayak wrote:
> Enable all dpll autoidle for OMAP4 and OMAP3 (OMAP3
> already had dpll autoidle turned on, but was done
> using low level cm accessor apis).
> On OMAP3, replace the cm accessor apis doing this
> with the now available support for doing this in
> clock f
On Thu, 10 Feb 2011, Rajendra Nayak wrote:
> On OMAP4, the dpll post divider outputs (MX outputs)
> along with clockout_x2 output provide a way to allow/deny
> hardware level autogating.
> Allowing autoidle would mean that the hw would autogate
> this clock when there is no dependency for it.
> De
On Thu, 10 Feb 2011, Rajendra Nayak wrote:
> Enable hardware gate control for all dpll MX and X2 postdividers.
> This requires the allow_idle/deny_idle functions to be
> populated for all clock nodes (mx/x2 post dividers) in
> clkops.
>
> Signed-off-by: Rajendra Nayak
Thanks, queued for 2.6.39
r 2.6.39 in two branches of
git://git.pwsan.com/linux-2.6:
clk_a_2.6.39 (for the autoidle-independent fixes)
clk_autoidle_a_2.6.39 (for the autoidle-specific code and data changes)
Both branches have been added to the 'integration-2.6.39' branch of
git://git.pwsan.com/linux-integration, an
40 matches
Mail list logo
