From: jassisinghbrar@gmail.com (jassi brar)
To: linux-arm-kernel@lists.infradead.org
Subject: Samsung: New driver for AC97 controllers
Date: Tue, 26 Jan 2010 15:16:54 +0900 [thread overview]
Message-ID: <1b68c6791001252216t5a91b9a9t92edb5e515ddd434@mail.gmail.com> (raw)
In-Reply-To: <1264485091-13750-1-git-send-email-jassisinghbrar@gmail.com>
On Tue, Jan 26, 2010 at 2:51 PM, <jassisinghbrar@gmail.com> wrote:
> From: Jassi Brar <jassi.brar@samsung.com>
>
> Hi,
> ?I am going to submit new driver for the AC97-ver-2.0 controllers found in
> Samsung SoCs. The driver is named generic s3c-ac97.c
> ?The driver has been tested for on s3c64xx and newer SoCs and is confirmed
> to support Playback/Capture and VRA.
>
> ?A machine driver, for SMDKs with wm9713 as AC97 codec attached, has also
> been added. The driver is generic enough to be used as such with newer SoCs.
>
> ?The controller driver patch is meant for Mark Brown's for-2.6.34
> ?Other patches apply cleanly against the Ben Dooks' next-samsung
>
> ?The s3c-ac97.c is meant to replace s3c2443-ac97.c after someone confirms
> Playback/Capture to work fine. My smdk2443 seems to not play any sound though
> the DAI link is establised and the codec detected fine.
I forgot to mention that that's the status with new s3c-ac97.c as well as
old s3c2443-ac97.c .... now read on please.
> So, my opinion is that the new driver is atleast as good as the old one.
> If that is good enough, I have patches ready that switch the only two users
> of s3c2443-ac97.c(smdk2443 and ln2440sbc) to use this new driver.
>
> Regards.
> --
> To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at ?http://vger.kernel.org/majordomo-info.html
>
prev parent reply other threads:[~2010-01-26 6:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-26 5:51 Samsung: New driver for AC97 controllers jassisinghbrar at gmail.com
2010-01-26 6:16 ` jassi brar [this message]
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=1b68c6791001252216t5a91b9a9t92edb5e515ddd434@mail.gmail.com \
--to=jassisinghbrar@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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).