On Wed, Jun 25, 2008 at 8:43 PM, Miguel Angel Aguilar Ulloa
[EMAIL PROTECTED] wrote:
The OMAP3 EVM has 15 keys arranged in a matrix from SW4 to SW18, but it also
has a user key (power on/off) in SW3, this key is included in the keypad
mapping. This is how mapping is done in an 4x4 array.
arun
On OMAP3430ES2, DSS has both an initiator standby CM_IDLEST bit, and a
target idle CM_IDLEST bit. This is a departure from previous silicon,
which only had an initiator standby bit.
This means we need to test the target idle bit after enabling
dss1_alwon_fclk. Previous clock code has done the
On OMAP3430ES2+, SSI has both an initiator standby CM_IDLEST bit, and a
target idle CM_IDLEST bit. This is a departure from previous silicon,
which only had an initiator standby bit.
This means that omap2_clk_wait_ready() needs to wait for the SSI
module to indicate readiness after both SSI
The test in omap2_clk_wait_ready() for DSS or CAM clocks didn't
verify that the PRCM {F,I}CLKEN1 register was in the CORE powerdomain.
Add this check in.
Signed-off-by: Paul Walmsley [EMAIL PROTECTED]
---
arch/arm/mach-omap2/clock.c | 10 +++---
1 files changed, 7 insertions(+), 3
Hi,
On Thu, 26 Jun 2008 09:55:43 +0530, Gadiyar, Anand [EMAIL PROTECTED]
wrote:
That wasn't what I said or meant. What I did want to bring out was that
having
something built-in might give it more exposure to test by someone who
wasn't
actively working on that area. And most bugs are caught
On Thursday 26 June 2008 09:03:09 Premi, Sanjeev wrote:
Hi Tom,
The tslib is contained OMAP35x package released from Texas Instruments. It is
functional.
This package is based on 2.6.22-18.
What is the kernel version you are using?
Are you may want to look to update the touchscreen
That wasn't what I said or meant. What I did want to bring out was that
having
something built-in might give it more exposure to test by someone who wasn't
actively working on that area. And most bugs are caught by people other than
the active developers.
Not really, another usecase
ext Rajendra Nayak [EMAIL PROTECTED] writes:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Jouni Hogander
Sent: Wednesday, June 25, 2008 2:44 PM
To: linux-omap@vger.kernel.org
Subject: [PATCH 6/7] 34XX: PM: Workaround for taking care of
-Original Message-
From: Högander Jouni [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 5:46 PM
To: ext Rajendra Nayak
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 6/7] 34XX: PM: Workaround for taking care
of gpio clocks
ext Rajendra Nayak [EMAIL PROTECTED]
ext Rajendra Nayak [EMAIL PROTECTED] writes:
-Original Message-
From: Högander Jouni [mailto:[EMAIL PROTECTED]
Sent: Thursday, June 26, 2008 5:46 PM
To: ext Rajendra Nayak
Cc: linux-omap@vger.kernel.org
Subject: Re: [PATCH 6/7] 34XX: PM: Workaround for taking care
of gpio
* Gadiyar, Anand [EMAIL PROTECTED] [080626 11:33]:
That wasn't what I said or meant. What I did want to bring out was that
having
something built-in might give it more exposure to test by someone who
wasn't
actively working on that area. And most bugs are caught by people other
hi all,
Resending the patch as it didn't get applied.
Searching on the archives would be painful :-p
--
- Balbi
From d8f7f708e32ad7daadf9e48e7ba0ebecdf91094c Mon Sep 17 00:00:00 2001
From: Felipe Balbi [EMAIL PROTECTED]
Date: Thu, 26 Jun 2008 16:31:44 +0300
Subject: [PATCH] ARCH: OMAP:
* Felipe Balbi [EMAIL PROTECTED] [080626 16:34]:
hi all,
Resending the patch as it didn't get applied.
Searching on the archives would be painful :-p
Thanks, one question below..
--
- Balbi
From d8f7f708e32ad7daadf9e48e7ba0ebecdf91094c Mon Sep 17 00:00:00 2001
From: Felipe
* Paul Walmsley [EMAIL PROTECTED] [080626 03:17]:
This series revises the support for automatic hardware-controlled
powerdomain context save-and-restore (SAR). Previously, this was
partially handled through the clock framework; but handling it via the
powerdomain framework is a better
On Thu, Jun 26, 2008 at 04:38:38PM +0300, Tony Lindgren wrote:
Did you mean to remove omap2_allow_sleep() instead of clk_disable()?
Crap... yeah.. sorry, attached is new patch.
--
- Balbi
From d096d1c215e4c519d77ba27035ea4c57fb793362 Mon Sep 17 00:00:00 2001
From: Felipe Balbi [EMAIL
* Paul Walmsley [EMAIL PROTECTED] [080624 10:12]:
OMAP34xx ES2 TRM Delta G to H states that the divider for DPLL1_FCLK and
DPLL2_FCLK can divide by 4 in addition to dividing by 1 and 2. Encode this
into the OMAP3 clock framework.
Pushing today.
Tony
Signed-off-by: Paul Walmsley [EMAIL
Could you please tell me what exactly you are trying to do?
I am able to open the device /dev/video0 here at my end. Please verify your
configuration file for all the required options. Here are my /dev/video nodes
on my system -
[EMAIL PROTECTED] /]# ls -l /dev/video*
crw-rw1 root
Hi,
What is the current status of the camera isp driver on OMAP3 processor?
I am using the linux-2.6.22 kernel on linux.omap.com. I am using the
camera isp driver
that exists on 0.9.8 release. I have also tried 0.9.7 release.
Has anybody tested it on ISP sensor (ISP is within the sensor)
Dear Steve,
i split the file into two pieces:
split rootfs-jffs2.img --bytes=12m
so i have two files with xaa(12Mb) and xab(11.5Mb)
i was ablt to transfer the first file completely with any problem.
but i dont know what to do next. should i transfer the first image in
RAM to flash? could you
Mohammed,
This is the correct approach. As long as you avoid anything below
0x24, you avoid touching u-boot and the kernel. I suggest to turn
protect off only for the sectors needed. The sectors/addresses depends
upon your flash. If you are using the OSK, then these are told in the
the problem was that my kernel was extending beyond to 0x24.. and
i was then writing fs from ox24. i then reflashed the kernel adn
then shifted the fs image to 0x34. but still when i do
mount -t jffs2 /dev/mntblock3 /mnt/flash
i get the same error.
cat /proc/mtd
dev size
On Thu, 26 Jun 2008, Pandita, Vikram wrote:
I hope this has fixed:
Clock usbhost_48m_fck didn't enable in 10 tries
This patch has been in the works for several days. Maybe it fixes the
problem you reported? Please let me know either way.
- Paul
Fix some bugs in the OMAP3 clock tree
22 matches
Mail list logo
