linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] ARM: OMAP: GPMC generic timing
Date: Mon, 12 Nov 2012 15:50:43 -0800	[thread overview]
Message-ID: <20121112235042.GY6801@atomide.com> (raw)
In-Reply-To: <1352470910-9630-1-git-send-email-afzal@ti.com>

* Afzal Mohammed <afzal@ti.com> [121109 06:23]:
> The following changes since commit 6ba54ab4a49bbad736b0254aa6bdf0cb83013815:
> 
>   ARM: OMAP: Remove omap_init_consistent_dma_size() (2012-11-06 16:01:19 -0800)
> 
> are available in the git repository at:
> 
>   git://gitorious.org/x0148406-public/linux-kernel.git tags/gpmc-generic-timing
> 
> for you to fetch changes up to 47acde16726080e5157b602f23937d00a04cd2ed:
> 
>   ARM: OMAP2+: tusb6010: generic timing calculation (2012-11-09 18:07:23 +0530)
> 
> ----------------------------------------------------------------
> These changes provide a generic gpmc timing calculation method,
> migrates existing peripherals that makes use of custom gpmc timing
> calculation method to use the new generic one.
> 
> Generic routine has been verified for onenand async timing calculation
> on omap3evm (with a local change to add onenand support). Generic
> timing calculation method were verified for other peripherals by
> simulation. Generic method has to be verified on peripherals supported
> in mainline.

Thanks pulled into omap-for-v3.8/gpmc. I've replaced the second paragraph
in my tag with the following as that's what I've tried it with:

The generic timing routine has been tested with onenand, smsc911x,
and tusb6010 devices connected to GPMC in addition to simulating
other devices support in the mainline kernel.

Regards,

Tony

      reply	other threads:[~2012-11-12 23:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-11-09 14:21 [GIT PULL] ARM: OMAP: GPMC generic timing Afzal Mohammed
2012-11-12 23:50 ` Tony Lindgren [this message]

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=20121112235042.GY6801@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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).