All of lore.kernel.org
 help / color / mirror / Atom feed
From: Afzal Mohammed <x0148406@ti.com>
To: Tony Lindgren <tony@atomide.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>,
	Artem Bityutskiy <artem.bityutskiy@linux.intel.com>,
	David Woodhouse <David.Woodhouse@intel.com>
Subject: Re: [PATCH 0/4] OMAP-GPMC generic timing migration
Date: Tue, 16 Oct 2012 12:26:13 +0530	[thread overview]
Message-ID: <507D050D.2090402@ti.com> (raw)
In-Reply-To: <20121015160154.GB15569@atomide.com>

Hi Tony,

On Monday 15 October 2012 09:31 PM, Tony Lindgren wrote:
> * Mohammed, Afzal<afzal@ti.com>  [121015 05:42]:
>> On Thu, Oct 11, 2012 at 20:17:56, Tony Lindgren wrote:

>>> 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.

>> Ok, I will keep timings aside for now and proceed with DT
>> (avoiding auxdata usage with generic routine looked to me a
>> saner approach though, with an initial DT'fy delay)

> Oh well if you think it's easier to do the timings too in
> the DT binding, please go ahead with that. It may take some
> longer discussion on the lists for the binding though. But
> up to you.

I certainly don't think it is easier, rather tougher, cleaner
as well. One thing that worried me was, if we pursue the
auxdata path (a last resort option) and later if it is
objected, we would be back to square one.

Let me discuss internally and get back.

Regards
Afzal

WARNING: multiple messages have this Message-ID (diff)
From: x0148406@ti.com (Afzal Mohammed)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 0/4] OMAP-GPMC generic timing migration
Date: Tue, 16 Oct 2012 12:26:13 +0530	[thread overview]
Message-ID: <507D050D.2090402@ti.com> (raw)
In-Reply-To: <20121015160154.GB15569@atomide.com>

Hi Tony,

On Monday 15 October 2012 09:31 PM, Tony Lindgren wrote:
> * Mohammed, Afzal<afzal@ti.com>  [121015 05:42]:
>> On Thu, Oct 11, 2012 at 20:17:56, Tony Lindgren wrote:

>>> 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.

>> Ok, I will keep timings aside for now and proceed with DT
>> (avoiding auxdata usage with generic routine looked to me a
>> saner approach though, with an initial DT'fy delay)

> Oh well if you think it's easier to do the timings too in
> the DT binding, please go ahead with that. It may take some
> longer discussion on the lists for the binding though. But
> up to you.

I certainly don't think it is easier, rather tougher, cleaner
as well. One thing that worried me was, if we pursue the
auxdata path (a last resort option) and later if it is
objected, we would be back to square one.

Let me discuss internally and get back.

Regards
Afzal

  reply	other threads:[~2012-10-16  6:56 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
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 [this message]
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=507D050D.2090402@ti.com \
    --to=x0148406@ti.com \
    --cc=David.Woodhouse@intel.com \
    --cc=artem.bityutskiy@linux.intel.com \
    --cc=jon-hunter@ti.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=paul@pwsan.com \
    --cc=tony@atomide.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.