From: Mark Brown <broonie@opensource.wolfsonmicro.com>
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:54:20 +0000 [thread overview]
Message-ID: <20100224175419.GI9018@sirena.org.uk> (raw)
In-Reply-To: <C171323BB93CB94897E300CBB6D4537F1D94251A@CLMSG-01.ad.cirrus.com>
On Wed, Feb 24, 2010 at 11:43:41AM -0600, Austin, Brian wrote:
> 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
Yes, it's entirely normal to submit CODEC drivers that aren't referenced
by any machine drivers in mainline - please just go ahead and do this.
> soc-audio soc-audio: RXEN: Invalid MODE in IISMOD
...
> It seems that the S3C2412 I2S is not setup correctly for my platform.
It'd probably be easier for folks to help if you post your machine
driver...
next prev parent reply other threads:[~2010-02-24 17:54 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 [this message]
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
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=20100224175419.GI9018@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--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