From: Lars-Peter Clausen <lars@metafoo.de>
To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Simon <horms@verge.net.au>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [PATCH] ASoC: ak4613: add single-end optional property for IN/OUT pins
Date: Fri, 13 Nov 2015 11:06:39 +0100 [thread overview]
Message-ID: <5645B62F.3020101@metafoo.de> (raw)
In-Reply-To: <87ziyiij30.wl%kuninori.morimoto.gx@renesas.com>
On 11/13/2015 06:12 AM, Kuninori Morimoto wrote:
> From: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
>
> ak4613 IN/OUT pin can be selected as differential/single-end.
> Differential is default, because it is register default settings.
>
> Signed-off-by: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>
> ---
> Documentation/devicetree/bindings/sound/ak4613.txt | 10 ++++++++
> sound/soc/codecs/ak4613.c | 29 ++++++++++++++++++++++
> 2 files changed, 39 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/sound/ak4613.txt b/Documentation/devicetree/bindings/sound/ak4613.txt
> index 15a9195..392b5b5 100644
> --- a/Documentation/devicetree/bindings/sound/ak4613.txt
> +++ b/Documentation/devicetree/bindings/sound/ak4613.txt
> @@ -7,6 +7,16 @@ Required properties:
> - compatible : "asahi-kasei,ak4613"
> - reg : The chip select number on the I2C bus
>
> +Optional properties:
> +- in1-single-end : Boolean. Indicate input / output pins are single-ended.
> +- in2-single-end rather than differential.
> +- out1-single-end
> +- out2-single-end
> +- out3-single-end
> +- out4-single-end
> +- out5-single-end
> +- out6-single-end
vendor prefix?
prev parent reply other threads:[~2015-11-13 10:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-13 5:12 [PATCH] ASoC: ak4613: add single-end optional property for IN/OUT pins Kuninori Morimoto
2015-11-13 10:06 ` Lars-Peter Clausen [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=5645B62F.3020101@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@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.