From: Tony Lindgren <tony@atomide.com>
To: Jon Hunter <jon-hunter@ti.com>
Cc: Christoph Fritz <chf.fritz@googlemail.com>,
Javier Martinez Canillas <javier.martinez@collabora.co.uk>,
Daniel Mack <daniel@zonque.org>,
linux-omap@vger.kernel.org
Subject: Re: ARM: dts: omap3: NAND support - how?
Date: Fri, 19 Apr 2013 09:15:22 -0700 [thread overview]
Message-ID: <20130419161522.GJ10155@atomide.com> (raw)
In-Reply-To: <5171692C.1080407@ti.com>
* Jon Hunter <jon-hunter@ti.com> [130419 09:01]:
> On 04/19/2013 10:48 AM, Tony Lindgren wrote:
> >
> > What about DVFS though? The L3 clock can get rescaled with DVFS,
> > and after that the retime function needs to get called. We are
> > not doing it in the mainline tree, but at least n8x0 - n900 vendor
> > trees were doing it.
>
> I wondered if you would mention that ;-)
>
> If you look at the implementation of the omap2_nand_gpmc_retime(), it
> does not actually perform any retiming base upon frequency whatsoever
> (unlike smc91c96_gpmc_retime). So right now omap2_nand_gpmc_retime is a
> basic wrapper around gpmc_cs_set_timings() really adding no value.
> Hence, I agree with Christoph's patch to remove it.
OK thanks fine with me then.
Tony
next prev parent reply other threads:[~2013-04-19 16:15 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 19:03 ARM: dts: omap3: NAND support - how? Christoph Fritz
2013-04-18 19:39 ` Jon Hunter
2013-04-18 20:23 ` Christoph Fritz
2013-04-18 22:28 ` Jon Hunter
2013-04-18 22:48 ` Christoph Fritz
2013-04-18 23:24 ` Jon Hunter
2013-04-18 23:26 ` Jon Hunter
2013-04-19 9:01 ` Christoph Fritz
2013-04-19 12:02 ` Christoph Fritz
2013-04-19 14:00 ` Jon Hunter
2013-04-19 14:53 ` Christoph Fritz
2013-04-19 15:36 ` Jon Hunter
2013-04-19 15:48 ` Tony Lindgren
2013-04-19 15:56 ` Jon Hunter
2013-04-19 16:15 ` Tony Lindgren [this message]
2013-04-19 16:29 ` [PATCH] ARM: OMAP2+: nand: reorganize gpmc timing values Christoph Fritz
2013-05-16 15:49 ` Tony Lindgren
2013-04-19 12:57 ` ARM: dts: omap3: NAND support - how? Jon Hunter
2013-04-19 13:06 ` Christoph Fritz
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=20130419161522.GJ10155@atomide.com \
--to=tony@atomide.com \
--cc=chf.fritz@googlemail.com \
--cc=daniel@zonque.org \
--cc=javier.martinez@collabora.co.uk \
--cc=jon-hunter@ti.com \
--cc=linux-omap@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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;
as well as URLs for NNTP newsgroup(s).