From: wsa@the-dreams.de (Wolfram Sang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] ARM: sunxi: dt: Convert to the new i2c compatibles
Date: Fri, 14 Feb 2014 08:44:07 +0100 [thread overview]
Message-ID: <20140214074407.GA2569@katana> (raw)
In-Reply-To: <20140213225248.GB15350@lukather>
> > For non-a10, That should be at least
> >
> > compatible = "allwinner,sun4i-a13-i2c", "allwinner,sun4i-a10-i2c";
> >
> > or
> >
> > compatible = "allwinner,sun4i-a13-i2c", "allwinner,sun4i-i2c";
> >
> > depending on the outcome above.
> >
> > Or is my knowledge outdated already?
> >
>
> Since they are strictly compatible, we don't need to introduce any
> different compatible string here.
You never know all errata in advance. From what I know, one should
always use the specfic naming first, and then the generic fallback. So,
in case a distinction is needed later (think errata), then one doesn't
need to change the devicetrees.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140214/23f31104/attachment.sig>
next prev parent reply other threads:[~2014-02-14 7:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-06 9:51 [PATCH v2 0/2] i2c: sunxi: Change compatibles pattern Maxime Ripard
2014-02-06 9:51 ` [PATCH v2 1/2] i2c: sunxi: Change i2c compatibles Maxime Ripard
2014-02-06 9:51 ` [PATCH v2 2/2] ARM: sunxi: dt: Convert to the new " Maxime Ripard
2014-02-13 8:26 ` Wolfram Sang
2014-02-13 22:52 ` Maxime Ripard
2014-02-14 7:44 ` Wolfram Sang [this message]
2014-02-14 20:36 ` Maxime Ripard
2014-02-13 8:19 ` [PATCH v2 0/2] i2c: sunxi: Change compatibles pattern Wolfram Sang
2014-02-13 22:37 ` Maxime Ripard
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=20140214074407.GA2569@katana \
--to=wsa@the-dreams.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