On Wed, Nov 17, 2010 at 02:28:11PM +0200, Tomi Valkeinen wrote:
> On Tue, 2010-11-16 at 21:10 +0100, ext Tony Lindgren wrote:
> > Sure a module would be even better. My point is that the selection of
> > all the features should be enabled by default and the board options come
> > from platform_data
Hi Kishore,
On Mon, Nov 15, 2010 at 02:38:59PM +0530, kishore kadiyala wrote:
> While booting OMAP4 ES2.0 boards, cards on MMC1 and MMC2 controllers
> are not getting detected some times.
>
> During reset of command/data line, wrong pointer to base address
> was passed while read operation to SYS
On Wed, Nov 17, 2010 at 10:18 PM, Tomi Valkeinen
wrote:
> On Wed, 2010-11-17 at 21:34 +0800, ext Bryan Wu wrote:
>> There are 4 duplicated DPI panel drivers in DSS2 display driver. They are
>> similar and a generic DPI panel driver can support all them with specific
>> panel configuration. And new
Signed-off-by: Bryan Wu
---
drivers/video/omap2/displays/panel-generic-dpi.c | 10 ++
1 files changed, 10 insertions(+), 0 deletions(-)
diff --git a/drivers/video/omap2/displays/panel-generic-dpi.c
b/drivers/video/omap2/displays/panel-generic-dpi.c
index 6702cf6..07eb30e 100644
--- a/
Between 2.6.35 and 2.6.36 there have need quite a few changes in the NAND
driver, including a change from software to hardware ECC.
The new code has hardware ECC forced on by:
#define CONFIG_MTD_NAND_OMAP_HWECC
I am surprised that this was done. Surely this should have been a Kconfig
option to
On Thu, Nov 18, 2010 at 12:13 AM, Premi, Sanjeev wrote:
>> -Original Message-
>> From: linux-omap-ow...@vger.kernel.org
>> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Bryan Wu
>> Sent: Wednesday, November 17, 2010 7:05 PM
>> To: tomi.valkei...@nokia.com; linux-omap@vger.kernel.o
Hello,
There have been a few discussions over the few months about how to
properly use omap_hwmod to manage certain IPs that have the interface
clock as the functional clock (e.g. OMAP3 GPIOs.) The goal of this RFC
is to come to a conclusion about what should be done, and how to go
about implemen
Commit 72f381ba056 (omap3: Remove VMMC2 regulator on IGEP v2)
removed an unused regulator entry, but left the second MMC channel
(used by the Libertas WLAN module) without link to power regulator.
This causes the SDIO module to fail being detected.
This patch adds the two regulators that actually
* Greg KH [101117 09:21]:
> On Wed, Nov 17, 2010 at 09:28:52AM -0800, Kevin Hilman wrote:
> > Greg KH writes:
> >
> > > On Wed, Nov 17, 2010 at 10:31:52AM +0200, Emeltchenko Andrei wrote:
> > >> From: Andrei Emeltchenko
> > >>
> > >> Access to some registers depends on register access mode
> >
On Wed, Nov 10, 2010 at 11:45 AM, Tomi Valkeinen
wrote:
> Use memblock_free() and memblock_remove() to remove the allocated or
> reserved VRAM area from normal kernel memory.
>
> This is a slightly modified version of patches from Felipe Contreras and
> Namhyung Kim.
>
> Reported-by: Felipe Contre
Added APIs to get and set the mux setting via the MUX
name. In doing this the omap_mux_read and omap_mux_write can
be made static as these interfaces should be called indirectly.
Added a check in the omap_write_array to test the partition pointer
is valid prior to dereferencing.
Tested the new i
From: Jean Pihet
Add comments and IDs for the following erratas:
- i540: MPU cannot exit from Standby,
- i478: Unexpected Cold-Reset is generated when device is coming
back from OFF mode
Signed-off-by: Jean Pihet
---
arch/arm/mach-omap2/irq.c |5 -
arch/arm/mach-omap2/p
Jean Pihet writes:
> From: Jean Pihet
>
> Add comments and IDs for the following erratas:
> - i540: MPU cannot exit from Standby,
> - i478: Unexpected Cold-Reset is generated when device is coming
>back from OFF mode
>
> Signed-off-by: Jean Pihet
Nice, it's great to have the errata numbers
On Wed, Nov 17, 2010 at 09:28:52AM -0800, Kevin Hilman wrote:
> Greg KH writes:
>
> > On Wed, Nov 17, 2010 at 10:31:52AM +0200, Emeltchenko Andrei wrote:
> >> From: Andrei Emeltchenko
> >>
> >> Access to some registers depends on register access mode
> >> Three different modes are available for
Greg KH writes:
> On Wed, Nov 17, 2010 at 10:31:52AM +0200, Emeltchenko Andrei wrote:
>> From: Andrei Emeltchenko
>>
>> Access to some registers depends on register access mode
>> Three different modes are available for OMAP (at least)
>> • Operational mode LCR_REG[7] = 0x0
>> • Configurati
On 11/17/2010 5:16 PM, Kevin Hilman wrote:
"Cousson, Benoit" writes:
[...]
+#define OMAP_MPUIO_IRQ_END (IH_MPUIO_BASE + 16)
+
+/* 32 IRQs for the PRCM */
+#define OMAP_PRCM_IRQ_BASE (OMAP_MPUIO_IRQ_END)
+#define INT_34XX_PRCM_WKUP_EN (OMAP_PRCM_IRQ_BASE + 0)
On Wed, Nov 17, 2010 at 10:31:52AM +0200, Emeltchenko Andrei wrote:
> From: Andrei Emeltchenko
>
> Access to some registers depends on register access mode
> Three different modes are available for OMAP (at least)
> • Operational mode LCR_REG[7] = 0x0
> • Configuration mode A LCR_REG[7] = 0x1
"Cousson, Benoit" writes:
[...]
>> +#define OMAP_MPUIO_IRQ_END (IH_MPUIO_BASE + 16)
>> +
>> +/* 32 IRQs for the PRCM */
>> +#define OMAP_PRCM_IRQ_BASE (OMAP_MPUIO_IRQ_END)
>> +#define INT_34XX_PRCM_WKUP_EN (OMAP_PRCM_IRQ_BASE + 0)
>> +#define INT_34XX_PRCM_EVGENON_
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Bryan Wu
> Sent: Wednesday, November 17, 2010 7:05 PM
> To: tomi.valkei...@nokia.com; linux-omap@vger.kernel.org;
> linux-arm-ker...@lists.infradead.org; Gadiyar, Anand
>
From: Jean Pihet
Add comments and IDs for the following erratas:
- i540: MPU cannot exit from Standby,
- i478: Unexpected Cold-Reset is generated when device is coming
back from OFF mode
Signed-off-by: Jean Pihet
---
arch/arm/mach-omap2/irq.c |3 ++-
arch/arm/mach-omap2/pow
On Wed, 2010-11-17 at 21:34 +0800, ext Bryan Wu wrote:
> There are 4 duplicated DPI panel drivers in DSS2 display driver. They are
> similar and a generic DPI panel driver can support all them with specific
> panel configuration. And new DPI panel driver can be easily supported
> by adding panel co
On Wed, Nov 17, 2010 at 8:44 PM, Tomi Valkeinen
wrote:
> On Wed, 2010-11-17 at 10:23 +0800, ext Bryan Wu wrote:
>> Generic DPI panel driver includes the driver and 4 similar panel
>> configurations. It
>> will match the panel name which is passed from platform data and setup the
>> right configur
Still keep sharp_ls_panel driver, because it contains blacklight control driver.
Signed-off-by: Bryan Wu
---
drivers/video/omap2/displays/Kconfig | 18 --
drivers/video/omap2/displays/Makefile |3 -
drivers/video/omap2/displays/panel-generic.c | 174 --
Still keep sharp_ls_panel, since the sharp_ls_panel driver contains blacklight
control driver code which will be moved out later. Then we can use generic DPI
driver for sharp_ls_panel.
Signed-off-by: Bryan Wu
---
arch/arm/mach-omap2/board-3430sdp.c | 12 +---
arch/arm/mach-omap2/b
Generic DPI panel driver includes the driver and 4 similar panel
configurations. It
will match the panel name which is passed from platform data and setup the
right configurations.
With generic DPI panel driver, we can remove those 4 duplicated panel display
drivers. In the future, it is simple f
There are 4 duplicated DPI panel drivers in DSS2 display driver. They are
similar and a generic DPI panel driver can support all them with specific
panel configuration. And new DPI panel driver can be easily supported
by adding panel configurations into generic panel DPI driver.
This patchset intr
Hi Thomas,
On 11/17/2010 1:16 PM, Thomas Petazzoni wrote:
From: Thomas Petazzoni
[...]
static int __init omap3_pm_init(void)
That code is purely OMAP3 specific, do you think it might scale well on
OMAP4?
BTW, you should maybe change the subject with "OMAP3: prcm: ..." to
reflect that.
Hi,
Tomi Valkeinen wrote:
> Hi,
>
> Tomi Valkeinen wrote:
>> On Tue, 2010-11-16 at 12:22 +0100, ext Taneja, Archit wrote:
>>> Hi,
>>>
>>> Tomi Valkeinen wrote:
Hi,
>>>
>>> [snip]
>>>
> diff --git a/arch/arm/plat-omap/include/plat/display.h
> b/arch/arm/plat-omap/include/plat
Acked-by: Archit Taneja
bryan...@canonical.com wrote:
> There are 4 duplicated DPI panel drivers in DSS2 display
> driver. They are similar and a generic DPI panel driver can
> support all them with specific panel configuration. And new
> DPI panel driver can be easily supported by adding panel
>
On Wed, 2010-11-17 at 10:23 +0800, ext Bryan Wu wrote:
> Generic DPI panel driver includes the driver and 4 similar panel
> configurations. It
> will match the panel name which is passed from platform data and setup the
> right configurations.
>
> With generic DPI panel driver, we can remove thos
On Tue, 2010-11-16 at 21:10 +0100, ext Tony Lindgren wrote:
> * Kevin Hilman [101116 11:45]:
> > Tony Lindgren writes:
> >
> > > * Tomi Valkeinen [101116 05:41]:
> > >> On Tue, 2010-11-16 at 07:09 +0100, ext Nilofer, Samreen wrote:
> > >> > Hi,
> > >> > Any more comments on this patch?
> > >>
From: Thomas Petazzoni
Until this patch, the PRCM interrupt was handled through a normal,
single interrupt handler. However, the PRCM notifies various types of
events, which might be of interest to different drivers. In
preparation for the usage of the PRCM interrupt by those drivers, we
switch t
Tony Lindgren wrote, on 11/16/2010 03:27 PM:
* Nishanth Menon [101105 17:29]:
From: Arno Steffen
OMAP3_IVA_MASK should use OMAP3_IVA_SHIFT instead of OMAP3_SGX_SHIFT
Signed-off-by: Arno Steffen
---
Sending on behalf of Arno - he pointed at the change and everything
except for the patch ;)
Rep
Hi,
This patch was already applied months ago.
It appeared by mistake as "git format-patch" took it somehow.
Please ignore it...
- Dmitry
On 16/11/10 19:19, ext Tony Lindgren wrote:
> * Dmitry Kasatkin [101110 09:20]:
>
>> - registration with multi OMAP kernels support
>> - clocks
>>
>> Sig
- Original Message -
From: "Grant Erickson"
To: "Hemanth V"
Cc: "Tony Lindgren" ;
Sent: Tuesday, November 16, 2010 11:15 PM
Subject: Re: [PATCH] Add OMAP Support for Generic PWM Devices using
Dual-mode Timers
Boards can register such devices using platform data such as in the
fo
On Wed, Nov 17, 2010 at 2:01 PM, Emeltchenko Andrei
wrote:
> From: Andrei Emeltchenko
>
> Access to some registers depends on register access mode
> Three different modes are available for OMAP (at least)
> • Operational mode LCR_REG[7] = 0x0
> • Configuration mode A LCR_REG[7] = 0x1 and LCR_
From: Andrei Emeltchenko
Access to some registers depends on register access mode
Three different modes are available for OMAP (at least)
• Operational mode LCR_REG[7] = 0x0
• Configuration mode A LCR_REG[7] = 0x1 and LCR_REG[7:0]! = 0xBF
• Configuration mode B LCR_REG[7] = 0x1 and LCR_REG[7:
Hi,
Tomi Valkeinen wrote:
> On Tue, 2010-11-16 at 12:22 +0100, ext Taneja, Archit wrote:
>> Hi,
>>
>> Tomi Valkeinen wrote:
>>> Hi,
>>>
>>
>> [snip]
>>
diff --git a/arch/arm/plat-omap/include/plat/display.h
b/arch/arm/plat-omap/include/plat/display.h
index 586944d..3e6eec1 10064
On Tue, 16 Nov 2010 08:16:07 -0800
Kevin Hilman wrote:
> Yes, I'm not a big fan of the init function called multiple times
> either, but I really want to minimize what board files have to do.
>
> Historically, we tend to add all the init functions to every board
> file, and this is getting cumbe
39 matches
Mail list logo
