linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: alsa-devel@alsa-project.org, devicetree-discuss@lists.ozlabs.org,
	Barry Song <21cnbao@gmail.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	linux-input@vger.kernel.org, Liam Girdwood <lrg@ti.com>
Subject: Re: [PATCH] ASoC: Add device tree binding for WM8753
Date: Tue, 9 Aug 2011 23:28:52 +0900	[thread overview]
Message-ID: <20110809142851.GA15861@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <20110809065100.GB8017@core.coreip.homeip.net>

On Mon, Aug 08, 2011 at 11:51:00PM -0700, Dmitry Torokhov wrote:

> The issue I have with the ads7846 driver is that it still needs platform
> code to supply the needed platform data structure to make the
> driver/device usable. So I am not sure what the benefit DT matching code
> brings to that driver.

Oh, if that's the case the driver ought to have device tree bindings
which replicate the platform data.  Unless the platform data is
sufficiently obscure for hardly anyone to want to use it I guess.

  reply	other threads:[~2011-08-09 14:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1312778255-29755-1-git-send-email-broonie@opensource.wolfsonmicro.com>
2011-08-08  8:38 ` [alsa-devel] [PATCH] ASoC: Add device tree binding for WM8753 Barry Song
2011-08-08  8:55   ` Mark Brown
2011-08-09  6:51   ` Dmitry Torokhov
2011-08-09 14:28     ` Mark Brown [this message]
2011-08-10  1:21       ` Barry Song
2011-08-10  4:51         ` Mark Brown
2011-08-10  5:57           ` Barry Song
2011-08-10  6:30             ` Mark Brown
2011-08-12  3:16               ` Barry Song
2011-08-12  3:53                 ` Dmitry Torokhov
2011-08-12  4:35                   ` Barry Song
2011-08-12  4:41                   ` [alsa-devel] " Mark Brown
2011-08-12  5:57                     ` Dmitry Torokhov
2011-08-12  6:07                       ` Mark Brown

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=20110809142851.GA15861@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=21cnbao@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-input@vger.kernel.org \
    --cc=lrg@ti.com \
    /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).