All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rajeev kumar <rajeev-dlh.kumar@st.com>
To: Rajeev kumar <rajeev-dlh.kumar@st.com>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
	"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
	Mark Brown <broonie@opensource.wolfsonmicro.com>,
	"lrg@slimlogic.co.uk" <lrg@slimlogic.co.uk>
Subject: Re: [PATCH V2 7/9] sound:asoc: Add support for SPEAr ASoC machine driver.
Date: Wed, 27 Jun 2012 10:07:04 +0530	[thread overview]
Message-ID: <4FEA8DF0.70107@st.com> (raw)
In-Reply-To: <4FE83D3E.1070900@st.com>

Hello Mark,

On 6/25/2012 3:58 PM, Rajeev kumar wrote:
>> I'd expect to see an of_match_table in the device too given that you're
>> parsing OF compatible data.  Given how simple this is I wonder if you
>> can instead add DT support to the simple-card driver which Morimoto-san
>> recently contributed rather than adding a new driver?
>>

This will completely eliminate m/c driver. Am I correct ?

>
> I am not well-versed with device-tree framework. It will take me some
> time to study and incorporate the changes. I will get back on this point
> as soon as I finish the same.
>


> In the meanwhile can I send the V3 of rest patches which is not applied,
> namely
>
> 1. [PATCH V2 1/9] sound:asoc: Add support for spdif in Audio Codec.
> 2. [PATCH V2 2/9] sound:asoc: Add support for STA529 Audio Codec.
> 3. [PATCH V2 6/9] sound:asoc:spdif_out: Add spdif out support

Can I send above patches.

Best Regards
Rajeev

  reply	other threads:[~2012-06-27  5:08 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-21 10:24 [PATCH V2 0/9] Add ASoC drivers for SPEAr platform & I2S driver for Designware module Rajeev Kumar
2012-06-21 10:24 ` [PATCH V2 1/9] sound:asoc: Add support for spdif in Audio Codec Rajeev Kumar
2012-06-22  9:21   ` Mark Brown
2012-06-22  9:44     ` Rajeev kumar
2012-06-22  9:49       ` Mark Brown
2012-06-22  9:54         ` Rajeev kumar
2012-06-21 10:24 ` [PATCH V2 2/9] sound:asoc: Add support for STA529 " Rajeev Kumar
2012-06-21 12:25   ` Mark Brown
2012-06-22  6:26     ` Rajeev kumar
2012-06-22  8:49       ` Mark Brown
2012-06-21 10:24 ` [PATCH V2 3/9] sound:asoc: Add support for synopsys i2s controller as per ASoC framework Rajeev Kumar
2012-06-22  9:25   ` Mark Brown
2012-06-22  9:43     ` Rajeev kumar
2012-06-21 10:24 ` [PATCH V2 4/9] sound:asoc: Add support for SPEAr ASoC pcm layer Rajeev Kumar
2012-06-22  9:28   ` Mark Brown
2012-06-22  9:37     ` Rajeev kumar
2012-06-21 10:24 ` [PATCH V2 5/9] sound:asoc:spdif_in: Add spdif IN support Rajeev Kumar
2012-06-23 10:55   ` Mark Brown
2012-06-21 10:24 ` [PATCH V2 6/9] sound:asoc:spdif_out: Add spdif out support Rajeev Kumar
2012-06-23 10:56   ` Mark Brown
2012-06-21 10:24 ` [PATCH V2 7/9] sound:asoc: Add support for SPEAr ASoC machine driver Rajeev Kumar
2012-06-23 11:01   ` Mark Brown
2012-06-25 10:28     ` Rajeev kumar
2012-06-27  4:37       ` Rajeev kumar [this message]
2012-06-27 11:12         ` Mark Brown
2012-06-21 10:24 ` [PATCH V2 8/9] sound:asoc: Add Kconfig and Makefile to support SPEAr audio driver Rajeev Kumar
2012-06-21 10:24 ` [PATCH V2 9/9] sound:asoc: Update Kconfig and Makefile(sound/soc/) to support SPEAr audio Rajeev Kumar

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=4FEA8DF0.70107@st.com \
    --to=rajeev-dlh.kumar@st.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lrg@slimlogic.co.uk \
    --cc=tiwai@suse.de \
    /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 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.