linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: arm@kernel.org, linux-omap@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [GIT PULL 2/3] omap gpmc changes for v3.19
Date: Thu, 20 Nov 2014 08:08:36 -0800	[thread overview]
Message-ID: <20141120160836.GO7046@atomide.com> (raw)
In-Reply-To: <201411201202.41698.arnd@arndb.de>

* Arnd Bergmann <arnd@arndb.de> [141120 03:04]:
> On Wednesday 12 November 2014, Tony Lindgren wrote:
> > GPMC (General Purpose Memory Controller) changes for omaps. These
> > changes allow us to drop dependencies to bootloader timings now
> > that the known device tree entries have been fixed. So we can now
> > require proper timings to be configured and get rid of the legacy
> > smsc91x code.
> > 
> > Note that this branch has a dependency to the related device tree
> > branch sent in a separate pull request as timings are now required.
> 
> Does this mean you are breaking compatibility with old dtb files?
> 
> Can you be more specific which machines are affected?

Not breaking compability. We had timings missing in the .dts files
for a few devices that caused all kinds of hacks in the GPMC code.

Now those are all fixed up and we are actually using the bindings.

Regards,

Tony

  reply	other threads:[~2014-11-20 16:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <pull-1415814409-868361>
2014-11-12 18:05 ` [GIT PULL 2/3] omap gpmc changes for v3.19 Tony Lindgren
2014-11-12 18:05 ` Tony Lindgren
2014-11-12 18:05 ` [GIT PULL 3/3] omap clean-up " Tony Lindgren
2014-11-12 18:05 ` Tony Lindgren
2014-11-20 10:47 ` [GIT PULL 1/3] omap device tree changes " Arnd Bergmann
     [not found] ` <pull-1415814409-868361-2>
2014-11-20 11:02   ` [GIT PULL 2/3] omap gpmc " Arnd Bergmann
2014-11-20 16:08     ` Tony Lindgren [this message]
2014-11-20 16:25       ` 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=20141120160836.GO7046@atomide.com \
    --to=tony@atomide.com \
    --cc=arm@kernel.org \
    --cc=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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).