From: jassi brar <jassisinghbrar@gmail.com>
To: alsa-devel@alsa-project.org
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
Ben Dooks <ben-linux@fluff.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: ASoC: SAMSUNG: About I2S_v4 support
Date: Wed, 3 Mar 2010 17:32:13 +0900 [thread overview]
Message-ID: <1b68c6791003030032n7de8a0d8t5395a0a260d92b19@mail.gmail.com> (raw)
Hello,
Could we please reach some agreement about the support of I2Sv4 block of
S3C64XX and newer SoCs?
Kindly express your opinion.
Otherwise, I am planning to re-factor(as and if needed) s3c-i2s-v2.c,
s3c2412-i2s.c and s3c64xx-i2s.c
and add a new s3c-i2s-v4.c to handle I2S_v4 controllers.
Kindly ACK/NAK this idea if you are busy with other stuff and I am to
start working on the issue.
Thanks.
next reply other threads:[~2010-03-03 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-03 8:32 jassi brar [this message]
2010-03-03 9:54 ` ASoC: SAMSUNG: About I2S_v4 support Mark Brown
2010-03-03 11:10 ` jassi brar
2010-03-03 11:21 ` Mark Brown
2010-03-03 12:53 ` jassi brar
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=1b68c6791003030032n7de8a0d8t5395a0a260d92b19@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@slimlogic.co.uk \
/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).