The vaux2 (VCSI) regulator is left on by the bootloader
in rx-51. Since there the product has shipped and there
won't be any bootloader updates to fix this issue, we
need to define all the regulators and declare full
constraints for the regulator FW. This will allow the
regulator FW to disable
Adding regulator definitions to correctly shut down unneeded
regulators. Needed, but previously undefined regulators were
marked always_on.
Tested on top of MeeGo N900 DE daily release (.37 kernel) and
with linux-omap. Patch based on linux-omap HEAD.
v2: updated as per comments from Jarkko
On Mon, 2 May 2011 05:19:46 +
kalle.jokini...@nokia.com wrote:
It seems I was not answering your question quite rightly... So these are used
to power some internal blocks inside the TWL5030. The dependencies there
are not very well documented, so it's best to leave them be. I think these
On Mon, 2 May 2011 09:28:53 +0300
Kalle Jokiniemi kalle.jokini...@nokia.com wrote:
The vaux2 (VCSI) regulator is left on by the bootloader
in rx-51. Since there the product has shipped and there
won't be any bootloader updates to fix this issue, we
need to define all the regulators and
Hi,
-Original Message-
From: ext Jarkko Nikula [mailto:jhnik...@gmail.com]
Sent: 2. toukokuuta 2011 9:57
To: Jokiniemi Kalle (Nokia-SD/Tampere)
Cc: t...@atomide.com; Ailus Sakari (Nokia-SD/Helsinki); linux-
o...@vger.kernel.org; l...@slimlogic.co.uk;
Hi,
-Original Message-
From: ext Tony Lindgren [mailto:t...@atomide.com]
Sent: 29. huhtikuuta 2011 12:14
To: Jokiniemi Kalle (Nokia-SD/Tampere)
Cc: laurent.pinch...@ideasonboard.com; mche...@infradead.org; linux-
o...@vger.kernel.org; linux-me...@vger.kernel.org
Subject: Re:
The current omap3isp driver is missing regulator handling
for CSIb complex in omap34xx based devices. This patch
adds a mechanism for this to the omap3isp driver.
Signed-off-by: Kalle Jokiniemi kalle.jokini...@nokia.com
---
drivers/media/video/omap3isp/ispccp2.c | 27
The CSIb block is used in rx-51 to handle camera ccp2 IO. Adding
support to omap3isp driver for managing the power supply for the
CSIb IO complex via regulator framework. Also create the
apropriate regulator definitions in the rx-51 board file.
I propose to push this set through the linux-media,
The RX-51 uses the CSIb IO complex for camera operation. The
board file is missing definition for the regulator supplying
the CSIb complex, so this is added for better power
management.
Signed-off-by: Kalle Jokiniemi kalle.jokini...@nokia.com
---
arch/arm/mach-omap2/board-rx51-peripherals.c |
The sequence of _ocp_softreset doesn't work for i2c. The i2c module has a
special sequence to reset the module. The sequence is
- Disable the I2C.
- Write to SOFTRESET bit.
- Enable the I2C.
- Poll on the RESETDONE bit.
The sequence is implemented as a function and the i2c_class is updated
On Wed, Apr 27, 2011 at 05:02:37PM +0300, Jarkko Nikula wrote:
Recent runtime pm and hwmod conversions for 2.6.39 broke the musb peripheral
mode OMAP retention idle on boards where the board mode in struct
musb_hdrc_platform_data is set to MUSB_PERIPHERAL.
These conversions changed the way
On Fri, Apr 29, 2011 at 04:17:35PM +0300, Jarkko Nikula wrote:
If cable is not connected to peripheral only board when initializing the
gadget driver, then runtime pm calls are out-of-sync and the musb cannot
idle with omap2430.c. This was noted on Nokia N900 where musb prevented the
CPU to be
On Thu, Apr 21, 2011 at 07:52:41PM +0530, Keshava Munegowda wrote:
From: Axel Lin axel@gmail.com
In the case of missing platform_data we do not hold a spin_lock,
thus we should not call spin_unlock_irqrestore in the error path.
Also simplify the error handling by separating the
On Thu, Apr 21, 2011 at 07:52:42PM +0530, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
The gpio of EHCI phy should be 0 instead of 1;
This fixes the hub enumeration issue in beagle xm board.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
applied, thanks
On Thu, Apr 21, 2011 at 07:52:43PM +0530, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
in case of ehci phy mode; regulator of phy
should be enabled before initializing the
usbhs core driver.
Signed-off-by: Keshava Munegowda keshava_mgo...@ti.com
applied, thanks
am35x_musb_set_mode() was redefined. Fix it.
Reported-by: Sebastian Andrzej Siewior bige...@linutronix.de
Signed-off-by: Felipe Balbi ba...@ti.com
---
arch/arm/mach-omap2/board-am3517evm.c |2 +-
arch/arm/mach-omap2/omap_phy_internal.c |2 +-
arch/arm/plat-omap/include/plat/usb.h |
Hi,
On Fri, Apr 15, 2011 at 05:44:44PM +0530, ABRAHAM, KISHON VIJAY wrote:
Hi,
I tried to test ehci based in 2.6.39 rc2 + reverts commit
09173b589d547c002b6a2b560e150c4d7bb56c99.
I connected a HS device to HS-USB1 and find it's trying to enumerate the
device as FS and fails.
/ # [
Hi all,
These patches add support for two new panels to the generic-dpi-panel.
The first patch adds support for the Seiko 70WVW1TZ3 LCD panel, and the second
adds support for the Powertip PH480272T LCD panel.
Tested with an IGEP v2 board.
Please consider to add in next merge window, thanks,
Add support for Seiko 70WVW1TZ3, a LCD 7.0inch WVGA (800x480) display
type with 24-bit RGB interface and Touch-Panel, to panel-generic-dpi.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
drivers/video/omap2/displays/panel-generic-dpi.c | 25 ++
1 files
Add support for Powertip PH480242T, a LCD 4.3inch (480x242) display
type with 24-bit RGB interface, to panel-generic-dpi.
Signed-off-by: Enric Balletbo i Serra eballe...@iseebcn.com
---
drivers/video/omap2/displays/panel-generic-dpi.c | 25 ++
1 files changed, 25
Hi,
-Original Message-
From: ext Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: 29. huhtikuuta 2011 12:49
To: Jokiniemi Kalle (Nokia-SD/Tampere)
Cc: t...@atomide.com; mche...@infradead.org; linux-
o...@vger.kernel.org; linux-me...@vger.kernel.org
Subject:
On Mon, May 2, 2011 at 3:08 PM, Felipe Balbi ba...@ti.com wrote:
On Thu, Apr 21, 2011 at 07:52:42PM +0530, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
The gpio of EHCI phy should be 0 instead of 1;
This fixes the hub enumeration issue in beagle xm board.
On Mon, May 02, 2011 at 05:01:05PM +0530, Munegowda, Keshava wrote:
On Mon, May 2, 2011 at 3:08 PM, Felipe Balbi ba...@ti.com wrote:
On Thu, Apr 21, 2011 at 07:52:42PM +0530, Keshava Munegowda wrote:
From: Keshava Munegowda keshava_mgo...@ti.com
The gpio of EHCI phy should be 0 instead of
On Mon, May 2, 2011 at 5:24 PM, Felipe Balbi ba...@ti.com wrote:
On Mon, May 02, 2011 at 05:01:05PM +0530, Munegowda, Keshava wrote:
On Mon, May 2, 2011 at 3:08 PM, Felipe Balbi ba...@ti.com wrote:
On Thu, Apr 21, 2011 at 07:52:42PM +0530, Keshava Munegowda wrote:
From: Keshava Munegowda
Hi Kalle,
Thanks for the patch.
On Monday 02 May 2011 11:16:16 Kalle Jokiniemi wrote:
The current omap3isp driver is missing regulator handling
for CSIb complex in omap34xx based devices. This patch
adds a mechanism for this to the omap3isp driver.
Signed-off-by: Kalle Jokiniemi
Hi Kalle,
On Monday 02 May 2011 11:16:17 Kalle Jokiniemi wrote:
The RX-51 uses the CSIb IO complex for camera operation. The
board file is missing definition for the regulator supplying
the CSIb complex, so this is added for better power
management.
Signed-off-by: Kalle Jokiniemi
ping?
On Mon, Apr 25, 2011 at 1:09 PM, Mike Rapoport m...@compulab.co.il wrote:
Hi Tony,
These patches cleanup some of the common code in the board files. The
changes
are basically almost mechanically move the code shared among several
boards
into some common place.
There are a lot of
* Oleg Drokin gr...@linuxhacker.ru [110428 09:33]:
Hello!
On Apr 28, 2011, at 12:28 PM, Russell King - ARM Linux wrote:
mm, it looks to me like we're ending up with two layers on top of
each other, both trying to provide some kind of generic board interface.
I think they should be
* Mike Rapoport m...@compulab.co.il [110502 06:54]:
ping?
Looks OK to me, let's wait on Felipe's comments on the
musb related stuff.
Tony
--
To unsubscribe from this list: send the line unsubscribe linux-omap in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Srinath.R srin...@mistralsolutions.com
This patch fixes the EHCI PHY reset issue found on CraneBoard.
History:
https://patchwork.kernel.org/patch/740741/
Signed-off-by: Srinath.R srin...@mistralsolutions.com
---
arch/arm/mach-omap2/board-am3517crane.c |2 +-
1 files changed, 1
On Mon, May 02, 2011 at 07:20:52AM -0700, Tony Lindgren wrote:
* Oleg Drokin gr...@linuxhacker.ru [110428 09:33]:
Hello!
On Apr 28, 2011, at 12:28 PM, Russell King - ARM Linux wrote:
mm, it looks to me like we're ending up with two layers on top of
each other, both trying to provide
From: Srinath.R srin...@mistralsolutions.com
Added Display (DVI and TV) support for CraneBoard.
History:
https://patchwork.kernel.org/patch/740761/
Signed-off-by: Srinath.R srin...@mistralsolutions.com
---
arch/arm/mach-omap2/board-am3517crane.c | 73 +++
1 files
introduced by: 6629398945426f388d61392eecd76a6316a4
environment: OMAP3503, Gumstix Overo, linux-omap-2.6.39-rc5
kernel .config @ http://pastebin.com/QESCFb6j
Thank you for looking into it.
[0.205139] kobject (c04ce3a8): tried to init an initialized object,
something is seriously wrong.
[
From: Mythri P K mythr...@ti.com
A projector panel named picodlp is supported by OMAP.
panel driver is required to be added with the name picodlp_panel.
It is a WVGA panel with resolution 864 X 480 and panel timing data
is defined in the panel driver.
picodlp makes use of parallel (DPI)
The configurations and data transfer with picodlp panel happens through i2c.
An i2c client with name picodlp_i2c_driver is registered inside panel.
dpp2600 requires 4 gpio lines for interfacing it with any processor,
phy_reset, ready_reset, park, display_select
Signed-off-by: Mayuresh Janorkar
From: Mythri P K mythr...@ti.com
A new panel picodlp for OMAP4 has been introduced
picodlp is a projector available on OMAP4430SDP and EVM platforms.
Signed-off-by: Mythri P K mythr...@ti.com
Signed-off-by: Mayuresh Janorkar ma...@ti.com
---
Changes since v1: Nil
picodlp projector is supported by OMAP.
OMAP4430 SDP and EVM boards have an on board projector called as picodlp
projector.
picodlp would be connected to display sub system as a display panel.
It has a dlp processor dpp2600.
The panel would be connected using 24 bit parallel interface.
It is a
picodlp is a TI projector panel supported by OMAP
picodlp makes use of i2c interface for transferring commands to the panel
panel data is required for identifying i2c_adapter id and dlp GPIOs
A new header file has been added for panel data and
picodlp_panel_data struct has been introduced
From: Mythri P K mythr...@ti.com
picodlp_i2c_client needs to send commands over i2c as a part of initialiazation.
system controller dlp pico processor dpp2600 is used.
It configures the splash screen of picodlp using a sequence of commands.
A programmer's guide is available at:
An on-board panel named picodlp projector is available for OMAP4430 SDP.
Entry for this panel is being added in dss_devices in the board file.
It also needs 4 GPIO pins and are defined and used in board file.
picodlp also needs an i2c client over i2c controller-2 at address 0x1b.
Signed-off-by:
I've got a Gumstix Overo with linux-2.6.39-rc5 (pulled from Sakoman's tree).
Every boot I get this message. I'm not sure whether I should be
worried about it or not.
[1.996582] [ cut here ]
[2.001586] WARNING: at kernel/irq/handle.c:130
Hi,
-Original Message-
From: ext Laurent Pinchart [mailto:laurent.pinch...@ideasonboard.com]
Sent: 2. toukokuuta 2011 16:50
To: Jokiniemi Kalle (Nokia-SD/Tampere)
Cc: mauroche...@gmail.com; t...@atomide.com; linux-
o...@vger.kernel.org; linux-me...@vger.kernel.org
Subject:
Hi,
-Original Message-
From: Jokiniemi Kalle (Nokia-SD/Tampere)
--- a/arch/arm/mach-omap2/board-rx51-peripherals.c
+++ b/arch/arm/mach-omap2/board-rx51-peripherals.c
@@ -337,6 +337,13 @@ static struct omap2_hsmmc_info mmc[] __initdata
=
{
static struct
43 matches
Mail list logo
