From: "Hebbar, Gururaja" <gururaja.hebbar@ti.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"davinci-linux-open-source@linux.davincidsp.com"
<davinci-linux-open-source@linux.davincidsp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"tony@atomide.com" <tony@atomide.com>,
"Girdwood, Liam" <lrg@ti.com>, "perex@perex.cz" <perex@perex.cz>,
"Nori, Sekhar" <nsekhar@ti.com>,
"Rajashekhara, Sudhakar" <sudhakar.raj@ti.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"rob@landley.net" <rob@landley.net>
Subject: RE: [PATCH 2/2] ASoC: Davinci: machine: Add device tree binding
Date: Tue, 27 Nov 2012 12:53:00 +0000 [thread overview]
Message-ID: <1BAFE6F6C881BF42822005164F1491C33EADA52C@DBDE01.ent.ti.com> (raw)
In-Reply-To: <20121126115619.GF9411@opensource.wolfsonmicro.com>
On Mon, Nov 26, 2012 at 17:26:19, Mark Brown wrote:
> On Thu, Nov 22, 2012 at 09:34:59AM +0530, Hebbar, Gururaja wrote:
>
> > +- dai-data : A list of DAI data used by SOC code to register
> > + DAI, Codecs platform.
> > + The string index "should" be as shown below.
> > +dai-data =
> > +"<DAI Name>", "<DAI Stream Name>",
> > +"<CODEC DAI Name>", "<true if evm_aic3x_init is required, else false>",
> > +"<evm ops required (evm_ops or evm_spdif_ops)>";
>
> This continues to have the same issue as with previous versions, this is
> all Linux internals (especially the evm_aic3x_init thing) not a
> description of the hardware, there's not enough information to allow
> someone to work out what the bindings for their system should be.
Last time when you gave the review comments for this, I misunderstood it for
missing/incomplete documentation, which is why I added more details to the
binding document in V3.
Now that I have understood correctly, I will be removing references to
linux/software parts in the DT and will handle it internally in the driver
code.
Kindly accept my apologies in this regard.
>
> Do not post *ANY* further versions that have this evm_aic3x_init stuff
> in them, it's very annoying that you keep on ignoring this feedback.
Sure will remove the reference and repost it soon.
Thanks for all the review and guidance.
>
Regards,
Gururaja
next prev parent reply other threads:[~2012-11-27 12:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-22 4:04 [PATCH 0/2] ARM/ASoC: Davinci: Device Tree Update Hebbar, Gururaja
2012-11-22 4:04 ` [PATCH 1/2] ASoC: davinci-mcasp: Add pinctrl support Hebbar, Gururaja
2012-11-26 11:45 ` Mark Brown
2012-11-27 5:55 ` Peter Korsgaard
2012-11-27 14:04 ` Mark Brown
2012-11-22 4:04 ` [PATCH 2/2] ASoC: Davinci: machine: Add device tree binding Hebbar, Gururaja
2012-11-26 11:56 ` Mark Brown
2012-11-27 12:53 ` Hebbar, Gururaja [this message]
2012-11-26 11:41 ` [PATCH 0/2] ARM/ASoC: Davinci: Device Tree Update Hebbar, Gururaja
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=1BAFE6F6C881BF42822005164F1491C33EADA52C@DBDE01.ent.ti.com \
--to=gururaja.hebbar@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lrg@ti.com \
--cc=nsekhar@ti.com \
--cc=perex@perex.cz \
--cc=rob@landley.net \
--cc=sudhakar.raj@ti.com \
--cc=tony@atomide.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).