All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Daniel Glöckner" <dg@emlix.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Chris Zankel <chris@zankel.net>,
	alsa-devel@alsa-project.org, Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: S6000 ASoC drivers with multi-component
Date: Mon, 29 Nov 2010 11:34:03 +0100	[thread overview]
Message-ID: <4CF3819B.5040507@emlix.com> (raw)
In-Reply-To: <20101128120702.GA12683@opensource.wolfsonmicro.com>

On 11/28/2010 01:07 PM, Mark Brown wrote:
> I'm a little concerned that there have been no updates to the s6000
> audio drivers since the merge of multi-component ASoC (which is now in
> mainline and should be released as part of 2.6.37).  This was a very
> big and invasive update, and experience with other architectures has
> been that there's usually at least some typos that need fixing.  It'd be
> good to get some confirmation that the audio drivers have at least been
> tested with current mainline - if everything worked fine that's
> obviously excellent but it'd be good if someone could confirm that this
> is the case.

Oh dear, you killed Schrödinger's cat..

Yes there are some bugs in the s6000 ASoC code.
A missing semicolon at the end of s6000_i2s_dai, a lacking forward
declaration of s6000_soc_platform in the request_irq line, and a reference
to codec->snd_card which should probably be changed to codec->card->snd_card.

But trying to build a s6105 kernel from vanilla sources made me realize
two things:
1. Nobody ever tried to do that before as s6000 support has been merged
   incompletely and in some cases with merge errors (variant_irq_disable
   declaration, I2C_BOARD_INFO in struct platform_device[], clk framework
   missing completely).
2. Compiling Xtensa kernels in general is broken at least since 2.6.35-rc1
   because of e520c41085

So for now I could just compile-test the ASoC changes. Actually booting a
kernel will probably take more of my spare time..
Would you like to have patches for the found ASoC bugs now or do you prefer
waiting until I could make it work on hardware?

  Daniel


-- 
Dipl.-Math. Daniel Glöckner, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax -11, Bahnhofsallee 1b, 37081 Göttingen, Germany
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
Geschäftsführer: Dr. Uwe Kracke, Ust-IdNr.: DE 205 198 055

emlix - your embedded linux partner

  reply	other threads:[~2010-11-29 10:34 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-28 12:07 S6000 ASoC drivers with multi-component Mark Brown
2010-11-29 10:34 ` Daniel Glöckner [this message]
2010-11-29 10:42   ` Mark Brown
2010-11-30  0:00     ` [PATCH 1/3] s6000-i2s: fix compilation Daniel Glöckner
2010-11-30 11:21       ` Liam Girdwood
2010-11-30 11:26         ` Mark Brown
2010-11-30  0:00     ` [PATCH 2/3] s6000-pcm: " Daniel Glöckner
2010-11-30  0:00     ` [PATCH 3/3] s6105-ipcam: " Daniel Glöckner

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=4CF3819B.5040507@emlix.com \
    --to=dg@emlix.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=chris@zankel.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.