linux-omap.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: Andreas Kemnade <andreas@kemnade.info>
Cc: linux-omap@vger.kernel.org
Subject: Re: receiving data from mcbsp1 in master mode
Date: Thu, 23 Aug 2012 11:47:59 +0300	[thread overview]
Message-ID: <5035EE3F.9000903@ti.com> (raw)
In-Reply-To: <20120822221942.2ebb4fd3@kemnade.info>

On 08/22/2012 11:19 PM, Andreas Kemnade wrote:
> if I understand the TRM correctly, according to Figure 21-26 in chapter 21.4.2.3.
> if GSYNC is set, the receiver uses the signal from the sample rate generator,
> so CLKX does not need to be the CLKR source.
> But I tried also with the DEVCONF0 MCBSP1_CLKR bit as you proposed.
> I tried
>  snd_soc_dai_set_sysclk(cpu_dai, OMAP_MCBSP_CLKR_SRC_CLKX, 0,
>                                      SND_SOC_CLOCK_OUT);
>  snd_soc_dai_set_sysclk(cpu_dai, OMAP_MCBSP_FSR_SRC_FSX, 0,
>                                      SND_SOC_CLOCK_OUT);

There is an issue with the 6pin mux code, try to add this patch:
http://mailman.alsa-project.org/pipermail/alsa-devel/2012-August/054041.html

>  That is why I send you my patch about that mux settings. But I had no success.
> The CLKX as CLKR source and FSX as FSR source setting I have only seen when
> mcbsp1 is used in slave mode. If you know any working code which uses mcbsp1 in
> master mode then let me know.

No, I don't have board which uses McBSP1.

-- 
Péter
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-08-23  8:48 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-21  5:42 receiving data from mcbsp1 in master mode Andreas Kemnade
2012-08-21 13:42 ` Peter Ujfalusi
2012-08-22 20:19   ` Andreas Kemnade
2012-08-23  8:47     ` Peter Ujfalusi [this message]
2012-08-23  9:32       ` Andreas Kemnade

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=5035EE3F.9000903@ti.com \
    --to=peter.ujfalusi@ti.com \
    --cc=andreas@kemnade.info \
    --cc=linux-omap@vger.kernel.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).