Hi,
>
> FWIW, as the author of much of the PM hacker in mach-omap2/serial.c, I
> agree with Tao.
>
> The only reason for the PM hackery in mach-omap2/serial.c is because
> of the limitations of the 8250 driver.
>
I have an query,
We have following functionality in serial.c:
1.) Enabling and disa
> -Original Message-
> From: Kevin Hilman [mailto:khil...@deeprootsystems.com]
> Sent: Friday, September 11, 2009 12:00 AM
> To: Premi, Sanjeev
> Cc: linux-omap@vger.kernel.org
> Subject: Re: [RFC] OMAP3 : PM : Handle variable length OPP tables
>
> "Premi, Sanjeev" writes:
>
> > Hi all
Kevin Hilman wrote:
Mike Chan writes:
Need to lock the res_mutex when traversing the res_list.
Signed-off-by: Mike Chan
Looks good, thanks.
This patch causes a hang for me when transitioning to OFF mode. This
was tested on the Android 2.6.29 tree and is 100% reproducible. The
moment
On Wed, 09 Sep 2009 15:00:03 +0300
Adrian Hunter wrote:
> >From baf6574a1b5e7c4fdc4a66d9e038efeee75ea1a0 Mon Sep 17 00:00:00 2001
> From: Adrian Hunter
> Date: Sun, 31 May 2009 19:27:36 +0300
> Subject: [PATCH] omap_hsmmc: ensure all clock enables and disables are paired
>
This patch hasn't be
> Not sure about the OMAP5912, but at least on the OMAP3430, there
> is a register (PRM_RSTST) that can logs the global reset sources.
> Reading this register after the reset should tell you the cause of
> the last reset.
>
> Maybe there is something similar in the OMAP5912.
You can look at the A
Suresh Rajashekara wrote:
>
> Is there anyway on OMAP systems (or in general in embedded systems) to
> know a way in which the processor was reset, after the reset.
>
> I am using a system based on OMAP5912 OSK and its getting reset for no
> known reason.
Not sure about the OMAP5912, but at least
Is there anyway on OMAP systems (or in general in embedded systems) to
know a way in which the processor was reset, after the reset.
I am using a system based on OMAP5912 OSK and its getting reset for no
known reason.
Thanks in advance,
Suresh
--
To unsubscribe from this list: send the line "uns
> -Original Message-
> From: Tomi Valkeinen [mailto:tomi.valkei...@nokia.com]
> Sent: Thursday, September 03, 2009 4:30 PM
> To: ext Andrew Morton
> Cc: Artem Bityutskiy; t...@atomide.com; Hiremath, Vaibhav; Syed
> Mohammed, Khasim; sako...@gmail.com; linux-ker...@vger.kernel.org;
> linux-
"Premi, Sanjeev" writes:
> Hi all,
>
> There is no generic function to translate an OPP to FREQ and vice versa.
> Came across the problem while trying to submit a follow-up to earlier
> patch for change in mpurate via bootargs.
>
> The function get_opp in resource34xx.c, but it is always called
Sanjeev Premi writes:
> When 'enable_off_mode' is 0, the target power state for MPU
> and Core is locally changed to PWRDM_POWER_RET but, the
> statistics are updated for idle state originally selected
> by the governor.
>
> This patch 'invalidates' the idle states that lead either of
> MPU or Co
Olof Johansson writes:
> On Thu, Sep 03, 2009 at 04:14:28PM +0530, Premi, Sanjeev wrote:
>> Hi,
>>
>> Currently there are multiple mechanisms for identifying the si revisions.
>>
>> Most places the comparison is against omap_rev() as a whole number. Example:
>>
>> arch/arm/mach-omap2/board-343
Hi Adrian,
>[PATCH V3 0/30] mmc and omap_hsmmc patches
What is the reason for V3? What is the difference between V2 and V3 series?
Regards,
Madhu
--
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 a
Cliff Brake writes:
> On Tue, Sep 1, 2009 at 6:34 AM, Mike Rapoport wrote:
>
>> 3) If I'm not much mistaken, board specific pin mux configuration has to deal
>> with arch/arm/plat-omap/include/mach/mux.h and arch/arm/mach-omap2/mux.c. For
>> instance, if my board uses ULPI pins that have not been
"HU TAO-TGHK48" writes:
> Resend to linux-omap
>
> -Original Message-
> From: HU TAO-TGHK48
> Sent: Monday, August 31, 2009 7:50 PM
> To: 'vimal singh'; linux-omap@vger.kernel.org; LKML;
> linux-ser...@vger.kernel.org
> Cc: Ye Yuan.Bo-A22116; Chen Xiaolong-A21785
> Subject: RE: [RFC][PAT
Currently, only GPIOs in the wakeup domain (GPIOs in bank 0) are
enabled as wakups. This patch also enables GPIOs in the PER
powerdomain (banks 2-6) to be used as possible wakeup sources.
In addition, this patch ensures that all GPIO wakeups can wakeup
the MPU using the PM_MPUGRPSEL_ registers.
I've been working with the linux-omap kernel, and after 2.6.31-rc5 I
started seeing some strange crashes. A back trace is given here:
[ 46.620941] Unable to handle kernel paging request at virtual
address 512a
[ 46.628295] pgd = c71f4000
[ 46.631042] [512a] *pgd=878a6031, *pte=00
From: "ext C.A, Subramaniam"
Subject: RE: [PATCH 10/10] omap mailbox: OMAP4 Mailbox-driver Patch to support
tasklet implementation
Date: Thu, 10 Sep 2009 13:46:53 +0200
>
>
> Hi Hiroshi,
>
> > -Original Message-
> > From: Hiroshi DOYU [mailto:hiroshi.d...@nokia.com]
> > Sent: Wednes
Hi Hiroshi,
> -Original Message-
> From: Hiroshi DOYU [mailto:hiroshi.d...@nokia.com]
> Sent: Wednesday, September 09, 2009 2:32 PM
> To: C.A, Subramaniam
> Cc: linux-omap@vger.kernel.org; t...@atomide.com;
> r...@arm.linux.org.uk; Kanigeri, Hari; Gupta, Ramesh
> Subject: Re: [PATCH 10
From: Vimal Singh
Enable NAND options by default in zoom2_defconfig file
Other changes in defconfig come from make menuconfig syncup
Signed-off-by: Vikram Pandita
Signed-off-by: Vimal Singh
---
arch/arm/configs/omap_zoom2_defconfig | 241 --
1 files changed, 1
Sorry I clicked on -send- button without $SUBJECT. Correcting this time.
-vimal
From: Vimal Singh
Adding NAND support for ZOOM2 and LDP board. I have tested it for ZOOM2 boards,
someone can verify it for LDP, hopefully it should not have any problem.
The size of the U-Boot environment partitio
From: Vimal Singh
Adding NAND support for ZOOM2 and LDP board. I have tested it for ZOOM2
boards, someone can verify it for LDP, hopefully it should not have any
problem.
The size of the U-Boot environment partition was increased to 1.25MB.
Vikram: Changed ldp name to zoom.
Future board
From: Vimal Singh
Add support for flash on SDP boards. NAND, NOR and OneNAND
are supported.
Only tested on 3430SDP (ES2 and ES3.1), somebody please test on
2430SDP and check the chips select for 2430SDP.
Also note that:
For OneNAND: in the earlier 2430SDP code the kernel partition
was set to on
This patch series adds flash support for NAND (in sdp, zoom2 and ldp),
OneNAND and NOR (in sdp)
Tested on Zoom2 by Vikram, On SDP by Vimal
OMAP: Zoom2: Enable NAND and JFFS2 in defconfig
OMAP2/3: Add support for flash on SDP boards
OMAP3: Add support for NAND on ZOOM2/LDP boards
arch/arm/
Hi Vikram,
I am going to post version-3 for these patches due to below updates/fixes:
PATCH 2/3: Add support for NAND on ZOOM2/LDP boards
1. prototype mismatch for 'unlock' funtion pointer in 'mach/nand.h and
in 'mtd_struct'
2. typo error (Singned -> Signed) indicated by Kishore.
PATCH 3/3: Zoom
Hello Sanjeev,
On Thu, 3 Sep 2009, Premi, Sanjeev wrote:
> Here, I am proposing a common mechanism to identify the si revision; that
> focuses
> on the revision bits alone. (See code below)
>
> The usage would then be (example):
>
>if (omap_rev() > OMAP3430_REV_ES1_0)
>
> To
>
>if (c
25 matches
Mail list logo
