All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Mohammed, Afzal" <afzal@ti.com>
Cc: Daniel Mack <zonque@gmail.com>, Paul Walmsley <paul@pwsan.com>,
	"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
	"Hunter, Jon" <jon-hunter@ti.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/4] OMAP-GPMC generic timing migration
Date: Thu, 11 Oct 2012 07:47:56 -0700	[thread overview]
Message-ID: <20121011144756.GB12552@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E9FBC41@DBDE01.ent.ti.com>

* Mohammed, Afzal <afzal@ti.com> [121011 05:48]:
> Hi Daniel,
> 
> On Thu, Oct 11, 2012 at 17:15:42, Daniel Mack wrote:
> 
> > Admittedly, I lost track on the multiple GPMC series here, and they also
> > cause major merge conflicts with Linus' current master branch.
> > 
> > Could you tell me which patches I need on top of soon-to-be-3.7-rc1? I
> 
> Series [1-2] plus this series would be the required.
> Note that 1st patch of series [2] has already reached mainline.
> 
> Another easy way would be, pull,
> git://gitorious.org/x0148406-public/linux-kernel.git gpmc-timing
> 
> git checkout -b gpmc <myremote/gpmc-timing>
> git rebase --onto <Linus-current-master> next-20121005 (or "080aa9c")

After -rc1 is out, let's plan on adding the minimal
set required for removing plat and mach includes from
drivers into a clean-up branch. Afzal, can you maybe
do a pull request for that set against -rc1 when it's
out? Just the minimal set of patches.

> > would like to augment this to make GPMC attached NAND probable in DT, in
> > case this is still an open topic.
> 
> I would be doing gpmc DT conversion next. Hoping that this
> series too will be picked up by Tony, as once this series is
> accepted, during DT conversion we need not rely on
> auxdata (a last resort option) for timings.

Yes, then please do a second pull request for what's needed
to apply the minimal DT bindings. For the DT binding, let's
just leave out the timings for now as we can load those from
auxdata. Then the binding for the timings can be added
later on. So just the minimal binding using standard features
for the iorange and interrupt.

Thanks,

Tony 

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] OMAP-GPMC generic timing migration
Date: Thu, 11 Oct 2012 07:47:56 -0700	[thread overview]
Message-ID: <20121011144756.GB12552@atomide.com> (raw)
In-Reply-To: <C8443D0743D26F4388EA172BF4E2A7A93E9FBC41@DBDE01.ent.ti.com>

* Mohammed, Afzal <afzal@ti.com> [121011 05:48]:
> Hi Daniel,
> 
> On Thu, Oct 11, 2012 at 17:15:42, Daniel Mack wrote:
> 
> > Admittedly, I lost track on the multiple GPMC series here, and they also
> > cause major merge conflicts with Linus' current master branch.
> > 
> > Could you tell me which patches I need on top of soon-to-be-3.7-rc1? I
> 
> Series [1-2] plus this series would be the required.
> Note that 1st patch of series [2] has already reached mainline.
> 
> Another easy way would be, pull,
> git://gitorious.org/x0148406-public/linux-kernel.git gpmc-timing
> 
> git checkout -b gpmc <myremote/gpmc-timing>
> git rebase --onto <Linus-current-master> next-20121005 (or "080aa9c")

After -rc1 is out, let's plan on adding the minimal
set required for removing plat and mach includes from
drivers into a clean-up branch. Afzal, can you maybe
do a pull request for that set against -rc1 when it's
out? Just the minimal set of patches.

> > would like to augment this to make GPMC attached NAND probable in DT, in
> > case this is still an open topic.
> 
> I would be doing gpmc DT conversion next. Hoping that this
> series too will be picked up by Tony, as once this series is
> accepted, during DT conversion we need not rely on
> auxdata (a last resort option) for timings.

Yes, then please do a second pull request for what's needed
to apply the minimal DT bindings. For the DT binding, let's
just leave out the timings for now as we can load those from
auxdata. Then the binding for the timings can be added
later on. So just the minimal binding using standard features
for the iorange and interrupt.

Thanks,

Tony 

  reply	other threads:[~2012-10-11 14:48 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-05 16:00 [PATCH 0/4] OMAP-GPMC generic timing migration Afzal Mohammed
2012-10-05 16:00 ` Afzal Mohammed
2012-10-05 16:01 ` [PATCH 1/4] ARM: OMAP2+: gpmc: generic timing calculation Afzal Mohammed
2012-10-05 16:01   ` Afzal Mohammed
2012-10-05 16:01 ` [PATCH 2/4] ARM: OMAP2+: onenand: " Afzal Mohammed
2012-10-05 16:01   ` Afzal Mohammed
2012-10-05 16:01 ` [PATCH 3/4] ARM: OMAP2+: smc91x: " Afzal Mohammed
2012-10-05 16:01   ` Afzal Mohammed
2012-10-05 16:01 ` [PATCH 4/4] ARM: OMAP2+: tusb6010: " Afzal Mohammed
2012-10-05 16:01   ` Afzal Mohammed
2012-10-09  3:01 ` [PATCH 0/4] OMAP-GPMC generic timing migration Tony Lindgren
2012-10-09  3:01   ` Tony Lindgren
2012-10-09 12:59   ` Afzal Mohammed
2012-10-09 12:59     ` Afzal Mohammed
2012-10-11 11:45 ` Daniel Mack
2012-10-11 11:45   ` Daniel Mack
2012-10-11 12:47   ` Mohammed, Afzal
2012-10-11 12:47     ` Mohammed, Afzal
2012-10-11 14:47     ` Tony Lindgren [this message]
2012-10-11 14:47       ` Tony Lindgren
2012-10-15 12:41       ` Mohammed, Afzal
2012-10-15 12:41         ` Mohammed, Afzal
2012-10-15 16:01         ` Tony Lindgren
2012-10-15 16:01           ` Tony Lindgren
2012-10-16  6:56           ` Afzal Mohammed
2012-10-16  6:56             ` Afzal Mohammed
2012-10-17  5:42             ` Afzal Mohammed
2012-10-17  5:42               ` Afzal Mohammed
2012-10-17 15:13               ` Daniel Mack
2012-10-17 15:13                 ` Daniel Mack
2012-10-17 15:53                 ` Tony Lindgren
2012-10-17 15:53                   ` Tony Lindgren
2012-10-18  5:26                 ` Afzal Mohammed
2012-10-18  5:26                   ` Afzal Mohammed
2012-10-19 15:34   ` Afzal Mohammed
2012-10-19 15:34     ` Afzal Mohammed
2012-10-22 19:51     ` Daniel Mack
2012-10-22 19:51       ` Daniel Mack

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=20121011144756.GB12552@atomide.com \
    --to=tony@atomide.com \
    --cc=afzal@ti.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=zonque@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.