From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 0/4] OMAP-GPMC generic timing migration
Date: Mon, 8 Oct 2012 20:01:27 -0700 [thread overview]
Message-ID: <20121009030126.GB12552@atomide.com> (raw)
In-Reply-To: <cover.1349450723.git.afzal@ti.com>
* Afzal Mohammed <afzal@ti•com> [121005 09:02]:
>
> Proposed generic routine has been tested on OneNAND (async) on
> OMAP3EVM rev C (as mainline does not have the OneNAND support for this,
> local patch were used to test). For other cases of custom timing
> calculation (tusb6010, smc91x non-muxed, OneNAND sync), generic timing
> calculation routine was verified by simulating on OMAP3EVM.
Have you tested to make sure this works if you change the
L3 frequency?
That should probably be tested as a sanity check. Maybe you
can force the L3 for some test boots for this, I don't think
we scale it by default.
Regards,
Tony
next prev parent reply other threads:[~2012-10-09 3:01 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-05 16:00 [PATCH 0/4] OMAP-GPMC generic timing migration Afzal Mohammed
2012-10-05 16:01 ` [PATCH 1/4] ARM: OMAP2+: gpmc: generic timing calculation Afzal Mohammed
2012-10-05 16:01 ` [PATCH 2/4] ARM: OMAP2+: onenand: " Afzal Mohammed
2012-10-05 16:01 ` [PATCH 3/4] ARM: OMAP2+: smc91x: " Afzal Mohammed
2012-10-05 16:01 ` [PATCH 4/4] ARM: OMAP2+: tusb6010: " Afzal Mohammed
2012-10-09 3:01 ` Tony Lindgren [this message]
2012-10-09 12:59 ` [PATCH 0/4] OMAP-GPMC generic timing migration Afzal Mohammed
2012-10-11 11:45 ` Daniel Mack
2012-10-11 12:47 ` Mohammed, Afzal
2012-10-11 14:47 ` Tony Lindgren
2012-10-15 12:41 ` Mohammed, Afzal
2012-10-15 16:01 ` Tony Lindgren
2012-10-16 6:56 ` Afzal Mohammed
2012-10-17 5:42 ` Afzal Mohammed
2012-10-17 15:13 ` Daniel Mack
2012-10-17 15:53 ` Tony Lindgren
2012-10-18 5:26 ` Afzal Mohammed
2012-10-19 15:34 ` Afzal Mohammed
2012-10-22 19:51 ` Daniel Mack
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20121009030126.GB12552@atomide.com \
--to=tony@atomide$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox