From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Marek Belisko <marek.belisko@open-nandra.com>
Cc: alsa-devel@alsa-project.org, tiwai@suse.de,
broonie@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org, ben-linux@fluff.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] arm: mini2440: Fix uda134x codec problem.
Date: Fri, 11 Mar 2011 12:14:11 +0000 [thread overview]
Message-ID: <1299845651.3394.47.camel@odin> (raw)
In-Reply-To: <1299703580-3957-1-git-send-email-marek.belisko@open-nandra.com>
On Wed, 2011-03-09 at 21:46 +0100, Marek Belisko wrote:
> ASoC audio for mini2440 platform in current kenrel doesn't work.
> First problem is samsung_asoc_dma device is missing in initialization.
> Next problem is with codec. Codec is initialized but never probed
> because no platform_device exist for codec driver. It leads to errors
> during codec binding to asoc dai. Next problem was platform data which
> was passed from board to asoc main driver but not passed to codec when
> called codec_soc_probe().
>
> Following patch should fix issues. But not sure if in correct way.
> Please review.
>
> Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
Acked-by: Liam Girdwood <lrg@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: lrg@slimlogic.co.uk (Liam Girdwood)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RFC] arm: mini2440: Fix uda134x codec problem.
Date: Fri, 11 Mar 2011 12:14:11 +0000 [thread overview]
Message-ID: <1299845651.3394.47.camel@odin> (raw)
In-Reply-To: <1299703580-3957-1-git-send-email-marek.belisko@open-nandra.com>
On Wed, 2011-03-09 at 21:46 +0100, Marek Belisko wrote:
> ASoC audio for mini2440 platform in current kenrel doesn't work.
> First problem is samsung_asoc_dma device is missing in initialization.
> Next problem is with codec. Codec is initialized but never probed
> because no platform_device exist for codec driver. It leads to errors
> during codec binding to asoc dai. Next problem was platform data which
> was passed from board to asoc main driver but not passed to codec when
> called codec_soc_probe().
>
> Following patch should fix issues. But not sure if in correct way.
> Please review.
>
> Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
Acked-by: Liam Girdwood <lrg@ti.com>
WARNING: multiple messages have this Message-ID (diff)
From: Liam Girdwood <lrg@slimlogic.co.uk>
To: Marek Belisko <marek.belisko@open-nandra.com>
Cc: ben-linux@fluff.org, perex@perex.cz, tiwai@suse.de,
alsa-devel@alsa-project.org, broonie@opensource.wolfsonmicro.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC] arm: mini2440: Fix uda134x codec problem.
Date: Fri, 11 Mar 2011 12:14:11 +0000 [thread overview]
Message-ID: <1299845651.3394.47.camel@odin> (raw)
In-Reply-To: <1299703580-3957-1-git-send-email-marek.belisko@open-nandra.com>
On Wed, 2011-03-09 at 21:46 +0100, Marek Belisko wrote:
> ASoC audio for mini2440 platform in current kenrel doesn't work.
> First problem is samsung_asoc_dma device is missing in initialization.
> Next problem is with codec. Codec is initialized but never probed
> because no platform_device exist for codec driver. It leads to errors
> during codec binding to asoc dai. Next problem was platform data which
> was passed from board to asoc main driver but not passed to codec when
> called codec_soc_probe().
>
> Following patch should fix issues. But not sure if in correct way.
> Please review.
>
> Signed-off-by: Marek Belisko <marek.belisko@open-nandra.com>
Acked-by: Liam Girdwood <lrg@ti.com>
next prev parent reply other threads:[~2011-03-11 12:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-09 20:46 [PATCH RFC] arm: mini2440: Fix uda134x codec problem Marek Belisko
2011-03-09 20:46 ` Marek Belisko
2011-03-11 12:14 ` Liam Girdwood [this message]
2011-03-11 12:14 ` Liam Girdwood
2011-03-11 12:14 ` Liam Girdwood
2011-03-11 12:17 ` Mark Brown
2011-03-11 12:17 ` Mark Brown
2011-03-11 12:17 ` Mark Brown
2011-03-11 12:23 ` Belisko Marek
2011-03-11 12:23 ` Belisko Marek
2011-03-11 12:26 ` Mark Brown
2011-03-11 12:26 ` Mark Brown
2011-03-11 12:26 ` Mark Brown
2011-03-21 23:17 ` Ben Dooks
2011-03-21 23:17 ` Ben Dooks
2011-03-21 23:17 ` Ben Dooks
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=1299845651.3394.47.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=ben-linux@fluff.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marek.belisko@open-nandra.com \
--cc=tiwai@suse.de \
/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.