From: Tony Lindgren <tony@atomide.com>
To: Mike Rapoport <mike@compulab.co.il>
Cc: linux-omap@vger.kernel.org, vimal.newwork@gmail.com, s-ghorai@ti.com
Subject: Re: [PATCH v2 3/3] omap: gpmc-nand: add ability to keep timings defined by the bootloader
Date: Mon, 3 May 2010 11:24:26 -0700 [thread overview]
Message-ID: <20100503182426.GX29604@atomide.com> (raw)
In-Reply-To: <f20c8d0dc1c81a0cc5a334d03c9c7dc73046293d.1272530653.git.mike@compulab.co.il>
* Mike Rapoport <mike@compulab.co.il> [100429 01:44]:
> Signed-off-by: Mike Rapoport <mike@compulab.co.il>
Please add a proper description to all the patches.
> --- a/arch/arm/mach-omap2/gpmc-nand.c
> +++ b/arch/arm/mach-omap2/gpmc-nand.c
> @@ -116,6 +124,11 @@ int __init gpmc_nand_init(struct omap_nand_platform_data *_nand_data)
> return err;
> }
>
> + if (gpmc_nand_data->keep_timings) {
> + gpmc_cs_get_timings(gpmc_nand_data->cs, &gpmc_default_timings);
> + gpmc_nand_data->gpmc_t = &gpmc_default_timings;
> + }
> +
> err = gpmc_nand_setup();
> if (err < 0) {
> dev_err(dev, "NAND platform setup failed: %d\n", err);
Hmm, so you're setting the timings based on the bootloader values?
I' think the problem with that is that chances are that it still won't
work for other L3 frequencies because of rounding errors.
With gpmc_cs_get_timings() you're already using tick rounded timings,
so you won't get the required accuracy out of those for the other
L3 frequencies.
So maybe just not do anything, and print a warning on gpmc L3 changes
if the timings are not set?
Regards,
Tony
next prev parent reply other threads:[~2010-05-03 18:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-29 8:48 [PATCH v2 0/3] omap: gpmc-nand: add ability to keep timings defined by the bootloader Mike Rapoport
2010-04-29 8:48 ` [PATCH v2 1/3] omap: gpmc: add gpmc_cs_get_timings Mike Rapoport
2010-04-29 8:48 ` [PATCH v2 2/3] omap: gpmc-nand: introduce omap2_nand_gpmc_round_timings helper Mike Rapoport
2010-04-29 8:48 ` [PATCH v2 3/3] omap: gpmc-nand: add ability to keep timings defined by the bootloader Mike Rapoport
2010-05-03 18:24 ` Tony Lindgren [this message]
2010-05-03 20:32 ` Mike Rapoport
2010-05-03 21:16 ` Tony Lindgren
2010-05-04 13:22 ` Mike Rapoport
2010-05-04 21:46 ` Tony Lindgren
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=20100503182426.GX29604@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=mike@compulab.co.il \
--cc=s-ghorai@ti.com \
--cc=vimal.newwork@gmail.com \
/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).