From: Liam Girdwood <lrg@slimlogic.co.uk>
To: "Austin, Brian" <Brian.Austin@cirrus.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: issues porting codec to s3c2443
Date: Wed, 24 Feb 2010 17:57:54 +0000 [thread overview]
Message-ID: <1267034274.3274.595.camel@odin> (raw)
In-Reply-To: <C171323BB93CB94897E300CBB6D4537F1D94251A@CLMSG-01.ad.cirrus.com>
On Wed, 2010-02-24 at 11:43 -0600, Austin, Brian wrote:
> Hello,
>
>
>
> I have forward ported the CS42L52 from 2.6.26.2 to the current asoc git
> tree. The codec and smdk2443-cs42l52 drivers load correctly, at least I
> think so, and would like to submit the CS42L52 driver but am having some
> issues with s3c2412-i2s. From my previous kernel version to the latest
> there has been significant changes to the S3C architecture and I pretty
> sure that I am missing something because of that. The question is, is
> it ok to submit the codec standalone and have someone look at it to make
> sure I made the correct changes. No compiler warnings occur. My port
> was based off of the WM8750 if that helps any
>
>
>
> Here is the output from my SMDK2443 Simtec
>
>
>
> Advanced Linux Sound Architecture Driver Version 1.0.18a.
>
> No device for DAI CS42L52
>
> No device for DAI s3c2412-i2s
>
> SMDK2443 cs42l52 ALSA SoC driver ver1.1 10/2008
>
> soc-audio soc-audio: RXEN: Invalid MODE in IISMOD
>
> CS42L52: Cirrus Logic ALSA SoC codec cs42l52 driver verison 1.1 10/2008
>
> ALSA device list:
>
> No soundcards found.
>
>
>
> It seems that the S3C2412 I2S is not setup correctly for my platform.
>
Please do send your codec and machine drivers to the list. This will
make it easier to debug.
Liam
--
Freelance Developer, SlimLogic Ltd
ASoC and Voltage Regulator Maintainer.
http://www.slimlogic.co.uk
prev parent reply other threads:[~2010-02-24 17:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 17:43 issues porting codec to s3c2443 Austin, Brian
2010-02-24 17:54 ` Mark Brown
2010-02-25 22:10 ` Brian Austin
2010-02-25 23:09 ` Mark Brown
2010-02-25 23:48 ` Brian Austin
2010-02-25 23:25 ` Mark Brown
2010-02-24 17:57 ` Liam Girdwood [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=1267034274.3274.595.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=Brian.Austin@cirrus.com \
--cc=alsa-devel@alsa-project.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