From: festevam@gmail.com (Fabio Estevam)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] imx: dma: remove SDMA_IS_MERGED
Date: Wed, 1 Dec 2010 13:40:17 -0200 [thread overview]
Message-ID: <AANLkTimofVgY4M7U+aLA1RUz0a2LOmPUFr6bwcj1vcZw@mail.gmail.com> (raw)
In-Reply-To: <20101201111448.GF6017@pengutronix.de>
Hi Sascha,
On Wed, Dec 1, 2010 at 9:14 AM, Sascha Hauer <s.hauer@pengutronix.de> wrote:
...
> It seems the reason for the crash is that firmware_class registers in
> fs_initcall whereas the sdma driver uses it at subsys_initcall time.
> Solution is to either use module_init in the sdma driver or
> subsys_initcall in drivers/base/firmware_class.c.
>
> When given a firmware it works, when no firmware is given the kernel
> locks for some time because it waits for the firmware to appear which
> never happens. We should probably use request_firmware_nowait in the
> sdma driver.
>
> I put together a branch with sdma sound working on the babbage and
> mx35-3ds boards using mx3_defconfig/mx51_defconfig from this branch.
> The branch works with and without firmware with the mentioned wait time
> when the firmware is not available.
>
> BTW I changed the SDMA firmware repository to name the i.MX51 firmware
> *to3.bin instead of to1, because that's what it actually is.
>
> Sound support is a story with many frameworks and a lot of board
> specifics involved, but I hope we manage to sort this out for i.MX soon.
> Sorry for the inconvenience.
>
> It would be great if someone steps forward and mainlines this sgtl5000
> codec driver, that's currently the main showstopper for sound support on
> the Freescale boards.
Thanks a lot for setting up this branch. I can confirm that audio
works on MX51 Babbage on this branch.
I will check internally if someone is willing to mainline sgtl5000.
Thanks,
Fabio Estevam
next prev parent reply other threads:[~2010-12-01 15:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-24 19:29 [PATCH] imx: dma: remove SDMA_IS_MERGED Fabio Estevam
2010-11-24 19:44 ` Uwe Kleine-König
2010-11-24 20:07 ` Fabio Estevam
2010-11-24 20:18 ` Uwe Kleine-König
2010-11-24 21:42 ` Fabio Estevam
2010-11-24 21:58 ` Uwe Kleine-König
2010-11-24 22:57 ` Richard Zhao
2010-11-25 9:13 ` Sascha Hauer
2010-11-25 12:09 ` Fabio Estevam
2010-11-25 12:29 ` Arnaud Patard (Rtp)
2010-11-25 12:32 ` Fabio Estevam
2010-11-25 13:58 ` Uwe Kleine-König
2010-11-29 21:24 ` Sascha Hauer
2010-11-29 22:27 ` Fabio Estevam
2010-12-01 11:14 ` Sascha Hauer
2010-12-01 11:35 ` Arnaud Patard (Rtp)
2010-12-01 15:41 ` Sascha Hauer
2010-12-01 23:44 ` Arnaud Patard (Rtp)
2010-12-02 12:14 ` Sascha Hauer
2010-12-02 15:36 ` Fabio Estevam
2010-12-01 15:40 ` Fabio Estevam [this message]
2010-12-03 13:00 ` Arnaud Patard (Rtp)
2010-12-03 19:49 ` Fabio Estevam
2010-11-25 9:07 ` Sascha Hauer
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=AANLkTimofVgY4M7U+aLA1RUz0a2LOmPUFr6bwcj1vcZw@mail.gmail.com \
--to=festevam@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).