From: Arnd Bergmann <arnd@arndb.de>
To: linux-sh@vger.kernel.org
Subject: Re: [PATCH 7/9] ARM: shmobile: APE6EVM: add MMCIF and SDHI DT nodes
Date: Fri, 21 Jun 2013 08:19:51 +0000 [thread overview]
Message-ID: <201306211019.52102.arnd@arndb.de> (raw)
In-Reply-To: <1368802520-16378-8-git-send-email-g.liakhovetski@gmx.de>
On Friday 21 June 2013, Guennadi Liakhovetski wrote:
> My preference still lies with specific per-feature driver bindings like in
> my original implementation. Adding compatible strings to every driver for
> every new SoC seems an absolute no-go to me. But with per-feature driver
> bindings you would have exactly the same problem: if you later add support
> for a new feature to the driver, and that feature is present on older
> SoCs, the only way to enable it would be to replace the DT.
That is the main problem with the per-feature listing, but less of
a problem if you list both the original part and the specific name of
the new one in the compatible string.
It's also not an either-or thing. For a number of features, having
flags makes most sense, in particular when the feature is not
a property of the IP block but of the way it is connected to the
rest of the SoC.
Arnd
prev parent reply other threads:[~2013-06-21 8:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 14:55 [PATCH 7/9] ARM: shmobile: APE6EVM: add MMCIF and SDHI DT nodes Guennadi Liakhovetski
2013-06-19 8:25 ` Magnus Damm
2013-06-20 21:10 ` Guennadi Liakhovetski
2013-06-21 6:24 ` Magnus Damm
2013-06-21 6:33 ` Guennadi Liakhovetski
2013-06-21 7:31 ` Magnus Damm
2013-06-21 7:48 ` Guennadi Liakhovetski
2013-06-21 8:11 ` Laurent Pinchart
2013-06-21 8:17 ` Arnd Bergmann
2013-06-21 8:19 ` Arnd Bergmann [this message]
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=201306211019.52102.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=linux-sh@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.