On Tue, 17 Aug 2010 09:15:59 +0300
Tony Lindgren wrote:
> * Stephen Rothwell [100817 05:14]:
> > Hi all,
> >
> > Today's linux-next merge of the sound-asoc tree got a conflict in
> > arch/arm/mach-omap2/board-n8x0.c between commits
> > 1c37553eb1778802f0e7b6730df36542752e801e ("omap: n8x0: Clea
* Stephen Rothwell [100817 05:14]:
> Hi all,
>
> Today's linux-next merge of the sound-asoc tree got a conflict in
> arch/arm/mach-omap2/board-n8x0.c between commits
> 1c37553eb1778802f0e7b6730df36542752e801e ("omap: n8x0: Cleanup i2c1 and
> menelaus registration") and 69be0f6f4b8e3be992ab6a333a3
>From: Hiroshi DOYU [hiroshi.d...@nokia.com]
>Sent: Tuesday, August 17, 2010 12:27 AM
>To: Guzman Lugo, Fernando
>Cc: linux-omap@vger.kernel.org; linux-ker...@vger.kernel.org; Kanigeri, Hari
>Subject: Re: [PATCH] iommu: fix end address of vm area comparation in
>alloc_iovm_area
>
>From: "ext Guzm
* Robert Nelson [100816 17:29]:
> Due to the omap3530 ES3.0 Silicon being used on both the
> B5/B6 and C1/2/3 Beagle we can't use the cpu_is_omap34xx()
> routines to differentiate the Beagle Boards.
>
> However gpio pins 171,172,173 where setup for this prupose, so
> lets use them.
>
> Changes
Hi
On Mon, 16 Aug 2010 09:36:41 -0500
Robert Nelson wrote:
> +u8 get_omap3_beagle_rev(void)
> +{
> + return omap3_beagle_version;
> +}
> +
> +static void __init omap3_beagle_get_revision(void)
> +{
> + int ret;
> + u16 beagle_rev = 0;
> +
> + omap_mux_init_gpio(171, OMAP_PIN_INPU
Tony/Kevin,
> -Original Message-
> From: Shilimkar, Santosh
> Sent: Sunday, August 08, 2010 3:46 PM
> To: linux-omap@vger.kernel.org
> Cc: linux-arm-ker...@lists.infradead.org; Shilimkar, Santosh
> Subject: [PATCH 0/3] SRAM map series
>
> Currently we map 1 MB section while setting up SRAM
From: "ext Guzman Lugo, Fernando"
Subject: RE: [PATCH] iommu: fix end address of vm area comparation in
alloc_iovm_area
Date: Tue, 17 Aug 2010 06:48:14 +0200
> From: linux-omap-ow...@vger.kernel.org [linux-omap-ow...@vger.kernel.org] On
> Behalf Of Guzman Lugo, Fernando [fernando.l...@ti.com]
>
There was a mistake with Hiroshi email. Looping in Hiroshi
Sorry for the noise.
Regards,
Fernando.
From: linux-omap-ow...@vger.kernel.org [linux-omap-ow...@vger.kernel.org] On
Behalf Of Guzman Lugo, Fernando [fernando.l...@ti.com]
Sent: Monday, August 16
OMAP4 has an iva device and a dsp devcice where as OMAP2/3
has only an iva device. In this file the iva device in the
system is registered under the name dsp_dev and the API
to retrieve the iva device is omap2_get_dsp_device.
This patch renames the dsp_dev to iva_dev, renames
omap2_get_dsp_device t
>From cc48c0adaee97c8385a356aefa5b64a51818b4fd Mon Sep 17 00:00:00 2001
From: Fernando Guzman Lugo
Date: Mon, 16 Aug 2010 22:28:24 -0500
Subject: [PATCH] iommu: fix end address of vm area comparation in
alloc_iovm_area
End address of the vm area is “start + bytes -1”,
not “start + byte”. This pa
Hi all,
Today's linux-next merge of the sound-asoc tree got a conflict in
arch/arm/mach-omap2/board-n8x0.c between commits
1c37553eb1778802f0e7b6730df36542752e801e ("omap: n8x0: Cleanup i2c1 and
menelaus registration") and 69be0f6f4b8e3be992ab6a333a3a82e043784c52
("omap: n8x0: Register i2c2 and ad
On Tuesday, August 10, 2010, Kevin Hilman wrote:
> When using runtime PM in combination with CPUidle, the runtime PM
> transtions of some devices may be triggered during the idle path.
> Late in the idle sequence, interrupts will likely be disabled when
> runtime PM for these devices is initiated.
On Monday, August 16, 2010, Kalliguddi, Hema wrote:
> Hi,
>
> >> -Original Message-
> >> From: Kalliguddi, Hema
> >> Sent: Friday, August 13, 2010 7:08 PM
> >> To: Cousson, Benoit
> >> Cc: linux-omap@vger.kernel.org; Tony Lindgren; Kevin Hilman;
> >paul.walmsley[p...@pwsan.com]
> >> Subj
This patch unifies the definition of revision bits
that used different base(nibble) since the OMAP3630
revisions.
Summary of changes that may not seem apparent:
1) Specific ES revision definitions are derived from
the associated class and ORing of the revision bits.
2) To do so, "dummy" OMAP36
The existing definitions for cpu revision used
upper nibble in the bits[15:08]. With OMAP3630,
definitions use lower nibble.
This patch unifies the definitions to start
at lower nibble.
[1] http://marc.info/?t=12816173915&r=1&w=2
Signed-off-by: Sanjeev Premi
---
arch/arm/mach-omap2/id.c
This patch fixes miltiple section mismatch errors
observed with the latest master.
Signed-off-by: Sanjeev Premi
---
arch/arm/mach-omap2/board-2430sdp.c |2 +-
arch/arm/mach-omap2/board-apollon.c |2 +-
arch/arm/mach-omap2/board-cm-t35.c |8
arch/a
Multiple section mismatches are observed with the latest
master. While attempting to fix the ones listed below, I
came across more instances.
The patch in this series fixes all these issues.
Though most of the changes are straight-forward, but for
these (for now annotated as ___refdata):
1) arch
Hi,
>> -Original Message-
>> From: Kalliguddi, Hema
>> Sent: Friday, August 13, 2010 7:08 PM
>> To: Cousson, Benoit
>> Cc: linux-omap@vger.kernel.org; Tony Lindgren; Kevin Hilman;
>paul.walmsley[p...@pwsan.com]
>> Subject: RE: [PATCH] : Bug fix in generic runtime pm APIs
>>
>> Hi,
>>
>>>
The omap3630 based BeagleBoard xM uses a MicroSD card slot with
no write protection.
Signed-off-by: Robert Nelson
---
arch/arm/mach-omap2/board-omap3beagle.c |4 +++-
1 files changed, 3 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-omap3beagle.c
b/arch/arm/mach-omap2
Due to the omap3530 ES3.0 Silicon being used on both the
B5/B6 and C1/2/3 Beagle we can't use the cpu_is_omap34xx()
routines to differentiate the Beagle Boards.
However gpio pins 171,172,173 where setup for this prupose, so
lets use them.
Changes:
for older U-Boot's, use omap_mux_init_gpio()
ke
system_rev comes from u-boot and is a constant 0x20, so
Bx boards also fall in this 'if' and will get setup with the
wrong gpio_wp pin. Switch to using the Beagle revision routine
to correcly set pin 23 only for C1/2/3 and C4 Boards. Bx boards
will then use the correct default pin setting.
Sign
>>-Original Message-
>>From: Cousson, Benoit
>>Sent: Monday, August 16, 2010 7:23 PM
>>To: Gopinath, Thara
>>Cc: linux-omap@vger.kernel.org; khil...@deeprootsystems.com; p...@pwsan.com;
>>Sripathy, Vishwanath;
>>Sawant, Anand
>>Subject: Re: [PATCH] OMAP4: pm.c extensions for OMAP4 suppor
This patch has multiple fixes together. To ensure that git bisect work across
commits, all changes are clubbed together
1. Move the common control base address to control core
2. Remove the manually coeded defines and use the ones from headers.
3. Fix the the status register define in id.c for OMA
On OMAP4 control pad are not addressable from control
core base. So the common omap_ctrl_read/write APIs breaks
Hence export separate APIs to manage the omap4 pad control
registers.
This APIs will work only for OMAP4
Signed-off-by: Santosh Shilimkar
---
arch/arm/mach-omap2/control.c
On omap4 control module is divided in four IP blocks.
- CTRL_MODULE_CORE 0x4a002000
- CTRL_MODULE_PAD_CORE 0x4a10
- CTRL_MODULE_WKUP 0x4a30c000
- CTRL_MODULE_PAD_WKUP 0x4a31e000
Addressing all the modules with single base address is n
On omap4 control mudule is divided in four IP blocks.
CTRL_MODULE_CORE0x4a002000
PAD_CTRL_MODULE_CORE0x4a10
CTRL_MODULE_WKUP0x4a30c000
PAD_CTRL_MODULE_WKUP0x4a31e000
Addressing all the modules with single base address is not possible
consi
Hi,
On 08/16/2010 04:57 PM, Luke-Jr wrote:
> Signed-off-by: Luke Dashjr
> ---
> arch/arm/mach-omap2/board-rx51-peripherals.c |5 +
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
> b/arch/arm/mach-omap2/board-
> rx51-peri
Signed-off-by: Luke Dashjr
---
arch/arm/mach-omap2/board-rx51-peripherals.c |5 +
1 files changed, 5 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
b/arch/arm/mach-omap2/board-
rx51-peripherals.c
index 9a5eb87..2c694d4 100644
--- a/arch/arm/mach-
Hi Thara,
On 8/16/2010 11:26 AM, Thara Gopinath wrote:
OMAP4 has an iva device and a dsp devcice where as OMAP2/3
has only an iva device. In this file the iva device in the
system is registered under the name dsp_dev and the API
to retrieve the iva device is omap2_get_dsp_device.
This patch rena
Hi,
On Wed, 2010-08-11 at 12:14 +0200, ext Janorkar, Mayuresh wrote:
> Hi Tomi,
>
> Could you please provide me info on how to update the screen from user's
> space incase of manual update mode?
You can use OMAPFB_UPDATE_WINDOW ioctl.
Tomi
--
To unsubscribe from this list: send the line "un
From: Benoit Cousson
Update omap4 hwmod file with watchdog info.
This patch is extracted from the below patch sent by Benoit
OMAP4: hwmod: Add partial hwmod support for OMAP4430 ES1.0
https://patchwork.kernel.org/patch/99052/
Signed-off-by: Benoit Cousson
Signed-off-by: Charulatha V
Cc: Paul
This patch converts the OMAP Watchdog timer driver to
get adapted to HWMOD FW and to use the runtime PM APIs.
Signed-off-by: Charulatha V
Signed-off-by: Basak, Partha
---
arch/arm/plat-omap/devices.c | 64 -
drivers/watchdog/omap_wdt.c | 43 +
Add hwmod structures for Watchdog module on OMAP2430
HWMOD Databse
Signed-off-by: Charulatha V
Signed-off-by: Basak, Partha
---
arch/arm/mach-omap2/omap_hwmod_2430_data.c | 59
1 files changed, 59 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/oma
Add hwmod structures for Watchdog module on OMAP3 HWMOD database
Signed-off-by: Charulatha V
Signed-off-by: Basak, Partha
---
arch/arm/mach-omap2/omap_hwmod_3xxx_data.c | 61
arch/arm/mach-omap2/prcm-common.h |4 ++
2 files changed, 65 insertions(+),
This patch series makes OMAP2PLUS Watchdog Timer Module implemented
in HWMOD FW way. It also implements Watchdog timer driver to
use the runtime PM layer.
This patch series is created on "origin/pm-wip/hwmods-omap4".
This patch series is tested on OMAP3430 SDP and OMAP4430 SDP.
It would be of gre
Add hwmod structures for Watchdog module on OMAP2420
HWMOD database
Signed-off-by: Charulatha V
Signed-off-by: Basak, Partha
---
arch/arm/mach-omap2/omap_hwmod_2420_data.c | 59
1 files changed, 59 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/om
> -Original Message-
> From: linux-omap-ow...@vger.kernel.org
> [mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Premi, Sanjeev
> Sent: Thursday, August 12, 2010 8:21 PM
> To: Menon, Nishanth
> Cc: Gadiyar, Anand; linux-omap@vger.kernel.org
> Subject: RE: [PATCH] omap: Add macros to
On Mon, 2010-08-16 at 14:59 +0200, ext Pawel Moll wrote:
> Hi Ameya,
>
> > [0.805419] omapfb omapfb: failed to allocate framebuffer
> > [0.810882] omapfb omapfb: failed to allocate fbmem
> > [0.815856] omapfb omapfb: failed to setup omapfb
> > [0.820648] omapfb: probe of omapfb fai
Hi Ameya,
> [0.805419] omapfb omapfb: failed to allocate framebuffer
> [0.810882] omapfb omapfb: failed to allocate fbmem
> [0.815856] omapfb omapfb: failed to setup omapfb
> [0.820648] omapfb: probe of omapfb failed with error -12
Could you quickly try this hack?
diff --git a/ar
Hi Tomi,
When I tried to boot 2.6.36-rc1 kernel on Nokia N900, omapfb failed with
following error messages:
[0.124145] OMAP DSS rev 2.0
[0.124237] OMAP DISPC rev 3.0
[0.303833] acx565akm spi1.2: omapfb: acx565akm rev 8b LCD detected
[0.805419] omapfb omapfb: failed to allocate f
Hi,
>-Original Message-
>From: Sergei Shtylyov [mailto:sshtyl...@mvista.com]
>Sent: Wednesday, August 11, 2010 5:05 PM
>To: Kalliguddi, Hema
>Cc: linux-...@vger.kernel.org; linux-omap@vger.kernel.org;
>Basak, Partha; Felipe Balbi; Tony Lindgren; Kevin Hilman
>Subject: Re: [PATCH 8/8 ]us
Hi Tarun,
You series is missing the omap4 hwmod data. You should rebase it on the
latest pm_wip/hwmods-omap4 and add the hwmod data for the timers.
For further details please read this:
http://www.spinics.net/lists/linux-omap/msg34700.html
On 8/14/2010 5:38 PM, DebBarma, Tarun Kanti wrote:
> -Original Message-
> From: Shilimkar, Santosh
> Sent: Friday, August 13, 2010 11:05 PM
> To: Que, Simon; Premi, Sanjeev; Linux Omap; Tony Lindgren
> Cc: Cousson, Benoit; Kanigeri, Hari
> Subject: RE: [PATCH 1/4 v2] omap: hwspinlock: uncomment the
> hwmod part for hwspinlock
>
> Simon
>
On Saturday, August 14, 2010 08:33:09 pm Guennadi Liakhovetski wrote:
> On Fri, 13 Aug 2010, Janusz Krzysztofik wrote:
>
> > Friday 13 August 2010 11:11:52 Marin Mitov napisał(a):
> > > On Friday, August 13, 2010 11:52:41 am Guennadi Liakhovetski wrote:
> > > > On Fri, 13 Aug 2010, Janusz Krzyszto
From: "Murphy, Dan"
> Hemanth
> I have a few comments on this patch.
>
> +static ssize_t cma3000_store_attr_mdfftmr(struct device *dev,
> + struct device_attribute *attr,
> + const char *buf, size_t count)
> +{
> + struct
OMAP4 has an iva device and a dsp devcice where as OMAP2/3
has only an iva device. In this file the iva device in the
system is registered under the name dsp_dev and the API
to retrieve the iva device is omap2_get_dsp_device.
This patch renames the dsp_dev to iva_dev, renames
omap2_get_dsp_device t
On Sun, 15 Aug 2010 01:12:10 -0500
"Luke-Jr" wrote:
> Signed-off-by: Luke Dashjr
> ---
> arch/arm/mach-omap2/board-rx51-peripherals.c |3 +++
> 1 files changed, 3 insertions(+), 0 deletions(-)
>
> diff --git a/arch/arm/mach-omap2/board-rx51-peripherals.c
> b/arch/arm/mach-omap2/board-rx51
47 matches
Mail list logo
