From: Mark Brown <broonie@opensource.wolfsonmicro.com> To: "Hebbar, Gururaja" <gururaja.hebbar@ti.com> Cc: alsa-devel@alsa-project.org, sudhakar.raj@ti.com, tony@atomide.com, nsekhar@ti.com, davinci-linux-open-source@linux.davincidsp.com, alsa-user@lists.sourceforge.net, lrg@ti.com, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH V2 5/6] ASoC: Davinci: machine: Add device tree binding Date: Mon, 27 Aug 2012 11:19:40 -0700 [thread overview] Message-ID: <20120827181939.GX4339@opensource.wolfsonmicro.com> (raw) In-Reply-To: <1346074004-22172-6-git-send-email-gururaja.hebbar@ti.com> On Mon, Aug 27, 2012 at 06:56:43PM +0530, Hebbar, Gururaja wrote: > Device tree support for tlv320aic3x CODEC driver Not really for the CODEC - this is a machine driver. > +- 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)>"; What do these different ops do - how would the user figure it out or if they're needed at all?
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH V2 5/6] ASoC: Davinci: machine: Add device tree binding Date: Mon, 27 Aug 2012 11:19:40 -0700 [thread overview] Message-ID: <20120827181939.GX4339@opensource.wolfsonmicro.com> (raw) In-Reply-To: <1346074004-22172-6-git-send-email-gururaja.hebbar@ti.com> On Mon, Aug 27, 2012 at 06:56:43PM +0530, Hebbar, Gururaja wrote: > Device tree support for tlv320aic3x CODEC driver Not really for the CODEC - this is a machine driver. > +- 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)>"; What do these different ops do - how would the user figure it out or if they're needed at all?
next prev parent reply other threads:[~2012-08-27 18:19 UTC|newest] Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-08-27 13:26 [PATCH V2 0/6] ARM/ASoC: Davinci: Add Device Tree Support Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 13:26 ` [PATCH V2 1/6] ASoC: davinci: davinci-pcm does not need to be a plaform_driver Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 18:12 ` Mark Brown 2012-08-27 18:12 ` Mark Brown 2012-08-29 6:25 ` Sergey Vlasov 2012-08-29 6:25 ` [alsa-devel] " Sergey Vlasov 2012-08-29 6:29 ` Hebbar, Gururaja 2012-08-29 6:29 ` [alsa-devel] " Hebbar, Gururaja 2012-08-27 13:26 ` [PATCH V2 2/6] ARM: Davinci: Remove references to davinci pcm Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 18:13 ` Mark Brown 2012-08-27 18:13 ` Mark Brown 2012-08-27 13:26 ` [PATCH V2 3/6] ASoC/ARM: Davinci: McASP: split asp header into platform and audio specific Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 18:13 ` Mark Brown 2012-08-27 18:13 ` Mark Brown 2012-08-27 13:26 ` [PATCH V2 4/6] ASoC: Davinci: McASP: add device tree support for McASP Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 18:08 ` Mark Brown 2012-08-27 18:08 ` Mark Brown 2012-08-27 18:13 ` Mark Brown 2012-08-27 18:13 ` Mark Brown 2012-08-27 13:26 ` [PATCH V2 5/6] ASoC: Davinci: machine: Add device tree binding Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 18:19 ` Mark Brown [this message] 2012-08-27 18:19 ` Mark Brown 2012-08-28 10:19 ` Hebbar, Gururaja 2012-08-28 10:19 ` Hebbar, Gururaja 2012-08-27 13:26 ` [PATCH V2 6/6] ASoC: tlv320aic3x: Add device tree bindings Hebbar, Gururaja 2012-08-27 13:26 ` Hebbar, Gururaja 2012-08-27 17:26 ` Mark Brown 2012-08-27 17:26 ` 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=20120827181939.GX4339@opensource.wolfsonmicro.com \ --to=broonie@opensource.wolfsonmicro.com \ --cc=alsa-devel@alsa-project.org \ --cc=alsa-user@lists.sourceforge.net \ --cc=davinci-linux-open-source@linux.davincidsp.com \ --cc=gururaja.hebbar@ti.com \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=lrg@ti.com \ --cc=nsekhar@ti.com \ --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: linkBe 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.