devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Pawel Moll <pawel.moll@arm.com>
To: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Cc: Stephen Warren <swarren@wwwdotorg.org>,
	"linux-sh@vger.kernel.org" <linux-sh@vger.kernel.org>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	Magnus Damm <magnus.damm@gmail.com>, Chris Ball <cjb@laptop.org>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	Simon Horman <horms@verge.net.au>,
	Ian Campbell <ian.campbell@citrix.com>,
	Mark Rutland <Mark.Rutland@arm.com>,
	"rob.herring@calxeda.com" <rob.herring@calxeda.com>
Subject: Re: [PATCH 1/2] mmc: add Device Tree properties for UHS modes
Date: Mon, 29 Jul 2013 11:50:53 +0100	[thread overview]
Message-ID: <1375095053.3340.7.camel@hornet> (raw)
In-Reply-To: <Pine.LNX.4.64.1307290903360.14405@axis700.grange>

On Mon, 2013-07-29 at 08:18 +0100, Guennadi Liakhovetski wrote:
> A short addendum. At least with Renesas SoCs I see the situation in the 
> following way: new SoC versions appear relatively frequently. 

What frequency are we talking about? Once per year? Once per month? I'm
not trying to be picky, it really makes a difference...

> With compatibility strings we have to change _all_ Renesas drivers for _each_ 
> SoC version even if just to add a new struct of_device_id entry. This 
> doesn't seem very productive to me.

There is at least precedence in the MMC world - have a look at
drivers/mmc/host/mmci.c and the struct variant_data... There seem to be
a new variant every 6 months or so (I must admit guilt of of making some
of them ;-) coming from two different companies.

And although it's a primecell (aka amba_bus) device, so the compatibilty
string remains the same, the struct amba_id was being extended every
time which is pretty much the same thing.

Pawel

PS. Having said all that I'm hoping the MMCI evolution has finally
stopped so no new variants will be needed ;-)



  reply	other threads:[~2013-07-29 10:50 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-26 15:51 [PATCH 1/2] mmc: add Device Tree properties for UHS modes Guennadi Liakhovetski
2013-07-26 15:51 ` [PATCH/RFC 2/2] ARM: shmobile: kzm9g: support DDR50 mode with 1.8V VccQ on MMCIF Guennadi Liakhovetski
2013-07-30  2:18   ` Simon Horman
2013-07-26 17:10 ` [PATCH 1/2] mmc: add Device Tree properties for UHS modes Stephen Warren
2013-07-26 20:23   ` Guennadi Liakhovetski
2013-07-26 21:36     ` Stephen Warren
2013-07-29  6:20       ` Guennadi Liakhovetski
2013-07-29  7:18         ` Guennadi Liakhovetski
2013-07-29 10:50           ` Pawel Moll [this message]
2013-07-29 11:27             ` Guennadi Liakhovetski
2013-07-29 11:42               ` Pawel Moll
2013-07-29 12:05                 ` Guennadi Liakhovetski
2013-07-29 13:07                   ` Pawel Moll
2013-07-29 13:30                     ` Guennadi Liakhovetski
2013-07-29 13:37                       ` Pawel Moll
2013-07-29 17:21                       ` Stephen Warren
2013-07-29 13:39           ` Rob Herring
2013-07-29 14:40             ` Guennadi Liakhovetski
2013-07-29 17:28         ` Stephen Warren
2013-07-29 10:57   ` Pawel Moll
2013-07-29 11:10     ` Guennadi Liakhovetski

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=1375095053.3340.7.camel@hornet \
    --to=pawel.moll@arm.com \
    --cc=Mark.Rutland@arm.com \
    --cc=cjb@laptop.org \
    --cc=devicetree@vger.kernel.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=horms@verge.net.au \
    --cc=ian.campbell@citrix.com \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=magnus.damm@gmail.com \
    --cc=rob.herring@calxeda.com \
    --cc=swarren@wwwdotorg.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).