From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: noman pouigt <variksla@gmail.com>,
"jarkko.nikula@bitmer.com" <jarkko.nikula@bitmer.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"jslaby@suse.cz" <jslaby@suse.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
zonque@gmail.com
Subject: Re: audio mcbsp1 broken for beagleboard-xm -OMAP
Date: Fri, 20 Feb 2015 18:24:43 +0200 [thread overview]
Message-ID: <54E75FCB.8040906@ti.com> (raw)
In-Reply-To: <CAES_P+_LNczMuQsUW=ghJ-SQjLn_+AokDHfY4k+zmoFBb8cF0w@mail.gmail.com>
Hi,
On 02/20/2015 08:45 AM, noman pouigt wrote:
> Hello,
>
> I am trying to integrate max98090 codec with $subject board. I am
> running the mcBSP in slave mode as i have not changed the hw_parms for
> omap-twl4030.c file. With below changes i see wait_for_avail is
> getting stuck i.e. mcbsp is not getting any interrupt and nothing is
> playing.
I have tested the XM with twl4030 on linux-next and McBSP is working fine as
slave and master (I have a patch to add the McBSP master support for testing)
also.
>
> Kernel version:
> VERSION = 3
> PATCHLEVEL = 19
> SUBLEVEL = 0
> EXTRAVERSION =
> NAME = Diseased Newt
>
> Setup information:
> Using beagle board -xm and connected max98090 codec to mcbsp1 pins.
> Connected only 4 pins.
>
> Changed the omap-twl4030.c machine file as below to disable the twl4030:
> static struct snd_soc_dai_link omap_twl4030_dai_links[] = {
> {
> + .name = "max98090",
> + .stream_name = "max98090",
> .cpu_dai_name = "omap-mcbsp.1",
Hrm, mcbsp.1 is not in use by default on the board, 2 and 3 are the one which
is used by the omap-twl4030 driver.
> + .codec_dai_name = "HiFi",
> .platform_name = "omap-mcbsp.1",
> + .codec_name = "max98090.1-0010",
> .ops = &omap_twl4030_ops,
> },
>
> DTSI file change:arch/arm/boot/dts/omap3-beagle-xm.dts
>
> &i2c2 {
> clock-frequency = <400000>;
> +
> + max98090: max98090@10 {
> + compatible = "maxim,max98090";
> + reg = <0x10>;
> + };
> };
>
> omap/omap-twl4030.c
> added in hw_params below function to set internal oscillator for 98090
> for generating PLL for master clock.
> snd_soc_dai_set_sysclk(codec_dai, 26000000, 0, SND_SOC_CLOCK_IN);
>
> I am able to see that the cpu_dai is mapped with codec_dai and
> configuration is ok. kernel logs at https://ideone.com/oezNSj
>
> I think i don't need to configure the mcbsp1 pins right as it uses default.
I think you should check the pin mux for the McBSP1 pins. They might not set
to correct mode.
>
> Please guide me.I have tried IRC channel also but not getting the right folks.
>
> https://github.com/CircuitCo/BeagleBoard-xM-RevC/blob/master/BeagleBoard-xM_revC_SCH.pdf?raw=true
>
> Thanks,
>
--
Péter
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2015-02-20 16:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-20 6:45 audio mcbsp1 broken for beagleboard-xm -OMAP noman pouigt
2015-02-20 16:24 ` Peter Ujfalusi [this message]
2015-02-24 0:03 ` noman pouigt
2015-02-20 16:27 ` Peter Ujfalusi
2015-02-21 2:36 ` noman pouigt
2015-02-25 9:40 ` Peter Ujfalusi
2015-02-25 20:09 ` noman pouigt
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=54E75FCB.8040906@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=jarkko.nikula@bitmer.com \
--cc=jslaby@suse.cz \
--cc=variksla@gmail.com \
--cc=zonque@gmail.com \
/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.