Hi Benoit,
-Original Message-
From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
Sent: Monday, February 21, 2011 7:16 PM
To: linux-omap@vger.kernel.org
Cc: ba...@ti.com; b-cous...@ti.com; r.sricha...@ti.com; Santosh Shilimkar
Subject: [PATCH 1/6] omap3: hwmod_data: Add l3 error log
Hi Benoit,
-Original Message-
From: Sricharan R [mailto:r.sricha...@ti.com]
Sent: Wednesday, February 23, 2011 11:09 AM
To: Benoit Cousson; Santosh Shilimkar
Cc: 'linux-omap@vger.kernel.org'; Felipe Balbi
Subject: RE: [PATCH 4/6] omap4: hwmod_data: Add l3 errorlog data to hwmod
database.
On Wed, Feb 23, 2011 at 12:16, Vishwanath Sripathy vishwanath...@ti.com wrote:
[...]
+int sr_notifier_control(struct voltagedomain *voltdm, bool enable)
+{
+ struct omap_sr *sr = _sr_lookup(voltdm);
+ u32 value = 0;
+ if (IS_ERR_OR_NULL(sr)) {
+ pr_warning(%s: sr
-Original Message-
From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
Sent: Monday, February 21, 2011 7:16 PM
To: linux-omap@vger.kernel.org
Cc: ba...@ti.com; b-cous...@ti.com; r.sricha...@ti.com; Santosh Shilimkar
Subject: [PATCH 1/6] omap3: hwmod_data: Add l3 error log data to
Hi Benoit,
-Original Message-
From: Sricharan R [mailto:r.sricha...@ti.com]
Sent: Wednesday, February 23, 2011 11:09 AM
To: Benoit Cousson; Santosh Shilimkar
Cc: 'linux-omap@vger.kernel.org'; Felipe Balbi
Subject: RE: [PATCH 4/6] omap4: hwmod_data: Add l3 errorlog data to hwmod
database.
Wed, Feb 23, 2011 at 12:24, Vishwanath Sripathy vishwanath...@ti.com wrote:
-Original Message-
From: Nishanth Menon [mailto:n...@ti.com]
Sent: Sunday, February 20, 2011 10:42 AM
To: Vishwanath Sripathy
Cc: linux-omap; Tony Lindgren; Kevin Hilman
Subject: Re: [PATCH 03/19] omap3+:
Currently, the core DSS platform device requests for an irq line for OMAP2 and
OMAP3. Make DISPC and DSI platform devices request for a shared IRQ line.
On OMAP3, the logical OR of DSI and DISPC interrupt lines goes to the MPU. There
is a register DSS_IRQSTATUS which tells if the interrupt came
From: Cousson, Benoit
Sent: Wednesday, February 23, 2011 4:23 AM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org; Paul Walmsley
Subject: Re: hwmod: multi-omap: disabling smartreflex on AM3517
On 2/22/2011 2:48 PM, Premi, Sanjeev wrote:
On 2/21/2011 4:41 PM, Premi, Sanjeev wrote:
[...]
The
Paul,
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Wednesday, February 23, 2011 12:42 PM
To: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Cc: Tony Lindgren; Kevin Hilman; Santosh Shilimkar; Benoīt Cousson
Subject: [PATCH 8/8] OMAP2+:
-Original Message-
From: Menon, Nishanth [mailto:n...@ti.com]
Sent: Wednesday, February 23, 2011 1:48 PM
To: Vishwanath Sripathy
Cc: linux-omap; Tony Lindgren; Kevin Hilman
Subject: Re: [PATCH 03/19] omap3+: voltage: remove initial voltage
Wed, Feb 23, 2011 at 12:24, Vishwanath
On Wed, Feb 23, 2011 at 14:29, Vishwanath Sripathy vishwanath...@ti.com wrote:
-Original Message-
From: Menon, Nishanth [mailto:n...@ti.com]
Sent: Wednesday, February 23, 2011 1:48 PM
To: Vishwanath Sripathy
Cc: linux-omap; Tony Lindgren; Kevin Hilman
Subject: Re: [PATCH 03/19]
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Paul Walmsley
Sent: Wednesday, February 23, 2011 12:42 PM
To: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Cc: Tony Lindgren; Hilman, Kevin;
On Wed, Feb 23, 2011 at 3:17 AM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 16, 2011 at 1:35 PM, David Cohen daco...@gmail.com wrote:
Add support to register an isr for IOMMU fault situations and adapt it
to allow such (*isr)() to be used as fault callback. Drivers using
On Tue, 2011-02-22 at 07:35 -0600, Janorkar, Mayuresh wrote:
When omapfb.mode is passed through bootargs, when omapfb is setting mode,
it would check if timings passed are fine for panel attached to it.
It makes use of check_timing API provided by the panel.
In current code if check_timing
Hi Paul,
-Original Message-
From: Paul Walmsley [mailto:p...@pwsan.com]
Sent: Wednesday, February 23, 2011 12:40 AM
To: Rajendra Nayak; Cousson, Benoit
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: RE: [PATCH 0/3] OMAP2+ hwmod fixes
Hi Rajendra
On
On Wed, 2011-02-23 at 02:41 -0600, Taneja, Archit wrote:
Currently, the core DSS platform device requests for an irq line for OMAP2 and
OMAP3. Make DISPC and DSI platform devices request for a shared IRQ line.
On OMAP3, the logical OR of DSI and DISPC interrupt lines goes to the MPU.
There
On Tue, Feb 22, 2011 at 1:01 PM, Peter Ujfalusi
peter.ujfal...@nokia.com wrote:
On 02/18/11 16:22, ext Kishon Vijay Abraham I wrote:
Modify OMAP McBSP driver to use omap hwmod framework and pm runtime APIs.
Created on top of linux OMAP master (linux-omap-2.6 :master)
Did digital loopback
Hi,
On Wednesday 23 February 2011 03:41 PM, Valkeinen, Tomi wrote:
On Wed, 2011-02-23 at 02:41 -0600, Taneja, Archit wrote:
Currently, the core DSS platform device requests for an irq line for OMAP2 and
OMAP3. Make DISPC and DSI platform devices request for a shared IRQ line.
On OMAP3, the
Enabling twl4030_wdt and twl4030_pwrbutton only for Triton i.e for
TWL4030 and TWL5030. This is to be excluded for Phoenix TWL6030.
Tested OMAP4 blaze, OMAP2430, OMAP3630 boot up.
Signed-off-by: Keerthy j-keer...@ti.com
Reviewed-by: Balaji T K balaj...@ti.com
---
drivers/mfd/twl-core.c |4
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Shilimkar, Santosh
Sent: Wednesday, February 23, 2011 2:23 PM
To: Paul Walmsley; linux-omap@vger.kernel.org; linux-arm-
ker...@lists.infradead.org
Cc: Tony Lindgren;
On Wed, Feb 23, 2011 at 10:20 AM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
-Original Message-
From: linux-omap-ow...@vger.kernel.org [mailto:linux-omap-
ow...@vger.kernel.org] On Behalf Of Tony Lindgren
Sent: Wednesday, February 23, 2011 12:44 AM
To: Cousson, Benoit
Cc:
The current implementation almost assumes that only
TWL4030/TWL5030/TWl6030 are (or can be) used with the
OMAP processors. This is, however, not true.
This patch removes the automatic selection of the PMIC
from Kconfig. Current defaults are chosen in default
configuration omap2plus_defconfig and
-Original Message-
From: Kishore Kadiyala [mailto:kishorek.kadiy...@gmail.com]
Sent: Wednesday, February 23, 2011 5:37 PM
To: DebBarma, Tarun Kanti
Cc: Tony Lindgren; Cousson, Benoit; Gadiyar, Anand; linux-omap
Subject: Re: Linux-next as of 20110222 broken on OMAP4
On Wed, Feb 23,
Hi Tony,
Below is an updated patch that addresses comments received from
community members over the weekend.
Please use this patch instead of the previous one.
Please notice that on the devel-board branch there are now two mux
arrays, one for omap35x and one for omap36x.
Please merge the mux
Enabling Display options to be built as modules
Also, the generic dpi, sharp nec panels are also
enabled as modules.
Signed-off-by: Samreen samr...@ti.com
---
Version5:
Incorporating the comments from Tony Lindgren, Kevin Hilman,
Paul Mundt Tomi Valkeinen to build DSS panels as
Hi all,
My OMAP37 board started choking on my USB mouse when I updated from
2.6.37 to 2.6.38rc5. I've tracked it down to commit
d199c96d41d80a567493e12b8e96ea056a1350c1, USB: prevent buggy hubs from
crashing the USB stack. If I revert this commit, my mouse works again.
Otherwise, I get the
On Wed, Feb 23, 2011 at 5:50 PM, DebBarma, Tarun Kanti
tarun.ka...@ti.com wrote:
-Original Message-
From: Kishore Kadiyala [mailto:kishorek.kadiy...@gmail.com]
Sent: Wednesday, February 23, 2011 5:37 PM
To: DebBarma, Tarun Kanti
Cc: Tony Lindgren; Cousson, Benoit; Gadiyar, Anand;
DSS submodules DPI/SDI/DSI/VENC require a regulator to function.
However, if the board doesn't use, say, SDI, the board shouldn't need to
configure vdds_sdi regulator required by the SDI module.
Currently the regulators are acquired when the DSS driver is loaded.
This means that if the kernel is
On Wed, Feb 23, 2011 at 3:45 AM, David Cohen daco...@gmail.com wrote:
On Wed, Feb 23, 2011 at 3:17 AM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 16, 2011 at 1:35 PM, David Cohen daco...@gmail.com wrote:
Add support to register an isr for IOMMU fault situations and adapt it
I will check that out Mark.
I did notice that there was discussion a while back about dummy regulators. I
think that might work -- has anyone tried this approach?
Mark Brown broo...@opensource.wolfsonmicro.com wrote:
On Tue, Feb 22, 2011 at 03:41:39PM -0500, Boswell, Patrick wrote:
The twl
On Wednesday 23 February 2011 11:59 AM, Dmitry Torokhov wrote:
On Sat, Feb 19, 2011 at 01:44:32PM +0530, Datta, Shubhrajyoti wrote:
On Sat, Feb 19, 2011 at 11:01 AM, Dmitry Torokhovdmitry.torok...@gmail.com
wrote:
Hi Shubhrajyoti,
On Sat, Feb 19, 2011 at 08:37:15AM +0530, Shubhrajyoti wrote:
Hi all,
While trying to suport TPS65023 with AM3517 processor, i realize
that much of the code has implicit assumption on usage of TWLx0y0
PMIC and Smartreflex.
Check the definition of omap_volt_pmic_info and omap_volt_data.
Just to hack support we can fill *don't care* values for the
fields
-Original Message-
From: Cousson, Benoit [mailto:b-cous...@ti.com]
Sent: Wednesday, February 23, 2011 7:50 PM
To: Paul Walmsley
Cc: Shilimkar, Santosh; linux-omap@vger.kernel.org; Tony Lindgren;
Hilman, Kevin
Subject: Re: [PATCH] omap: Move omap_hwmod_late_init() to mdesc-
On 2/23/2011 8:11 AM, Paul Walmsley wrote:
Move the code that looks for the MPU initiator hwmod to run during
the individual hwmod _register() function. (Previously, it ran after
all hwmods were registered in the omap_hwmod_late_init() function.)
This is done so code can late-initialize a few
On 2/23/2011 8:11 AM, Paul Walmsley wrote:
There's no longer any reason why we should prevent multiple
calls to omap_hwmod_init(). It is now simply used to register an
array of hwmods.
This should allow a subset of hwmods (e.g., hwmods
handling the system clocksource and clockevents) to be
On Wed, 23 Feb 2011, Alexander Holler wrote:
Am 23.02.2011 09:06, schrieb Alexander Holler:
Am 16.02.2011 02:44, schrieb Greg KH:
2.6.32-longterm review patch. If anyone has any objections, please let
us know.
This patch killed the MUSB-host-functionality here (on a BeagleBoard).
Hi Sanjeev,
On 2/23/2011 9:46 AM, Premi, Sanjeev wrote:
From: Cousson, Benoit
Sent: Wednesday, February 23, 2011 4:23 AM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org; Paul Walmsley
Subject: Re: hwmod: multi-omap: disabling smartreflex on AM3517
On 2/22/2011 2:48 PM, Premi, Sanjeev wrote:
On Sun, Feb 20, 2011 at 04:37:36PM +0530, Santosh Shilimkar wrote:
-Original Message-
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Sunday, February 20, 2011 4:34 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; khil...@ti.com; linux-arm-
-Original Message-
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Wednesday, February 23, 2011 10:07 PM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Kevin Hilman; linux-arm-
ker...@lists.infradead.org; t...@atomide.com; David Brown; Daniel
Walker;
From: Anand Gadiyar gadi...@ti.com
The MMC controller on the OMAP2420 is different from those
on the OMAP2430, OMAP3 and OMAP4 families - all of the latter
are identical. The one on the OMAP2420 is closer to that
on OMAP1 chips.
Currently, the n8x0 is the only OMAP2420 platform supported
in
On Wed, Feb 23, 2011 at 10:44 PM, Kishore Kadiyala
kishore.kadiy...@ti.com wrote:
From: Anand Gadiyar gadi...@ti.com
The MMC controller on the OMAP2420 is different from those
on the OMAP2430, OMAP3 and OMAP4 families - all of the latter
are identical. The one on the OMAP2420 is closer to
From: Anand Gadiyar gadi...@ti.com
The MMC controller on the OMAP2420 is different from those
on the OMAP2430, OMAP3 and OMAP4 families - all of the latter
are identical. The one on the OMAP2420 is closer to that
on OMAP1 chips.
Currently, the n8x0 is the only OMAP2420 platform supported
in
Adding hwmod data for hsmmc device on OMAP2430/OMAP3/OMAP4.
Adapting the omap_hsmmc driver to hwmod framework.
The patch series is based on -rc6 and tested on OMAP2430, OMAP3430SDP
OMAP4430SDP.
V3:
---
Omap2420 platform consists of mmc block as in omap1 and not the
hsmmc block as present in
Add a device attribute to hwmod data of omap2430, omap3, omap4.
Currently the device attribute holds information regarding dual volt MMC card
support by the controller which will be later passed to the host driver via
platform data.
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Changes involves:
1) Remove controller reset in devices.c which is taken care of
by hwmod framework.
2) Removing all base address macro defines except keeping one for OMAP2420.
3) Using omap-device layer to register device and utilizing data from
hwmod data file for base address, dma channel
From: Anand Gadiyar gadi...@ti.com
Enabling hsmmc hwmod for OMAP4
Signed-off-by: Anand Gadiyar gadi...@ti.com
Signed-off-by: Kishore Kadiyala kishore.kadiy...@ti.com
Cc: Benoit Cousson b-cous...@ti.com
Cc: Paul Walmsley p...@pwsan.com
CC: Kevin Hilman khil...@deeprootsystems.com
---
From: Paul Walmsley p...@pwsan.com
Update the omap3 hwmod data with the HSMMC info.
Signed-off-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Kishore Kadiyala kishore.kadiy...@ti.com
Cc: Benoit
From: Paul Walmsley p...@pwsan.com
Update the omap2430 hwmod data with the HSMMC info.
Signed-off-by: Paul Walmsley p...@pwsan.com
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Signed-off-by: Rajendra Nayak rna...@ti.com
Signed-off-by: Kishore Kadiyala kishore.kadiy...@ti.com
Cc:
-Original Message-
From: Santosh Shilimkar [mailto:santosh.shilim...@ti.com]
Sent: Wednesday, February 23, 2011 10:09 PM
To: Russell King - ARM Linux
Cc: linux-omap@vger.kernel.org; Kevin Hilman; linux-arm-
ker...@lists.infradead.org; t...@atomide.com; David Brown; Daniel
Walker;
Intent of this series is to solicit feedback on
on adding basic support for AM3517 and TPS65023.
This is definitely not the complete support, but
wanted to get early comments while i continue to
work.
Sanjeev Premi (3):
omap: voltage: Allow custom vp_init() implementation
am35xx: voltage:
This patch adds basic initialization in
the voltage layer for AM35xx processors.
In absence of AVS, functions vp_init() and
vc_init() are empty.
Signed-off-by: Sanjeev Premi pr...@ti.com
---
arch/arm/mach-omap2/voltage.c | 45 -
1 files changed, 44
Add glue logic to hook-up AM35x processors
with TPS65023.
Signed-off-by: Sanjeev Premi pr...@ti.com
---
arch/arm/mach-omap2/am3517_tps.c | 96 ++
1 files changed, 96 insertions(+), 0 deletions(-)
create mode 100644 arch/arm/mach-omap2/am3517_tps.c
diff
Current implementation expects AVS to be available
on the processor - by default. May not be true.
This patch allows the vp_init() to be implemented
per processor (or family) - same as vc_init().
Signed-off-by: Sanjeev Premi pr...@ti.com
---
arch/arm/mach-omap2/voltage.c |6 +-
1 files
On Wed, Feb 23, 2011 at 19:57, Premi, Sanjeev pr...@ti.com wrote:
Hi all,
While trying to suport TPS65023 with AM3517 processor, i realize
that much of the code has implicit assumption on usage of TWLx0y0
PMIC and Smartreflex.
Looking at the data sheet, single SCLK, SDAT makes me think that
On Wed, Feb 23, 2011 at 23:28, Sanjeev Premi pr...@ti.com wrote:
Current implementation expects AVS to be available
on the processor - by default. May not be true.
This patch allows the vp_init() to be implemented
per processor (or family) - same as vc_init().
I believe Voltage Processor !=
On Wed, Feb 23, 2011 at 23:28, Sanjeev Premi pr...@ti.com wrote:
This patch adds basic initialization in
the voltage layer for AM35xx processors.
In absence of AVS, functions vp_init() and
vc_init() are empty.
Signed-off-by: Sanjeev Premi pr...@ti.com
---
arch/arm/mach-omap2/voltage.c |
On Wed, Feb 23, 2011 at 23:28, Sanjeev Premi pr...@ti.com wrote:
Add glue logic to hook-up AM35x processors
with TPS65023.
Signed-off-by: Sanjeev Premi pr...@ti.com
[...]
+/**
+ * TBD: Just a copy of OMAP3 PMIC info.
+ * Many fields below don't make much sense for AM3517,
+ *
Hi,
Some comments and an alternative patch below.
* sricharan r.sricha...@ti.com [110127 21:05]:
--- a/arch/arm/mach-omap2/mux.c
+++ b/arch/arm/mach-omap2/mux.c
+ hmux-pads_static = kzalloc(sizeof(struct omap_device_pad) *
+ hmux-nr_pads_static, GFP_KERNEL);
* sricharan r.sricha...@ti.com [110127 21:04]:
Use the mux framework to initialise the serial pads.
Signed-off-by: sricharan r.sricha...@ti.com
---
arch/arm/mach-omap2/board-4430sdp.c | 73
++-
1 files changed, 72 insertions(+), 1 deletions(-)
diff
* sricharan r.sricha...@ti.com [110127 21:05]:
--- a/arch/arm/mach-omap2/board-omap4panda.c
+++ b/arch/arm/mach-omap2/board-omap4panda.c
@@ -370,13 +370,83 @@ static int __init omap4_panda_i2c_init(void)
omap_register_i2c_bus(4, 400, NULL, 0);
return 0;
}
-
#ifdef
* sricharan r.sricha...@ti.com [110127 21:05]:
The flag for remuxing uart3_rx_irxx pad is changed.
Signed-off-by: sricharan r.sricha...@ti.com
---
arch/arm/mach-omap2/board-n8x0.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/arch/arm/mach-omap2/board-n8x0.c
On Wed, Feb 23, 2011 at 11:28:11PM +0530, Santosh Shilimkar wrote:
Patch 6759/1 and patch 6760/1 in patch system
Was there any difference between 6760 and 6753 ?
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More
-Original Message-
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Thursday, February 24, 2011 12:33 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Kevin Hilman; linux-arm-
ker...@lists.infradead.org; t...@atomide.com; David Brown; Daniel
Walker; Bryan
Hi,
* Paul Walmsley p...@pwsan.com [110222 23:11]:
--- a/arch/arm/mach-omap2/omap_hwmod.c
+++ b/arch/arm/mach-omap2/omap_hwmod.c
+int __init omap_hwmod_late_init_one(const char *oh_name)
How about the following naming changes to avoid confusion:
omap_hwmod_init -
* Paul Walmsley p...@pwsan.com [110222 23:11]:
Hello,
This series adds the ability to late-initialize individual
hwmods. The goal here is for clockevent (and eventually
clocksource) hwmods to be late-initialized individually, and
right before they are needed, in the timer init code. Then
On Wed, Feb 23, 2011 at 3:39 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 23, 2011 at 3:45 AM, David Cohen daco...@gmail.com wrote:
On Wed, Feb 23, 2011 at 3:17 AM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 16, 2011 at 1:35 PM, David Cohen
On Thu, Feb 24, 2011 at 12:41:38AM +0530, Santosh Shilimkar wrote:
-Original Message-
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Thursday, February 24, 2011 12:33 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Kevin Hilman; linux-arm-
-Original Message-
From: Russell King - ARM Linux [mailto:li...@arm.linux.org.uk]
Sent: Thursday, February 24, 2011 1:26 AM
To: Santosh Shilimkar
Cc: linux-omap@vger.kernel.org; Kevin Hilman; linux-arm-
ker...@lists.infradead.org; t...@atomide.com; David Brown; Daniel
Walker; Bryan
On Wed, Feb 23, 2011 at 09:14:10AM -0500, Boswell, Patrick wrote:
Don't top post and please fix your mail client to word wrap within
paragraphs.
I will check that out Mark.
I did notice that there was discussion a while back about dummy
regulators. I think that might work -- has anyone tried
Guzman Lugo, Fernando wrote:
Hi,
Hi Fernando,
In OMAP4 the cortex M3 is a double core processor and as each core is
running they own version of the RTOS we threat them independently. So
our driver which controls the remote processor sees two processor but
both use the same iommu hw. When a
* Tomi Valkeinen tomi.valkei...@ti.com [110222 23:41]:
Ah, of course. I updated the branch
git://gitorious.org/linux-omap-dss2/linux.git for-tony
to be based on omap-for-linus. Minor conflicts in 3430sdp board file,
otherwise the commits are the same.
Thanks, pulled and pushed updated
On Wed, Feb 23, 2011 at 10:09 PM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
Guzman Lugo, Fernando wrote:
Hi,
Hi Fernando,
In OMAP4 the cortex M3 is a double core processor and as each core is
running they own version of the RTOS we threat them independently. So
our driver
-Original Message-
From: Menon, Nishanth
Sent: Thursday, February 24, 2011 12:06 AM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC 1/3] omap: voltage: Allow custom vp_init()
implementation
On Wed, Feb 23, 2011 at 23:28, Sanjeev Premi pr...@ti.com wrote:
David Cohen wrote:
On Wed, Feb 23, 2011 at 3:39 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 23, 2011 at 3:45 AM, David Cohen daco...@gmail.com wrote:
On Wed, Feb 23, 2011 at 3:17 AM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 16, 2011 at 1:35 PM,
On Wed, Feb 23, 2011 at 1:54 PM, David Cohen daco...@gmail.com wrote:
On Wed, Feb 23, 2011 at 3:39 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 23, 2011 at 3:45 AM, David Cohen daco...@gmail.com wrote:
On Wed, Feb 23, 2011 at 3:17 AM, Guzman Lugo, Fernando
On Wed, Feb 23, 2011 at 2:09 PM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
Guzman Lugo, Fernando wrote:
Hi,
Hi Fernando,
In OMAP4 the cortex M3 is a double core processor and as each core is
running they own version of the RTOS we threat them independently. So
our driver
* ABRAHAM, KISHON VIJAY kis...@ti.com [110223 02:11]:
Created on top of linux OMAP master (linux-omap-2.6 :master)
Does not look like that's the case. This does not seem to compile
because of .name usage in omap_hwmod_addr_space. Also contains
omap_device idle calls that we don't have merged
On Wed, Feb 23, 2011 at 2:56 PM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
David Cohen wrote:
On Wed, Feb 23, 2011 at 3:39 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 23, 2011 at 3:45 AM, David Cohen daco...@gmail.com wrote:
On Wed, Feb 23, 2011 at 3:17
* Reizer, Eyal ey...@ti.com [110223 04:22]:
Hi Tony,
Below is an updated patch that addresses comments received from
community members over the weekend.
Please use this patch instead of the previous one.
Please notice that on the devel-board branch there are now two mux
arrays, one for
* Russell King - ARM Linux li...@arm.linux.org.uk [110212 08:09]:
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
* Dmitry Torokhov dmitry.torok...@gmail.com [110218 21:29]:
Hi Shubhrajyoti,
On Sat, Feb 19, 2011 at 08:37:15AM +0530, Shubhrajyoti wrote:
Hello Dmitry,
If there are no further comments.
Can it be queued?
I normally try not to merge board code leaving it to arch owner. Can we
at
On Wed, Feb 23, 2011 at 02:58:18PM -0800, Tony Lindgren wrote:
* Dmitry Torokhov dmitry.torok...@gmail.com [110218 21:29]:
Hi Shubhrajyoti,
On Sat, Feb 19, 2011 at 08:37:15AM +0530, Shubhrajyoti wrote:
Hello Dmitry,
If there are no further comments.
Can it be queued?
I
From: Tony Lindgren [mailto:t...@atomide.com]
Sent: Wednesday, February 23, 2011 4:50 PM
Anybody from TI looking into these?
I'll poke some folks and check. I've not booted my LDP for a while.
As an older 3430 dev board its lost its shine compared to 3630 and 4430 dev
boards.
Regards,
Premi, Sanjeev wrote, on 02/24/2011 02:15 AM:
-Original Message-
From: Menon, Nishanth
Sent: Thursday, February 24, 2011 12:06 AM
To: Premi, Sanjeev
Cc: linux-omap@vger.kernel.org
Subject: Re: [RFC 1/3] omap: voltage: Allow custom vp_init()
implementation
On Wed, Feb 23, 2011 at 23:28,
Without this change a saw an 18% increase in idle power consumption
on one deivce when trace support is compiled into the kernel. Now
I see the same increase only when tracing.
Signed-off-by: Arve Hjønnevåg a...@android.com
---
arch/arm/kernel/etm.c |4 ++--
1 files changed, 2 insertions(+),
Hi,
Valkeinen, Tomi wrote:
Hi,
On Wed, 2011-02-23 at 06:22 -0600, Nilofer, Samreen wrote:
Enabling Display options to be built as modules Also, the generic dpi,
sharp nec panels are also enabled as modules.
I've just posted a patch which fixes the problem with the
regulators in DSS.
Hi,
On Sat, Feb 19, 2011 at 5:31 PM, Nishanth Menon n...@ti.com wrote:
Voltage values can get confusing in meaning with various Smartreflex
classes being active. Depending on the class used, the actual voltage
selected might be a variant. Hence pass the volt_data pointers through
the
Kishore,
On Wed, Feb 23, 2011 at 23:17, Kishore Kadiyala kishore.kadiy...@ti.com wrote:
Add a device attribute to hwmod data of omap2430, omap3, omap4.
Currently the device attribute holds information regarding dual volt MMC card
support by the controller which will be later passed to the host
On Thu, Feb 24, 2011 at 3:04 AM, Tony Lindgren t...@atomide.com wrote:
* ABRAHAM, KISHON VIJAY kis...@ti.com [110223 02:11]:
Created on top of linux OMAP master (linux-omap-2.6 :master)
Does not look like that's the case. This does not seem to compile
because of .name usage in
Kishore,
On Wed, Feb 23, 2011 at 23:17, Kishore Kadiyala kishore.kadiy...@ti.com wrote:
Changes involves:
1) Remove controller reset in devices.c which is taken care of
by hwmod framework.
2) Removing all base address macro defines except keeping one for OMAP2420.
why?
3) Using
Enabling all the display interface options to be built as module
And enabling all the display panels to be built as modules.
Signed-off-by: Samreen samr...@ti.com
---
Version6:
Enabling all the display interface options and all the display
panels.
Version5:
Incorporating the
On Wed, Feb 23, 2011 at 11:48 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb 23, 2011 at 2:56 PM, Sakari Ailus
sakari.ai...@maxwell.research.nokia.com wrote:
David Cohen wrote:
On Wed, Feb 23, 2011 at 3:39 PM, Guzman Lugo, Fernando
fernando.l...@ti.com wrote:
On Wed, Feb
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Woodruff, Richard
Sent: Thursday, February 24, 2011 4:53 AM
To: Tony Lindgren; Russell King - ARM Linux
Cc: linux-omap@vger.kernel.org; Paul Walmsley; Shilimkar, Santosh
Adds platform initialization for working with the WLAN module
attached to the omap3evm.
The patch includes MMC2 initialization, SDIO and control pins
muxing and platform device registration.
Signed-off-by: Eyal Reizer ey...@ti.com
---
arch/arm/mach-omap2/board-omap3evm.c | 74
94 matches
Mail list logo
