From: rajeev <rajeev-dlh.kumar@st.com>
To: Takashi Iwai <tiwai@suse.de>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Jaroslav Kysela <perex@perex.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: RFC: ST specific ASoC sound driver
Date: Wed, 16 Mar 2011 16:34:08 +0530 [thread overview]
Message-ID: <4D809928.2000905@st.com> (raw)
Hi,
I have developed a ASoC sound driver for a ST specific platform (SPEAr).
This module actually uses the Designware (Synopsys) "dw_apb_i2s_db" IP
+ some ST specific glue logic on top of it.
Now I am confused as to whether I should submit a single patch for
the SPEAr ASoC driver or should I try to break the driver such that
the Designware and glue logic parts are handled separately (which given
the current shape of design seems improbable)
Any pointers on the same will be highly appreciated.
Best Regards
Rajeev
next reply other threads:[~2011-03-16 11:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-16 11:04 rajeev [this message]
2011-03-16 11:22 ` RFC: ST specific ASoC sound driver 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=4D809928.2000905@st.com \
--to=rajeev-dlh.kumar@st.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--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 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).