From: Vaibhav Hiremath hvaib...@ti.com
Refreshed and Cleaned up as per the latest Tomi's DSS2
code-base -
http://www.bat.org/~tomba/git/linux-omap-dss.git
Tomi,
Can you please merge this patch to your repository, so
that it will be available as part of your HEAD?
Signed-off-by: Brijesh Jadav
Hi,
I am considering using the TI TSC2007 touch screen
controller with a TI OMAP3503 processor based motherboard. This
motherboard has the TI TPS65950 power management IC onboard.
I want to interface the TI TSC2007 to a 4-wire analog resistive touch
screen panel available on a
Hi Elvis
On Mon, Dec 15, 2008 at 2:27 PM, Elvis Dowson elvis.dow...@mac.com wrote:
Hi,
I am considering using the TI TSC2007 touch screen controller with a
TI OMAP3503 processor based motherboard. This motherboard has the TI
TPS65950 power management IC onboard.
I want to interface
On Mon, Dec 15, 2008 at 02:08:16PM +0200, Jani Nikula wrote:
Add new function omap_update_gpio_switch() to support dynamically
changing the GPIO switch notify callback functions and debounce
timeouts.
Why do they need to be changed? GPIO switches related to the board schematics,
which do not
On Mon, 2008-12-15 at 15:40 +0200, ext Juha Yrjölä wrote:
On Mon, Dec 15, 2008 at 02:08:16PM +0200, Jani Nikula wrote:
Add new function omap_update_gpio_switch() to support dynamically
changing the GPIO switch notify callback functions and debounce
timeouts.
Why do they need to be
On Mon, Dec 15, 2008 at 05:44:26PM +0530, ext Trilok Soni wrote:
Hi Tony
On Mon, Dec 15, 2008 at 5:38 PM, Jani Nikula
ext-jani.1.nik...@nokia.com wrote:
Add new function omap_update_gpio_switch() to support dynamically
changing the GPIO switch notify callback functions and debounce
Hi Tony
On Mon, Dec 15, 2008 at 5:38 PM, Jani Nikula
ext-jani.1.nik...@nokia.com wrote:
Add new function omap_update_gpio_switch() to support dynamically
changing the GPIO switch notify callback functions and debounce
timeouts.
Signed-off-by: Jani Nikula ext-jani.1.nik...@nokia.com
Not
On Mon, Dec 15, 2008 at 04:52:32PM +0200, Jani Nikula wrote:
Why do they need to be changed? GPIO switches related to the board
schematics,
which do not hopefully change dynamically.
The switches themselves don't change (nor does this patch support
changing them), but different kinds
On Mon, Dec 15, 2008 at 03:44:05PM +0200, Jani Nikula wrote:
That's a nice idea, but gpio_sw_irq_handler() actually supports having 0
debounce timeouts, i.e. no settling time. Of course, I could use -1 for
don't update. However, the semantics above is exactly the same as in
On Sun, Dec 14, 2008 at 9:38 PM, shekhar, chandra x0044...@ti.com wrote:
- Original Message - From: Jason Marini jason.mar...@gmail.com
To: linux-omap@vger.kernel.org
Sent: Friday, December 12, 2008 11:51 PM
Subject: McBSP register question
Looking at the latest git head, I see that
On Mon, Dec 15, 2008 at 10:13:27AM +0530, Pillai, Manikandan wrote:
Thanks for your comments.Pls find my responses inlined.
For posting on kernel lists you probably want to fix your mail client to
insert quote characters before the mail you're replying to - it makes
your mail much easier to
On Mon, 2008-12-15 at 17:29 +0200, ext Juha Yrjölä wrote:
On Mon, Dec 15, 2008 at 04:52:32PM +0200, Jani Nikula wrote:
The switches themselves don't change (nor does this patch support
changing them), but different kinds of external devices may be connected
to the GPIO swiches. It would
Add new function omap_update_gpio_switch() to support dynamically
changing the GPIO switch notify callback functions and debounce
timeouts.
Signed-off-by: Jani Nikula ext-jani.1.nik...@nokia.com
---
arch/arm/plat-omap/gpio-switch.c | 39 +++-
On Mon, 2008-12-15 at 15:22 +0200, Felipe Balbi wrote:
Hi,
one comment below
On Mon, Dec 15, 2008 at 02:08:16PM +0200, ext Jani Nikula wrote:
+int omap_update_gpio_switch(const struct omap_gpio_switch *cfg)
+{
+ unsigned long flags;
+ struct gpio_switch *sw =
* Aguirre Rodriguez, Sergio Alberto saagui...@ti.com [081211 12:41]:
From c442f389de719b47f8ec63f0ae07b5e2c2ef7b9d Mon Sep 17 00:00:00 2001
From: Sergio Aguirre saagui...@ti.com
Date: Thu, 11 Dec 2008 13:35:49 -0600
Subject: [PATCH] OMAP: CAM: Add ISP CSI2 API
Add ISP CSI2 API for operating
* Aguirre Rodriguez, Sergio Alberto saagui...@ti.com [081211 12:44]:
From 4fa46d05b1ecb83ccf2dd1c158ecba70dafc5888 Mon Sep 17 00:00:00 2001
From: Sergio Aguirre saagui...@ti.com
Date: Thu, 11 Dec 2008 13:42:51 -0600
Subject: [PATCH] OMAP34XX: CAM: Add Sensors Support
This adds support in
Hi,
one comment below
On Mon, Dec 15, 2008 at 02:08:16PM +0200, ext Jani Nikula wrote:
+int omap_update_gpio_switch(const struct omap_gpio_switch *cfg)
+{
+ unsigned long flags;
+ struct gpio_switch *sw = find_switch(cfg-gpio, cfg-name);
+
+ if (!sw)
+ return
From: Tony Lindgren [mailto:t...@atomide.com]
* Aguirre Rodriguez, Sergio Alberto saagui...@ti.com [081211 12:44]:
+ case V4L2_POWER_OFF:
+ /* Power Down Sequence */
+#ifdef CONFIG_TWL4030_CORE
+ twl4030_i2c_write_u8(TWL4030_MODULE_PM_RECEIVER,
+
Hi,
Thanks, applied.
Tomi
On Mon, 2008-12-15 at 10:01 +0200, hvaib...@ti.com wrote:
From: Vaibhav Hiremath hvaib...@ti.com
Refreshed and Cleaned up as per the latest Tomi's DSS2
code-base -
http://www.bat.org/~tomba/git/linux-omap-dss.git
Tomi,
Can you please merge this patch to
On Mon, Dec 15, 2008 at 08:12:41AM -0800, Tony Lindgren wrote:
You should not need cpu_is_omap() macros in the drivers. Please
set up the configuration in platform_data.
Also, please pass the IORESOURCE from platform_data, and then ioremap
it in the driver. That way you can use
* Aguirre Rodriguez, Sergio Alberto saagui...@ti.com [081215 09:02]:
From: Tony Lindgren [mailto:t...@atomide.com]
* Aguirre Rodriguez, Sergio Alberto saagui...@ti.com [081211 12:44]:
+ case V4L2_POWER_OFF:
+ /* Power Down Sequence */
+#ifdef CONFIG_TWL4030_CORE
+
* David Brownell davi...@pacbell.net [081127 09:12]:
On Wednesday 26 November 2008, Kyungmin Park wrote:
Custom board powered by VAUX2 and VAUX4 for MMC instead of VMMC
Also it uses VMMC for MMC core power not voltage.
MMC1: uses VMMC1(voltage) and VMMC2(Vdd)
MMC2: uses VAUX2(voltage)
* Tero Kristo tero.kri...@nokia.com [081211 07:59]:
From: Paul Walmsley p...@pwsan.com
Add a Non-cacheable Normal ARM executable memory type,
MT_MEMORY_NONCACHED. This is needed for the OMAP3 SDRAM clock change
code, which must run from SRAM. The SRAM must be marked as
non-cacheable
* Tero Kristo tero.kri...@nokia.com [081211 07:58]:
From: Paul Walmsley p...@pwsan.com
Mark the SRAM (aka OCM RAM) as Non-cacheable Normal memory[1]. This
is to prevent the ARM from evicting existing cache lines to SDRAM
while code is executing from the SRAM. Necessary since one of the
* David Brownell davi...@pacbell.net [081201 13:55]:
These five patches go on top of the two twl4030-usb patches sent
last Wednesday.
The first four are in the USB queue (though the fourth has some
minor updates that haven't yet made it there, like speling Tony's
name right) ... the last
Tero Kristo tero.kri...@nokia.com writes:
Previously only 1 and 2 was supported. This is needed for DVFS VDD2 control.
Tero,
What is this patch against? It doesn't apply to current PM branch,
current l-o HEAD or on top of you DVFS patchset.
Kevin
Signed-off-by: Tero Kristo
From: Vikram Pandita vikram.pand...@ti.com
attr_srp is created wrongly for GADGET only mode of MUSB
The attribute is related to OTG mode only
For Gadget mode, this attribute gets created on insmod but does
not get deleted. Fixing this bug.
Signed-off-by: Vikram Pandita vikram.pand...@ti.com
---
From: Vikram Pandita vikram.pand...@ti.com
attr_srp is created wrongly for GADGET only mode of MUSB
The attribute is related to OTG mode only
For Gadget mode, this attribute gets created on insmod but does
not get deleted. Fixing the bug.
Signed-off-by: Vikram Pandita vikram.pand...@ti.com
---
On Tue, Dec 16, 2008 at 12:53:47AM +0530, Pandita, Vikram wrote:
From: Vikram Pandita vikram.pand...@ti.com
attr_srp is created wrongly for GADGET only mode of MUSB
The attribute is related to OTG mode only
For Gadget mode, this attribute gets created on insmod but does
not get deleted.
-Original Message-
From: Felipe Balbi [mailto:m...@felipebalbi.com]
On Tue, Dec 16, 2008 at 12:53:47AM +0530, Pandita, Vikram wrote:
From: Vikram Pandita vikram.pand...@ti.com
attr_srp is created wrongly for GADGET only mode of MUSB
The attribute is related to OTG mode only
For
On Mon, 15 Dec 2008, Tony Lindgren wrote:
* Tero Kristo tero.kri...@nokia.com [081211 07:59]:
From: Paul Walmsley p...@pwsan.com
Add a Non-cacheable Normal ARM executable memory type,
MT_MEMORY_NONCACHED. This is needed for the OMAP3 SDRAM clock change
code, which must run from SRAM.
Hi,
On Tue, Dec 16, 2008 at 01:25:58AM +0530, Pandita, Vikram wrote:
Agreed. In that case, we still need the following patch:
Otherwise the srp entry does not get deleted on rmmod.
makes sense, can you just update one thing:
Signed-off-by: Vikram Pandita vikram.pand...@ti.com
diff --git
DSP getProcessor state updated to cover
DSP Hibernation state
Signed-off-by: Hari Kanigeri h-kanige...@ti.com
---
drivers/dsp/bridge/rmgr/proc.c |6 +-
1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/drivers/dsp/bridge/rmgr/proc.c b/drivers/dsp/bridge/rmgr/proc.c
index
From: Vikram Pandita vikram.pand...@ti.com
srp sysfs attribute is dependent on gadget mode
the entry was not getting deleted in rmmod case,
fixing the bug
Signed-off-by: Vikram Pandita vikram.pand...@ti.com
CC: Felipe Balbi m...@felipebalbi.com
---
drivers/usb/musb/musb_core.c |4 ++--
1
On Tue, Dec 16, 2008 at 01:35:05AM +0530, Pandita, Vikram wrote:
From: Vikram Pandita vikram.pand...@ti.com
srp sysfs attribute is dependent on gadget mode
the entry was not getting deleted in rmmod case,
fixing the bug
Signed-off-by: Vikram Pandita vikram.pand...@ti.com
CC: Felipe
This patch adds a Non-cacheable Normal ARM executable memory type,
MT_MEMORY_NONCACHED.
On OMAP3, this is used for rapid dynamic voltage/frequency scaling in the
VDD2 voltage domain. OMAP3's SDRAM controller (SDRC) is in the VDD2
voltage domain, and its clock frequency must change along with
What are the chances of getting suspend (resume from) working on the N810? Are
there any patches or branches around that I can test (I'm slowly learning how
to use git)?
I'm running Debian on an N810. With the current state of power management in
linux-omap, the N810 will only run (with LCD
* green greenfreedo...@gmail.com [081215 13:08]:
What are the chances of getting suspend (resume from) working on the N810?
Are
there any patches or branches around that I can test (I'm slowly learning how
to use git)?
I'm running Debian on an N810. With the current state of power
On Sun, Dec 07, 2008 at 11:11:36AM +, Russell King - ARM Linux wrote:
On Thu, Dec 04, 2008 at 06:31:04PM -0800, Tony Lindgren wrote:
Here are few omap1 specific updates for review.
Ok.
Are these, and the other OMAP2,3 series going to be submitted sometime?
--
To unsubscribe from this
Tero Kristo tero.kri...@nokia.com writes:
This patch set provides DVFS support for OMAP3. First 16 patches contain
clock framework modifications from Paul Walmsley, which are needed for VDD2
OPP clock control to work properly. Rest of the patches are misc fixes for
DVFS control, providing
Tony Lindgren t...@atomide.com writes:
* green greenfreedo...@gmail.com [081215 13:08]:
What are the chances of getting suspend (resume from) working on the N810?
Are
there any patches or branches around that I can test (I'm slowly learning
how
to use git)?
I'm running Debian on an
* Russell King - ARM Linux li...@arm.linux.org.uk [081215 13:47]:
On Sun, Dec 07, 2008 at 11:11:36AM +, Russell King - ARM Linux wrote:
On Thu, Dec 04, 2008 at 06:31:04PM -0800, Tony Lindgren wrote:
Here are few omap1 specific updates for review.
Ok.
Are these, and the other
Tero Kristo tero.kri...@nokia.com writes:
This function is now called only once during the initialization of the device
and consequent sleep cycles will re-use the same saved contents for secure
RAM. Users who need secure services should do secure RAM saving before
entering off-mode, if a
Tero Kristo tero.kri...@nokia.com writes:
MPU and CORE should stay awake if there is CAM domain ACTIVE. This is
because that module doesn't have wake-up capability.
This should replace the patch that is currently in the PM branch.
Signed-off-by: Jouni Hogander jouni.hogan...@nokia.com
* Tony Lindgren t...@atomide.com [081207 13:45]:
Hi Pierre Russell,
This series contains a better platform init for omap MMC as discussed earlier
on the linux-omap mailing list. The last patch in the series adds support for
a newer omap MMC controller available on 2430 and 34xx omaps.
On Fri, 12 Dec 2008, Tomi Valkeinen wrote:
Enabling clock in a disabled power domain causes the power domain to be
turned on. However, the power transition is not always finished when
clk_enable() returns and this randomly crashes the kernel when an
interrupt happens right after the
* Paul Walmsley p...@pwsan.com [081215 14:37]:
On Fri, 12 Dec 2008, Tomi Valkeinen wrote:
Enabling clock in a disabled power domain causes the power domain to be
turned on. However, the power transition is not always finished when
clk_enable() returns and this randomly crashes the kernel
This patch fixes a bug where omap2_sdrc_get_params() does not properly
check for a valid table entry before continuing.
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
arch/arm/mach-omap2/sdrc.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git
On Mon, 15 Dec 2008, Kevin Hilman wrote:
This patch fixes a bug where omap2_sdrc_get_params() does not properly
check for a valid table entry before continuing.
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Acked-by: Paul Walmsley p...@pwsan.com
- Paul
--
To unsubscribe from
* Jean Pihet jpi...@mvista.com [081211 09:02]:
Hi,
Here is a patch to have the OMAP2 OneNAND driver compile on the latest tree.
I do not know if this has been addressed already, here is a patch.
Looks like I already applied similar fixes. These are queued up for
mainline too BTW.
Regards,
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
---
drivers/usb/otg/twl4030-usb.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/usb/otg/twl4030-usb.c b/drivers/usb/otg/twl4030-usb.c
index a000fb3..416e441 100644
--- a/drivers/usb/otg/twl4030-usb.c
+++
* x0052...@ti.com x0052...@ti.com [081124 14:18]:
From: Misael Lopez Cruz x0052...@ti.com
This patch initializes XCCR and RCCR registers for OMAP McBSP DAI driver for
OMAP 2430/34xx platforms. Those registers were being set to 0 as they were
not properly initialized.
This patch should be
* Kevin Hilman khil...@deeprootsystems.com [081205 23:55]:
In omap24xx_cpu_suspend assembly routine, the r2 register which holds
the address of the SDRC_POWER reg is set to zero before the value is
written back triggering a fault due to writing to address zero.
It's hard to tell where this
* Paul Walmsley p...@booyaka.com [081215 15:37]:
On Mon, 15 Dec 2008, Kevin Hilman wrote:
This patch fixes a bug where omap2_sdrc_get_params() does not properly
check for a valid table entry before continuing.
Signed-off-by: Kevin Hilman khil...@deeprootsystems.com
Acked-by: Paul
The PM branch has been consolidated and rebased against today's
linux-omap HEAD. I've also included a few patches that were posted to
the list that had fallen through the cracks.
Reminder: The branch name is 'pm'. It will continue to be called pm
and just be periodially rebased against
55 matches
Mail list logo
