Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects

2009-06-09 Thread Jean Pihet
On Tuesday 09 June 2009 10:14:58 tero.kri...@nokia.com wrote: -Original Message- From: ext Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: 08 June, 2009 20:24 To: Jean Pihet Cc: Paul Walmsley; Kristo Tero (Nokia-D/Tampere); linux-omap Subject: Re: [RFC][PATCH] OMAP3: add

Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-06-08 Thread Jean Pihet
Paul, Here is the updated patch that fixes the Overo build as well. Can you check it? Kevin, can you push it if it is correct? Regards, Jean From ebe57354b0de059e1f042e0c488f761853f0 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Fri, 5 Jun 2009 17:19:00 +0200 Subject

Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-06-08 Thread Jean Pihet
2001 From: Jean Pihet jpi...@mvista.com Date: Mon, 8 Jun 2009 10:49:53 +0200 Subject: OMAP3 Pandora: add support for 2 SDRAM chip selects This allows the self refresh to work correctly on Pandora. Signed-off-by: Jean Pihet jpi...@mvista.com --- arch/arm/mach-omap2/board-omap3pandora.c |8

Re: [PATCH] RX51: Add support for SDRAM chip select 1

2009-06-08 Thread Jean Pihet
Hi Tero, You should also ensure that the CKE signals mux settings are correct cf. an example for Overo at http://patchwork.kernel.org/patch/28598/. Note: the config option CONFIG_OMAP_MUX must be set for the omap_cfg* functions to have any effect. Regards, Jean On Monday 08 June 2009

Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-06-08 Thread Jean Pihet
On Monday 08 June 2009 16:59:36 Kevin Hilman wrote: Jean Pihet jpi...@mvista.com writes: Paul, Here is the updated patch that fixes the Overo build as well. Can you check it? Kevin, can you push it if it is correct? Can you run it through checkpatch, fix the errors and also merge

Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-06-08 Thread Jean Pihet
Hi Kevin, On Monday 08 June 2009 13:01:18 Grazvydas Ignotas wrote:  static void __init omap3pandora_init_irq(void)  { -       omap2_init_common_hw(mt46h32m32lf6_sdrc_params, NULL, +       omap2_init_common_hw(mt46h32m32lf6_sdrc_params, +                            

Re: Script for applying a set of patches from a folder

2009-06-05 Thread Jean Pihet
On Friday 05 June 2009 12:55:41 Elvis Dowson wrote: HI, Does anyone have a script that will allow me to apply all the patches that are contained in a folder, using the git apply command? You need to use git am for that, with the dir as parameter. git am will apply each patch from the

Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-06-05 Thread Jean Pihet
that be checked on those boards? - it is assumed that RX51 only uses 1 CS. Is that correct? Can you review it and possibly merge? Thanks regards, Jean -- From 097a640997b74638e0e7200ecd5834205204c956 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Fri, 5 Jun 2009 17:19:00 +0200

Re: [RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-06-03 Thread Jean Pihet
comments can be inlined in the reply. On Tue, 26 May 2009, Jean Pihet wrote: Here is a patch for the SDRC 2nd CS support. It applies on top of the current pm branch. Thanks for doing this work. I have some questions: - Is it OK to copy the micron sdram params file to a new file with the 2

[RFC][PATCH] OMAP3: add support for 2 SDRAM chip selects (was: Re: Beagleboard rev C memory timings suspend/resume)

2009-05-26 Thread Jean Pihet
board have 2 sdram parts? If so I need to update the board file as well. Comments are welcome. Regards, Jean From 517f52f4bef8225c5921b55ecd96eda2e0c4b697 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Tue, 26 May 2009 14:55:57 +0200 Subject: [PATCH] OMAP3: add support for 2

Re: Beagleboard rev C memory timings suspend/resume

2009-05-11 Thread Jean Pihet
Hi Paul, On Saturday 09 May 2009 00:43:43 Paul Walmsley wrote: Hello Jean, On Fri, 8 May 2009, Jean Pihet wrote: On Thursday 07 May 2009 20:59:43 Paul Walmsley wrote: On Thu, 7 May 2009, Jean Pihet wrote: From the OMAP datasheet it looks like the ARCV setting is off: shouldn't

Re: Beagleboard rev C memory timings suspend/resume

2009-05-08 Thread Jean Pihet
Paul, On Thursday 07 May 2009 20:59:43 Paul Walmsley wrote: Hello Jean On Thu, 7 May 2009, Jean Pihet wrote: From the OMAP datasheet it looks like the ARCV setting is off: shouldn't it be (tREFI/tCK)+50=(7800/6)+50=0x546? Could you elaborate further what you're seeing? It would help

Re: Beagleboard rev C memory timings suspend/resume

2009-05-08 Thread Jean Pihet
On Thursday 07 May 2009 21:18:41 Paul Walmsley wrote: Hello Jean, one other suggestion. You mentioned that you had self-refresh working on another OMAP3430 board with two SDRAM chip-selects. You might consider dumping the SDRC registers from that board, and dumping the SDRC registers on

Re: Beagleboard rev C memory timings suspend/resume

2009-05-07 Thread Jean Pihet
Hi Paul, On Thursday 07 May 2009 01:39:02 Paul Walmsley wrote: Hello Jean, sorry about the delay, Thanks for replying! On Wed, 29 Apr 2009, Jean Pihet wrote: The suspend/resume on Beagleboard has some problem due to bad memory timings. Suspending for more than 5 to 10 seconds shows

Re: Beagleboard rev C memory timings suspend/resume

2009-05-07 Thread Jean Pihet
On Thursday 07 May 2009 13:18:30 Jean Pihet wrote: Hi Paul, On Thursday 07 May 2009 01:39:02 Paul Walmsley wrote: Hello Jean, sorry about the delay, Thanks for replying! On Wed, 29 Apr 2009, Jean Pihet wrote: The suspend/resume on Beagleboard has some problem due to bad memory

Beagleboard rev C memory timings suspend/resume

2009-04-29 Thread Jean Pihet
Hi, The suspend/resume on Beagleboard has some problem due to bad memory timings. Suspending for more than 5 to 10 seconds shows memory corruption. The new chips on rev Cx boards are using 2 DDR chip selects and it looks like the 2nd memory part is not correctly put into self refresh. As an

Re: [PATCH 00/10] OMAP3: SR: Fixes in Smartreflex driver

2009-04-27 Thread Jean Pihet
Hi, On Friday 24 April 2009 15:09:29 Kevin Hilman wrote: Nayak, Rajendra rna...@ti.com writes: -Original Message- From: Kevin Hilman [mailto:khil...@deeprootsystems.com] Sent: Thursday, April 23, 2009 1:35 AM To: Nayak, Rajendra Cc: linux-omap Subject: Re: [PATCH 00/10]

2.6.29 PM and CPUIDLE

2009-04-10 Thread Jean Pihet
Hi, I am having problems using CPUIDLE PM_SLEEP on Beagleboard with the latest pm tree. It looks like CPUIDLE prevents the system to go into retention mode, while it works fine without CPUIDLE enabled: r...@beagleboard:~# echo 1 /sys/power/clocks_off_while_idle r...@beagleboard:~# echo mem

Re: [PATCH 00/02] OMAP3 clock: Remove virtual clock nodes

2009-04-07 Thread Jean Pihet
driver. Signed-off-by: Rajendra Nayak rna...@ti.com Signed-off-by: Tero Kristo tero.kri...@nokia.com Signed-off-by: Jean Pihet jpi...@mvista.com --- arch/arm/plat-omap/cpu-omap.c |8 +--- 1 files changed, 5 insertions(+), 3 deletions(-) diff --git a/arch/arm/plat-omap/cpu-omap.c b/arch

Re: PM branch rebased to 2.6.29

2009-03-26 Thread Jean Pihet
Hi, I am having a crash with the latest 2.6.29 pm branch with CPU_FREQ enabled. It looks like clk_set_rate is called recursively, thus deadlocking on the mutex. Any idea why this worked fine on 2.6.29-rc8 pm? Here is the dump excerpt: ... Disabling unused clock sys_clkout1 BUG: scheduling

Re: [PATCH] OMAP: MMC: replace infinite loops with timeouts (was Re: [PATCH] OMAP: MMC: recover from transfer failures - Resend)

2009-02-11 Thread Jean Pihet
Hi, Here is the new version of the patch, which now uses cpu_relax in an inline function. The new function can be used from an irq handler as well. Regards, Jean From 9d1993dcf4d217837437a1cd9f6e9c1b81533549 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Fri, 6 Feb 2009 16

Re: [PATCH] OMAP: MMC: recover from transfer failures - Resend

2009-02-06 Thread Jean Pihet
On Thursday 05 February 2009 21:32:03 Paul Walmsley wrote: On Thu, 5 Feb 2009, Andrew Morton wrote: On Tue, 3 Feb 2009 15:05:58 +0100 Jean Pihet jpi...@mvista.com wrote: + while (OMAP_HSMMC_READ(host-base, + SYSCTL) SRD

[PATCH] OMAP: MMC: replace infinite loops with timeouts (was Re: [PATCH] OMAP: MMC: recover from transfer failures - Resend)

2009-02-06 Thread Jean Pihet
- Resend'). Is that OK? Related, who is the maintainer of this driver? Tony? I'd like to have someone who checks patches before I queue them up. Rgds From 5ee867d09efe22a903ac7373a05e9e047bad6544 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Fri, 6 Feb 2009 16:42:51 +0100

[PATCH] OMAP: MMC: recover from transfer failures - Resend

2009-02-03 Thread Jean Pihet
d143f6b2e705aa4e9d2b032097fd1c82f8163262 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Thu, 8 Jan 2009 12:35:21 +0100 Subject: [PATCH] OMAP: MMC: recover from transfer failures Timeouts during a command that has a data phase can result in the next command issued after the command

Re: [PATCH] OMAP: MMC: recover from transfer failures

2009-02-02 Thread Jean Pihet
Tony, Has this patch been applied to the linux-omap tree? Does it need to go the patchwork? Cf. http://marc.info/?l=linux-omapm=123141577308177w=2 Regards, Jean On Thursday 08 January 2009 12:49:19 Jean Pihet wrote: Thanks for the suggestion, it works great (stress tested) and is a cleaner

Re: [PATCH] OMAP: MMC: recover from transfer failures

2009-01-08 Thread Jean Pihet
Thanks for the suggestion, it works great (stress tested) and is a cleaner fix. Here is a patch the latest linux-omap-2.6 tree. Is this OK? Regards, Jean From d143f6b2e705aa4e9d2b032097fd1c82f8163262 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Thu, 8 Jan 2009 12:35:21

[PATCH] OMAP: MMC: recover from transfer failures

2008-12-19 Thread Jean Pihet
device removal while     transferring data. Regards, Jean From 48a40925a4d57f6e7e45809a4b5c09b20f9314d7 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Tue, 16 Dec 2008 19:44:12 +0100 Subject: [PATCH] OMAP: MMC: recover from transfer failures Timeouts during a command that has

Re: [PATCH] OMAP2 OneNAND GPIO fix

2008-12-16 Thread Jean Pihet
is the patch against the hsmmc-init branch. The patch changes the include path and the request/free free omap calls to the standard version. Regards, Jean. From a4f548c3f51c9a349decc761dd539499902873f5 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Tue, 16 Dec 2008 19:22:45 +0100

[RFC/PATCH] OMAP: MMC: recover from transfer failures

2008-12-16 Thread Jean Pihet
device removal while transferring data. Regards, Jean From 48a40925a4d57f6e7e45809a4b5c09b20f9314d7 Mon Sep 17 00:00:00 2001 From: Jean Pihet jpi...@mvista.com Date: Tue, 16 Dec 2008 19:44:12 +0100 Subject: [PATCH] OMAP: MMC: recover from transfer failures Timeouts during a command that has

[PATCH] OMAP2 OneNAND GPIO fix

2008-12-11 Thread Jean Pihet
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. Regards, Jean From f95826f916cde9c0d0da79e006f090bc69112a1e Mon Sep 17 00:00:00 2001 From: Jean Pihet [EMAIL PROTECTED] Date: Thu, 11 Dec 2008 17

Re: how to force IVA2 powerdomain OFF on boot

2008-11-25 Thread Jean Pihet
Hi Kevin, In fact the IVA2 needs to execute the WFI instruction for its domain to go into idle. Fortunately the IVA2 ROM code has some provision to do it in certain cases. The trick is to reset the IVA2, configure IVA to boot in idle mode, then let it run. The attached patch might help.

<    5   6   7   8   9   10