From: Lauri Hintsala <lauri.hintsala@bluegiga.com>
To: Dong Aisheng <b29396@freescale.com>
Cc: alsa-devel@alsa-project.org, linux-arm-kernel@lists.infradead.org
Subject: MXS: How to configure SGTL5000 ASoC as master?
Date: Tue, 10 Jan 2012 08:19:36 +0200 [thread overview]
Message-ID: <4F0BD878.40508@bluegiga.com> (raw)
Hi,
SGTL5000 ASoC is hard coded to be slave in sound/soc/mxs/mxs-sgtl5000.c.
In our HW design mclk of ASoC is sourced from external oscillator.
Because of our design ASoC should be configured as master. In that case
master clock of SAIF should be disabled.
Is there any plan to have configuration for mxs-sgtl5000 driver? What is
preferred way to solve this issue?
BR,
Lauri Hintsala
p.s. I resent this mail because I wasn't subscriber of alsa-devel
mailing list.
WARNING: multiple messages have this Message-ID (diff)
From: lauri.hintsala@bluegiga.com (Lauri Hintsala)
To: linux-arm-kernel@lists.infradead.org
Subject: MXS: How to configure SGTL5000 ASoC as master?
Date: Tue, 10 Jan 2012 08:19:36 +0200 [thread overview]
Message-ID: <4F0BD878.40508@bluegiga.com> (raw)
Hi,
SGTL5000 ASoC is hard coded to be slave in sound/soc/mxs/mxs-sgtl5000.c.
In our HW design mclk of ASoC is sourced from external oscillator.
Because of our design ASoC should be configured as master. In that case
master clock of SAIF should be disabled.
Is there any plan to have configuration for mxs-sgtl5000 driver? What is
preferred way to solve this issue?
BR,
Lauri Hintsala
p.s. I resent this mail because I wasn't subscriber of alsa-devel
mailing list.
next reply other threads:[~2012-01-10 6:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-10 6:19 Lauri Hintsala [this message]
2012-01-10 6:19 ` MXS: How to configure SGTL5000 ASoC as master? Lauri Hintsala
2012-01-10 6:43 ` Dong Aisheng-B29396
2012-01-10 6:43 ` Dong Aisheng-B29396
2012-01-10 13:57 ` Lauri Hintsala
2012-01-10 13:57 ` Lauri Hintsala
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=4F0BD878.40508@bluegiga.com \
--to=lauri.hintsala@bluegiga.com \
--cc=alsa-devel@alsa-project.org \
--cc=b29396@freescale.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 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.