devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Inki Dae <inki.dae@samsung.com>
Cc: Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	linux-samsung-soc@vger.kernel.org,
	Stephen Warren <swarren@wwwdotorg.org>,
	Leela Krishna Amudala <l.krishna@samsung.com>,
	devicetree-discuss@lists.ozlabs.org,
	dri-devel@lists.freedesktop.org, kgene.kim@samsung.com,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH V6 2/2] video: drm: exynos: Add device tree support
Date: Tue, 25 Sep 2012 16:31:09 +0100	[thread overview]
Message-ID: <20120925153109.GA8834@sirena.org.uk> (raw)
In-Reply-To: <CAAQKjZN++zZ9cfNCB21TeQwPZgFVU-Cmo9ZhVwaaMz+HO2vHig@mail.gmail.com>

On Wed, Sep 26, 2012 at 12:03:44AM +0900, Inki Dae wrote:
> 2012/9/25 Laurent Pinchart <laurent.pinchart@ideasonboard.com>:

> > Aren't DT bindings considered as an ABI, and required to be supported more or
> > less forever ? If you merge this DT binding you'll have to keep supporting it.
> > That's why DT bindings should not be rushed in.

> is ABI required for DT binding?  I know DT binding parses just lcd
> timing data from device tree file so ABI isn't needed. but when it
> comes to DT, I'm novice yet so there may be my missing point. could
> you tell me why DT bindings are considered as an ABI? if there is my
> missing point, will consider it again.

It's supposed to be possible to ship a DT with a board and then boot any
OS or OS version on the board.  If the meaning of the DT keeps changing
then this becomes impossible, you need to keep changing the DT when you
change the thing that parses it (rendering the whole exercise pointless).

  reply	other threads:[~2012-09-25 15:31 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-21 11:22 [PATCH V6 0/2] video: drm: Add Device tree support to exynos DRM-FIMD Leela Krishna Amudala
2012-09-21 11:22 ` [PATCH V6 1/2] drm/exynos: add platform_device_id table and driver data for drm fimd Leela Krishna Amudala
2012-09-21 11:22 ` [PATCH V6 2/2] video: drm: exynos: Add device tree support Leela Krishna Amudala
2012-09-21  5:14   ` Stephen Warren
2012-09-21  7:22     ` Inki Dae
2012-09-21 16:06       ` Stephen Warren
2012-09-24 12:35         ` Inki Dae
2012-09-25 13:03           ` Laurent Pinchart
2012-09-25 15:03             ` Inki Dae
2012-09-25 15:31               ` Mark Brown [this message]
2012-09-26  4:32                 ` Inki Dae
2012-10-01  5:29     ` Leela Krishna Amudala
     [not found]       ` <CAL1wa8eOA6eV-9EoeUFrSFaFwq5sEVnYXn9yKnPRv=0mSU5WvQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-01 16:20         ` Stephen Warren
2012-10-03  4:06           ` Leela Krishna Amudala
     [not found]             ` <CAL1wa8egdA=1iu8Jr-TQLnSweOQoCL=TD4cvo1BHHNn9UyOSEQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-10-03 15:27               ` Stephen Warren

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=20120925153109.GA8834@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=inki.dae@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=l.krishna@samsung.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-samsung-soc@vger.kernel.org \
    --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).