public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Felipe Balbi <balbi@ti.com>
To: Richard Cochran <richardcochran@gmail.com>
Cc: Felipe Balbi <balbi@ti.com>, Mugunthan V N <mugunthanvnm@ti.com>,
	netdev@vger.kernel.org, davem@davemloft.net,
	linux-omap@vger.kernel.org
Subject: Re: [net-next PATCH 1/1] drivers: net: cpsw: Add support for new CPSW IP version
Date: Wed, 31 Jul 2013 23:26:17 +0300	[thread overview]
Message-ID: <20130731202617.GB3737@radagast> (raw)
In-Reply-To: <20130731202006.GE8027@netboy>

[-- Attachment #1: Type: text/plain, Size: 1384 bytes --]

Hi,

On Wed, Jul 31, 2013 at 10:20:07PM +0200, Richard Cochran wrote:
> On Wed, Jul 31, 2013 at 11:07:56PM +0300, Felipe Balbi wrote:
> > 
> > what I'm saying is that we can give new IP revision a chance to work if
> > they have no programming model differences (except for, perhaps, new
> > features and different erratas).
> 
> But it also has a chance to fail when there are differences.
> Comparing CPSW V1 with V2, it appears that TI likes to move the
> registers around between versions. To me, this is reason enough to
> make the driver defensive.

oh well, we can go on and on with this. Unfortunately we (SW team) don't
have control over the HW folks. We strongly suggest that they don't
break SW compatibility, and that's starting to become true.

You can very well expect next version of CPSW to be SW compatible. If it
isn't, then TI will send patches to add a new revision check and treat
it well. We are the first ones to have access to new versions of all
our IPs anyway.

And, IMHO, even if HW engineers decides to move registers around in CPSW
v3, that still doesn't chage the fact that defaulting to highest known
revision is a good practice.

Bailing out just because the revision check isn't what you expect it to
be is a very poor practice and leads to periodic patches updating
'switch' statements all over the place.

-- 
balbi

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2013-07-31 20:26 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-31 12:12 [net-next PATCH 1/1] drivers: net: cpsw: Add support for new CPSW IP version Mugunthan V N
2013-07-31 14:49 ` Richard Cochran
2013-07-31 15:28   ` Felipe Balbi
2013-07-31 16:38     ` Richard Cochran
2013-07-31 18:45       ` Felipe Balbi
2013-07-31 19:22         ` Richard Cochran
2013-07-31 19:43           ` Felipe Balbi
2013-07-31 19:45             ` Felipe Balbi
2013-07-31 20:04               ` Richard Cochran
2013-07-31 20:07                 ` Felipe Balbi
2013-07-31 20:20                   ` Richard Cochran
2013-07-31 20:26                     ` Felipe Balbi [this message]
2013-07-31 20:34                       ` Richard Cochran
2013-07-31 21:11                         ` Felipe Balbi
2013-08-01  4:43                           ` Richard Cochran
2013-08-01  4:46             ` Richard Cochran
2013-07-31 23:55 ` David Miller

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=20130731202617.GB3737@radagast \
    --to=balbi@ti.com \
    --cc=davem@davemloft.net \
    --cc=linux-omap@vger.kernel.org \
    --cc=mugunthanvnm@ti.com \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox