public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Jon Hunter <jon-hunter@ti.com>
To: Tony Lindgren <tony@atomide.com>, Afzal Mohammed <afzal@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>,
	linux-arm <linux-arm-kernel@lists.infradead.org>,
	Jon Hunter <jon-hunter@ti.com>
Subject: [PATCH 0/2] ARM: OMAP2+: GPMC: Show correct frequency for OneNAND devices using async mode
Date: Thu, 28 Jun 2012 13:41:28 -0500	[thread overview]
Message-ID: <1340908890-28612-1-git-send-email-jon-hunter@ti.com> (raw)

Boards that have OneNAND devices but only support the async read and write modes
show that the OneNAND operating frequency is 0 MHz on boot. For example, the
OMAP3430 SDP shows the following:

omap2-onenand: initializing on CS2, phys base 0x20000000, virtual base c88c0000, freq 0 MHz

This series corrects this and cleans up the code that is determining the OneNAND
frequency. This series is based upon Afzal's prep-gpmc branch [1] and has been
tested on an OMAP3430 SDP.

[1] http://gitorious.org/x0148406-public/linux-kernel/trees/gpmc-prep

Jon Hunter (2):
  ARM: OMAP2+: GPMC: Remove unused OneNAND get_freq() platform function
  ARM: OMAP2+: GPMC: Show correct frequency for OneNAND devices using
    async mode

 arch/arm/mach-omap2/gpmc-onenand.c        |   53 +++++------------------------
 arch/arm/plat-omap/include/plat/onenand.h |    8 -----
 2 files changed, 9 insertions(+), 52 deletions(-)

-- 
1.7.9.5


             reply	other threads:[~2012-06-28 18:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 18:41 Jon Hunter [this message]
2012-06-28 18:41 ` [PATCH 1/2] ARM: OMAP2+: GPMC: Remove unused OneNAND get_freq() platform function Jon Hunter
2012-06-28 18:41 ` [PATCH 2/2] ARM: OMAP2+: GPMC: Show correct frequency for OneNAND devices using async mode Jon Hunter

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=1340908890-28612-1-git-send-email-jon-hunter@ti.com \
    --to=jon-hunter@ti.com \
    --cc=afzal@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=tony@atomide.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