linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Roger Quadros <rogerq@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, arm@kernel.org
Cc: "tony@atomide.com" <tony@atomide.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	Robert ABEL <rabel@cit-ec.uni-bielefeld.de>,
	Semen Protsenko <semen.protsenko@globallogic.com>
Subject: [GIT PULL] OMAP-GPMC driver updates for v4.1
Date: Mon, 9 Mar 2015 14:09:38 +0200	[thread overview]
Message-ID: <54FD8D82.9060507@ti.com> (raw)

Hi Arnd,

Based on Tony's request I will be sending you pull requests for OMAP-GPMC driver
hence forth.

Please pull in these OMAP-GPMC driver fixes for v4.1.
Patches have been tested for GPMC-NAND on dra7-evm and omap3-beagle.

Thanks.

The following changes since commit c517d838eb7d07bbe9507871fab3931deccff539:

  Linux 4.0-rc1 (2015-02-22 18:21:14 -0800)

are available in the git repository at:

  git@github.com:rogerq/linux.git tags/gpmc-omap-for-v4.1

for you to fetch changes up to 4b613e9b4bbe94545a588a100e09006d827a7ebe:

  ARM OMAP2+ GPMC: fix programming/showing reserved timing parameters (2015-03-06 12:55:32 +0200)

----------------------------------------------------------------
OMAP-GPMC driver fixes for v4.1

* Fixed WAITMONITORINGTIME programming to be based on
GPMC_CLK instead of GPMC_FCLK. The GPMC clock divider
programming is fixed for both synchronous and asynchronous
modes.
* Allow GPMC's children of default bus type to be populated in
the device tree.
* Improved DEBUG output data and format.
* Prevent writing 1 into reserved bits of GPMC_CONFIG7.

----------------------------------------------------------------
Robert ABEL (8):
      ARM OMAP2+ GPMC: don't undef DEBUG
      ARM OMAP2+ GPMC: add bus children
      ARM OMAP2+ GPMC: fix debug output alignment
      ARM OMAP2+ GPMC: change get_gpmc_timing_reg output for DTS
      ARM OMAP2+ GPMC: always program GPMCFCLKDIVIDER
      ARM OMAP2+ GPMC: calculate GPMCFCLKDIVIDER based on WAITMONITORINGTIME
      ARM OMAP2+ GPMC: fix WAITMONITORINGTIME divider bug
      ARM OMAP2+ GPMC: fix programming/showing reserved timing parameters

Semen Protsenko (2):
      ARM: OMAP2+: gpmc: Fix writing in gpmc_cs_set_memconf
      ARM: OMAP2+: gpmc: make gpmc_cs_get_name() static

 arch/arm/mach-omap2/gpmc-nand.c    |  18 +++++----
 arch/arm/mach-omap2/gpmc-onenand.c |   4 +-
 arch/arm/mach-omap2/usb-tusb6010.c |   4 +-
 drivers/memory/omap-gpmc.c         | 358 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++---------------------------------
 include/linux/omap-gpmc.h          |   3 +-
 5 files changed, 305 insertions(+), 82 deletions(-)

             reply	other threads:[~2015-03-09 12:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-09 12:09 Roger Quadros [this message]
2015-03-17 13:27 ` [GIT PULL] OMAP-GPMC driver updates for v4.1 Roger Quadros
  -- strict thread matches above, loose matches on Subject: below --
2015-03-23 10:32 Roger Quadros
2015-03-30  7:55 ` Roger Quadros
2015-04-03 18:01 ` Olof Johansson
2015-04-09  9:35   ` Roger Quadros

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=54FD8D82.9060507@ti.com \
    --to=rogerq@ti.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=rabel@cit-ec.uni-bielefeld.de \
    --cc=semen.protsenko@globallogic.com \
    --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;
as well as URLs for NNTP newsgroup(s).