linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (s.hauer at pengutronix.de)
To: linux-arm-kernel@lists.infradead.org
Subject: 答复: [PATCH v3 2/2] i2c: imx: Add Vybrid VF610 I2C controller support
Date: Tue, 13 Aug 2013 09:46:21 +0200	[thread overview]
Message-ID: <20130813074620.GR26614@pengutronix.de> (raw)
In-Reply-To: <52096E77.4040003@wwwdotorg.org>

On Mon, Aug 12, 2013 at 05:23:35PM -0600, Stephen Warren wrote:
> On 08/12/2013 10:43 AM, Mark Rutland wrote:
> >> The binding string for i2c-imx driver in Documentation/devicetree/bindings/i2c/i2c-imx.txt use a wildcard format
> >> of "- compatible : Should be "fsl,<chip>-i2c" " for device using this driver. Neither fsl,imx1-i2c nor fsl,imx21-i2c
> >> is described in the binding document. So I just leave the vf610 i2c compatible with this. 
> > 
> > I'm not a big fan on wildcards in bindings, as it leaves people free to
> > put anything in and claim it's a documented binding, and makes it far
> > harder for an os to actually implement drivers for said binding, as
> > there's no canonical reference for the set of valid variations.
> > 
> > Obviously there is some precedent, but I'm not sure it's something we
> > want to stick with, and we can prevent it my updating the documentation
> > now.
> > 
> > Does anyone else have an opinion?
> 
> I suppose technically we should list out every exact string in the
> binding, but it's a little annoying to have to update the binding doc
> every time a new chip comes out (and I expect that'll happen more and
> more!) just to add a new compatible value since all the differences are
> known internally to the driver and don't impact the binding...

We would only have to update the the docs when an incompatible SoC comes
out. For this particular driver this would be all marked with a star:

* i.MX1
* i.MX21
  i.MX25
  i.MX27
  i.MX31
  i.MX35
  i.MX51
  i.MX53
  i.MX6
* Vybrid

That's not too many updates to the binding docs since 2001.
(The SPI core changed with nearly every SoC version though)

Sascha

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

  reply	other threads:[~2013-08-13  7:46 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  4:44 [PATCH RESEND 1/2] ARM: dts: vf610-twr: enable i2c0 device Jingchang Lu
2013-08-02  4:44 ` [PATCH v3 2/2] i2c: imx: Add Vybrid VF610 I2C controller support Jingchang Lu
2013-08-05  8:30   ` Sascha Hauer
2013-08-05  9:32     ` Lu Jingchang-B35083
2013-08-05  9:53       ` Sascha Hauer
2013-08-05 15:51         ` 答复: " Lu Jingchang-B35083
2013-08-10 14:08   ` Mark Rutland
2013-08-12 12:56     ` 答复: " Lu Jingchang-B35083
2013-08-12 16:43       ` Mark Rutland
2013-08-12 16:59         ` Tomasz Figa
2013-08-12 17:04           ` Kumar Gala
2013-08-12 23:23         ` 答复: " Stephen Warren
2013-08-13  7:46           ` s.hauer at pengutronix.de [this message]
2013-08-13 15:48             ` Stephen Warren
2013-08-13 16:12               ` s.hauer at pengutronix.de
2013-08-14  3:29                 ` Shawn Guo
2013-08-15  9:48                 ` Wolfram Sang
2013-08-04 13:30 ` [PATCH RESEND 1/2] ARM: dts: vf610-twr: enable i2c0 device Shawn Guo

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=20130813074620.GR26614@pengutronix.de \
    --to=s.hauer@pengutronix.de \
    --cc=linux-arm-kernel@lists.infradead.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).