public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Nishanth Menon <nm@ti.com>, Paul Walmsley <paul@pwsan.com>,
	"Pandita, Vikram" <vikram.pandita@ti.com>,
	"Woodruff, Richard" <r-woodruff2@ti.com>,
	"linux-omap@vger.kernel.org" <linux-om>
Subject: Re: [PATCH v2 1/2] omap: add bits for future 3430/3630 ES revisions
Date: Mon, 2 Nov 2009 11:49:10 -0600	[thread overview]
Message-ID: <4AEF1B96.6070406@ti.com> (raw)
In-Reply-To: <20091102170123.GC15200@shisha.kicks-ass.net>

Alexander Shishkin had written, on 11/02/2009 11:01 AM, the following:
[..]
>>>> Issues with the strategy of restricting to the current 8 bits:
>>>> a) Why extrabits now:
>>>> we have 8 bits now and we would have used all 8 bits with 3630 with the
>>>> mentioned patch. What do we do with the next revision of 3430? Do we want to
>>>> increase the size once it comes along? OR Do we want to do it right now? Why
>>>> wait till we get additional silicons to go figure how to add those bits as
>>>> Richard pointed out, when there could be one more in the pipeline?
>>> But this code will have to be revisited for each additional silicon
>>> revision anyway, right? Why reserve now?
>>>
>> Agreed, that is one of the possible approaches we could take (and
>> seems to be the common consensus), we can review the structure at a
>> later point of time.
>>
>> http://patchwork.kernel.org/patch/54847/ seems to be the right
>> direction for now at least.
> 
> Ok, so let's have it in, perhaps.
Tony, Kevin, upto you guys now..

-- 
Regards,
Nishanth Menon

  reply	other threads:[~2009-11-02 17:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-20 22:26 [PATCH v2 1/2] omap: add bits for future 3430/3630 ES revisions Vikram Pandita
2009-10-20 22:26 ` [PATCH v2 2/2] omap: 3630: update is_chip variable Vikram Pandita
2009-10-20 23:14 ` [PATCH v2 1/2] omap: add bits for future 3430/3630 ES revisions Paul Walmsley
2009-10-21  1:07   ` Nishanth Menon
2009-10-21  1:15     ` Nishanth Menon
2009-11-02 13:12     ` Alexander Shishkin
2009-11-02 14:13       ` Nishanth Menon
2009-11-02 17:01         ` Alexander Shishkin
2009-11-02 17:49           ` Nishanth Menon [this message]
2009-12-15 21:26             ` Paul Walmsley
2009-10-21 17:48   ` Pandita, Vikram

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=4AEF1B96.6070406@ti.com \
    --to=nm@ti.com \
    --cc=paul@pwsan.com \
    --cc=r-woodruff2@ti.com \
    --cc=vikram.pandita@ti.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