linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: s.hauer@pengutronix.de (Sascha Hauer)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] pinctrl: imx: move hard-coding data into device tree
Date: Thu, 21 Feb 2013 08:55:39 +0100	[thread overview]
Message-ID: <20130221075539.GI1906@pengutronix.de> (raw)
In-Reply-To: <20130221053020.GE17738@S2101-09.ap.freescale.net>

On Thu, Feb 21, 2013 at 01:30:22PM +0800, Shawn Guo wrote:
> On Wed, Feb 20, 2013 at 12:04:58PM -0700, Stephen Warren wrote:
> > There are a couple of potential issues with this patch, which I'm in two
> > minds about:
> > 
> > 1)
> > 
> > This is an incompatible change to the DT binding definition. A DT
> > written to the old specification won't work with a newer kernel and
> > vice-versa. This isn't supposed to happen with device tree.
> > 
> > Right now I believe we're still being flexible about DT binding changes,
> > but I've seen hints that this kind of thing will start getting lots of
> > push-back in the near future...
> > 
> Last time I heard of the time frame about doing this is when we get
> device tree source maintained in a separate repository from the kernel
> tree.  I'm not sure how far we're still away from that.  But most of
> sub-architectures (including IMX) have not been converted over to
> device tree.  And as far as I know, none of IMX based product runs
> device tree kernel yet.

The nature of open source makes it hard to know which devices ship out
there, so please don't assume there are none just because you know of
none.

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-02-21  7:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-02-20  7:08 [PATCH 0/3] Get rid of big array from imx pinctrl driver Shawn Guo
2013-02-20  7:08 ` [PATCH 1/3] ARM: dts: imx: use pre-processor for device trees Shawn Guo
2013-02-20  9:26   ` Dong Aisheng
2013-02-20  9:25 ` [PATCH 0/3] Get rid of big array from imx pinctrl driver Dong Aisheng
     [not found] ` <1361344089-16804-4-git-send-email-shawn.guo@linaro.org>
2013-02-20  9:44   ` [PATCH 3/3] pinctrl: imx: move hard-coding data into device tree Dong Aisheng
2013-02-21  6:04     ` Shawn Guo
2013-02-20 19:04   ` Stephen Warren
2013-02-21  5:30     ` Shawn Guo
2013-02-21  7:55       ` Sascha Hauer [this message]
2013-02-21  9:36     ` Dong Aisheng
2013-02-21 19:57       ` Stephen Warren
2013-02-26  8:02         ` Dong Aisheng
     [not found] ` <1361344089-16804-3-git-send-email-shawn.guo@linaro.org>
2013-02-20  9:30   ` [PATCH 2/3] ARM: dts: imx: replace magic number with pin function name Dong Aisheng
2013-02-20 18:46   ` Stephen Warren
2013-02-21  0:03     ` Matt Sealey
2013-02-21  0:34       ` Stephen Warren
2013-02-21  5:02       ` Shawn Guo
2013-02-21 17:36         ` Matt Sealey
2013-02-21 17:57           ` Matt Sealey
2013-02-21 21:43           ` Sascha Hauer
2013-02-22  7:58             ` Shawn Guo
2013-02-22  5:52           ` Shawn Guo
2013-02-22  7:27             ` Sascha Hauer
2013-02-22  7:36               ` Shawn Guo
2013-02-22  8:12                 ` Sascha Hauer
2013-02-27  6:51             ` Matt Sealey
2013-02-27  7:44               ` Sascha Hauer
2013-02-27 18:16                 ` Matt Sealey
2013-02-27 20:00                   ` Sascha Hauer
2013-02-28  3:06                   ` Shawn Guo
2013-02-21  4:59     ` 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=20130221075539.GI1906@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).