From: Nicolin Chen <nicoleotsuka@gmail.com>
To: Marco Felsch <m.felsch@pengutronix.de>
Cc: alsa-devel@alsa-project.org, Xiubo.Lee@gmail.com,
lgirdwood@gmail.com, timur@tabi.org, broonie@kernel.org,
kernel@pengutronix.de, fabio.estevam@nxp.com
Subject: Re: [PATCH] ASoC: imx-audmux: add RXFS/RXCLK defines for 6-wire connections
Date: Sat, 19 May 2018 23:10:43 -0700 [thread overview]
Message-ID: <20180520060954.GA3257@Asurada-CZ80> (raw)
In-Reply-To: <20180517142601.19587-1-m.felsch@pengutronix.de>
On Thu, May 17, 2018 at 04:26:01PM +0200, Marco Felsch wrote:
> From: Philipp Zabel <p.zabel@pengutronix.de>
>
> In asynchronous mode, a RxFS and RxClk connection needs to be made between
> two ports. Add a define for the bit to be set in the *SEL fields.
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Signed-off-by: Marco Felsch <m.felsch@pengutronix.de>
> ---
> include/dt-bindings/sound/fsl-imx-audmux.h | 4 ++++
> 1 file changed, 4 insertions(+)
>
> diff --git a/include/dt-bindings/sound/fsl-imx-audmux.h b/include/dt-bindings/sound/fsl-imx-audmux.h
> index 751fe1416f95..6120696abe63 100644
> --- a/include/dt-bindings/sound/fsl-imx-audmux.h
> +++ b/include/dt-bindings/sound/fsl-imx-audmux.h
> @@ -25,6 +25,10 @@
> #define MX51_AUDMUX_PORT6 5
> #define MX51_AUDMUX_PORT7 6
>
> +/* TFSEL/TCSEL/RFSEL/RCSEL can be sourced from Rx/Tx clocks on i.MX51/53/6Q */
It's actually not confined to 51/53/6Q -- 21 and 35 should
also have it according to their Reference Manuals.
> +#define IMX_AUDMUX_RXFS 0x8
> +#define IMX_AUDMUX_RXCLK 0x8
> +
> /* Register definitions for the i.MX21/27 Digital Audio Multiplexer */
> #define IMX_AUDMUX_V1_PCR_INMMASK(x) ((x) & 0xff)
> #define IMX_AUDMUX_V1_PCR_INMEN (1 << 8)
> --
> 2.17.0
>
prev parent reply other threads:[~2018-05-20 6:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 14:26 [PATCH] ASoC: imx-audmux: add RXFS/RXCLK defines for 6-wire connections Marco Felsch
2018-05-20 6:10 ` Nicolin Chen [this message]
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=20180520060954.GA3257@Asurada-CZ80 \
--to=nicoleotsuka@gmail.com \
--cc=Xiubo.Lee@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=lgirdwood@gmail.com \
--cc=m.felsch@pengutronix.de \
--cc=timur@tabi.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).