SDI now makes use of vdds_sdi regulator supply.
DPI can now be disabled on systems that don't have it
changes since v1:
- Incorporated review comments
- no more omap3xx checks for regulator enable/disable in SDI
- Added Kconfig option to enable/disable DPI
Roger Quadros (3):
OMAP: DSS2: Add
From: Roger Quadros roger.quad...@nokia.com
This allows us to disable DPI on systems that do not have it
Signed-off-by: Roger Quadros roger.quad...@nokia.com
---
drivers/video/omap2/dss/Kconfig |6 ++
drivers/video/omap2/dss/Makefile |3 ++-
drivers/video/omap2/dss/core.c|
From: Roger Quadros roger.quad...@nokia.com
This patch enables the use of vdds_sdi regulator in SDI subsystem.
We can disable the vdds_sdi voltage when not in use to save
power.
Signed-off-by: Roger Quadros roger.quad...@nokia.com
---
drivers/video/omap2/dss/sdi.c | 15 +++
1
Earlier kernel contained omap sha1 and md5 driver, which was not maintained,
was not ported to new crypto APIs and removed from the source tree.
This driver implements async and sync crypto API.
It still contains pr_debug() for debugging purpose.
Will be remove for integration.
Dmitry Kasatkin
Earlier kernel contained omap sha1 and md5 driver, which was not maintained,
was not ported to new crypto APIs and removed from the source tree.
This driver implements async and sync crypto API.
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/omap-sha1-md5.c | 1449
Signed-off-by: Dmitry Kasatkin dmitry.kasat...@nokia.com
---
drivers/crypto/Kconfig |9 +
drivers/crypto/Makefile |2 ++
2 files changed, 11 insertions(+), 0 deletions(-)
diff --git a/drivers/crypto/Kconfig b/drivers/crypto/Kconfig
index b08403d..4cca798 100644
---
Hi,
On Fri, 2010-03-05 at 14:26 +0100, Syrjala Ville (Nokia-D/Helsinki)
wrote:
From: Ville Syrjälä ville.syrj...@nokia.com
Separate the memory region from the framebuffer device a little bit.
It's now possible to select the memory region used by the framebuffer
device using the new mem_idx
Tony,
http://www.pwsan.com/omap/patches/gpio/0002-OMAP-GPIO-split-omap1-and-
omap2.patch
What, make two almost identical copies of the shared code? No way!
Instead, please keep the common code under plat-omap:
arch/arm/plat-omap/gpio.c
Then implement the processor
Hi,
On Wed, 2010-03-17 at 13:35 +0100, Quadros Roger (Nokia-D/Helsinki)
wrote:
SDI now makes use of vdds_sdi regulator supply.
DPI can now be disabled on systems that don't have it
changes since v1:
- Incorporated review comments
- no more omap3xx checks for regulator enable/disable in SDI
In origin/pm-wip/hwmods branch, using omap_3430sdp_defconfig or
omap3_defconfig, results in the following error.
Anyone working on this?
drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'do'
drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before
* Varadarajan, Charulatha ch...@ti.com [100317 08:09]:
In origin/pm-wip/hwmods branch, using omap_3430sdp_defconfig or
omap3_defconfig, results in the following error.
Anyone working on this?
drivers/usb/musb/omap2430.c:261: error: expected identifier or '(' before 'do'
On Wed, Mar 17, 2010 at 03:12:50PM +0200, Dmitry Kasatkin wrote:
Earlier kernel contained omap sha1 and md5 driver, which was not maintained,
was not ported to new crypto APIs and removed from the source tree.
This driver implements async and sync crypto API.
Signed-off-by: Dmitry Kasatkin
Hi,
couple of minor comments inlined.
On Fri, Mar 05, 2010 at 02:26:19PM +0100, Syrjala Ville (Nokia-D/Helsinki)
wrote:
From: Ville Syrjälä ville.syrj...@nokia.com
Separate the memory region from the framebuffer device a little bit.
It's now possible to select the memory region used by the
Tony Lindgren t...@atomide.com writes:
* Varadarajan, Charulatha ch...@ti.com [100317 08:09]:
In origin/pm-wip/hwmods branch, using omap_3430sdp_defconfig or
omap3_defconfig, results in the following error.
Anyone working on this?
drivers/usb/musb/omap2430.c:261: error: expected
Hi all,
Here's an updated version of this patch with more details.
Looks like VFPv3 is only available on V7:
http://www.arm.com/products/processors/technologies/vector-floating-point.php
HAS_TLS reg is only on ARM11 starting with r1p0:
Vishwanath BS vishwanath...@ti.com writes:
From: Shweta Gulati shweta.gul...@ti.com
DSP usage at VDD1 OPP1 and OPP2 with Smartreflex enabled and any MM UCs
running DSP codec was earlier restricted as DSP crashed.
The root cause is wrong DPLL1/DPLL2 Bypass clock at VDD1 OPP1 and OPP2.
The
On Wed, 2010-03-17 at 17:57 +, Tony Lindgren wrote:
Here's an updated version of this patch with more details.
Looks like VFPv3 is only available on V7:
http://www.arm.com/products/processors/technologies/vector-floating-point.php
But does it cause any problem if the feature is enabled
* Catalin Marinas catalin.mari...@arm.com [100317 11:04]:
On Wed, 2010-03-17 at 17:57 +, Tony Lindgren wrote:
Here's an updated version of this patch with more details.
Looks like VFPv3 is only available on V7:
From: Francisco Alecrim francisco.alec...@openbossa.org
arch/arm/configs/n8x0_defconfig:1061:warning: override: reassigning to
symbol NILFS2_FS
Signed-off-by: Francisco Alecrim francisco.alec...@openbossa.org
---
arch/arm/configs/n8x0_defconfig |1 -
1 files changed, 0 insertions(+), 1
On Wed, Mar 17, 2010 at 06:34:07PM +0100, Deak Imre (Nokia-D/Helsinki) wrote:
Hi,
couple of minor comments inlined.
On Fri, Mar 05, 2010 at 02:26:19PM +0100, Syrjala Ville (Nokia-D/Helsinki)
wrote:
From: Ville Syrjälä ville.syrj...@nokia.com
Separate the memory region from the
* Felipe Balbi m...@felipebalbi.com [100317 10:04]:
On Wed, Mar 17, 2010 at 03:12:50PM +0200, Dmitry Kasatkin wrote:
Earlier kernel contained omap sha1 and md5 driver, which was not maintained,
was not ported to new crypto APIs and removed from the source tree.
+#include linux/version.h
Guys:
I have a Beagleboard-like unit here that uses two SMSC USB3320C-EZK
PHYs: one for EHCI (usb1), the other for OTG (usb0).
Two questions. First, the code in drivers/usb/otg/ulpi.c looks like it
might be what I need (my attempts so far with the nop transceiver have
ended in failure). Am I
Add new function omap_device_has_lost_context() as a simple check
to be used after omap_device_enable() to determine if device has
lost context (and thus needs context restore.)
Motivation: Currently, each driver needs to read the context-loss
count before suspend, and again upon resume to
Following patch series add initial support for TWL6040 codec driver.
The patch set is based on the series sent from Misael Lopez in October 2009.
Changes from v5:
- Add CONFIG_PM for twl6040_suspend and twl6030_resume functions
- Add description for patch 1
Regards,
Margarita
---
Misael Lopez
Correction for chips:
twl6030 is Phoenix Power chip
twl6040 is Phoenix Audio chip
Signed-off-by: Margarita Olaya Cabrera magi.ol...@ti.com
---
drivers/mfd/twl-core.c |4 ++--
include/linux/i2c/twl.h |6 +++---
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git
From: Misael Lopez Cruz x0052...@ti.com
Initial version of TWL6040 codec driver.
The TWL6040 codec uses a proprietary PDM-based digital audio interface.
Audio paths supported are:
- Input: Main Mic, Sub Mic, Headset Mic, Auxiliary-FM Left/Right
- Output: Headset Left/Right, Handsfree Left/Right
From: Ville Syrjälä ville.syrj...@nokia.com
Split the overlay address calculations into their own function.
Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com
---
drivers/video/omap2/omapfb/omapfb-main.c | 63 ++
1 files changed, 38 insertions(+), 25 deletions(-)
From: Ville Syrjälä ville.syrj...@nokia.com
In omapfb_enable_overlay() if the overlay state is already what we want
skip the set_overlay_info().
Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com
---
drivers/video/omap2/omapfb/omapfb.h |2 ++
1 files changed, 2 insertions(+), 0
This patchset is based on the v3 monolithic patch.
These are the changes from v3:
* split up into smaller chunks
* OMAPFB_MEM_IDX defines fixed to use the full byte
* unnecessary changes removed
* converted to use rwsems
* further modified further to make lockdep happy
* some debug WARN_ON()s
From: Ville Syrjälä ville.syrj...@nokia.com
If video memory hasn't been allocate have check_fb_var() still check
most of the settings, just skip the ones involving the size of the
memory region. Also skip the memory address calculations in
omapfb_setup_overlay() if there's no memory.
From: Ville Syrjälä ville.syrj...@nokia.com
Add locking to the memory regions to make sure the memory region size
won't be changed while some other piece of code is performing some
checks or setup based on that information.
Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com
---
From: Ville Syrjälä ville.syrj...@nokia.com
Separate the memory region from the framebuffer device a little bit.
It's now possible to select the memory region used by the framebuffer
device using the new mem_idx parameter of omapfb_plane_info. If the
mem_idx is specified it will be interpreted as
From: Ville Syrjälä ville.syrj...@nokia.com
When more than one memory region needs to be lockd at the same time use
the memory region id to fix the order in which the locks are taken. Also
one needs to use the _nested() versions of the locking primitives. The
memory region id can serve as the
From: Ville Syrjälä ville.syrj...@nokia.com
R/W semaphore is a goof fit for the memory region locking pattern.
So use it.
Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com
---
drivers/video/omap2/omapfb/omapfb-ioctl.c | 10 ++
drivers/video/omap2/omapfb/omapfb-main.c |2 +-
From: Ville Syrjälä ville.syrj...@nokia.com
Trigger WARN_ON() messages from various places in the code in case the
memory region is not currently locked.
Signed-off-by: Ville Syrjälä ville.syrj...@nokia.com
---
drivers/video/omap2/omapfb/omapfb-ioctl.c |2 ++
* Varadarajan, Charulatha ch...@ti.com [100317 07:07]:
Tony,
http://www.pwsan.com/omap/patches/gpio/0002-OMAP-GPIO-split-omap1-and-
omap2.patch
What, make two almost identical copies of the shared code? No way!
Instead, please keep the common code under plat-omap:
-Original Message-
From: linux-omap-ow...@vger.kernel.org
[mailto:linux-omap-ow...@vger.kernel.org] On Behalf Of Bill Gatliff
Sent: Thursday, March 18, 2010 3:05 AM
To: linux-omap@vger.kernel.org
Subject: Question on OTG transceivers
Guys:
I have a Beagleboard-like unit
The patch has the changes to calculate the dpll3 clock stabilization delay
dynamically. The SRAM delay is calibrated during bootup using the gptimers
and used while calculating the stabilization delay. By using the dynamic
method the dependency on the type of cache being used is removed.
To
From: Teerth Reddy tee...@ti.com
The patch has the changes to calculate the dpll3 clock stabilization
delay dynamically. The SRAM delay is calibrated during bootup using the
gptimers and used while calculating the stabilization delay. By using
the dynamic method the dependency on the type of
This patch uses new formula to derive the dpll3 clock Stabilization
delay during DVFS for OMAP3630. The formula used is :
Latency = 2 * SYS_CLK + 10 * CLKOUTX2
1usec buffer time is added for safety.
Signed-off-by: Vishwanath Sripathy vishwanath...@ti.com
Signed-off-by: Pramod Gurav
Hi All,
Dspbridge branch will be rebased to 2.6.33 kernel in the next couple of days,
along with it, mailbox migration patches will be pushed and a few omap mailbox
fixes will be cherry picked on top.
Thanks,
Omar
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the
From: Richard Woodruff r-woodru...@ti.com
This patch adds argument to smc calls as gcc-4.4.1 requires it
otherwise the build breaks with 2009-q3 toolchanin.
arch/arm/mach-omap2/omap-headsmp.S: Assembler messages:
arch/arm/mach-omap2/omap-headsmp.S:36: Error: missing expression -- `smc'
42 matches
Mail list logo
