public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/3] sound: tegra: Add the binding file for tegra-audio
Date: Wed, 24 Apr 2019 10:15:17 +0100	[thread overview]
Message-ID: <66146192-e453-02b3-dc88-e9496cfb3bc1@nvidia.com> (raw)
In-Reply-To: <20190424035625.57087-2-sjg@chromium.org>


On 24/04/2019 04:56, Simon Glass wrote:
> This file was missed when adding the sound driver to U-Boot. Bring it in
> from Linux 5.0.
> 
> Signed-off-by: Simon Glass <sjg@chromium.org>
> ---
> 
>  .../sound/nvidia,tegra-audio-max98090.txt     | 53 +++++++++++++++++++
>  1 file changed, 53 insertions(+)
>  create mode 100644 doc/device-tree-bindings/sound/nvidia,tegra-audio-max98090.txt
> 
> diff --git a/doc/device-tree-bindings/sound/nvidia,tegra-audio-max98090.txt b/doc/device-tree-bindings/sound/nvidia,tegra-audio-max98090.txt
> new file mode 100644
> index 00000000000..c3495beba35
> --- /dev/null
> +++ b/doc/device-tree-bindings/sound/nvidia,tegra-audio-max98090.txt
> @@ -0,0 +1,53 @@
> +NVIDIA Tegra audio complex, with MAX98090 CODEC

Does this work for all Tegra chips? I have noticed in some of our kernel
binding docs we don't really say specifically what Tegra devices this is
applicable for. If this is only verified for Tegra124 then it could be
worth mentioning that.

> +
> +Required properties:
> +- compatible : "nvidia,tegra-audio-max98090"
> +- clocks : Must contain an entry for each entry in clock-names.
> +  See ../clocks/clock-bindings.txt for details.
> +- clock-names : Must include the following entries:
> +  - pll_a
> +  - pll_a_out0
> +  - mclk (The Tegra cdev1/extern1 clock, which feeds the CODEC's mclk)
> +- nvidia,model : The user-visible name of this sound complex.
> +- nvidia,audio-routing : A list of the connections between audio components.
> +  Each entry is a pair of strings, the first being the connection's sink,
> +  the second being the connection's source. Valid names for sources and
> +  sinks are the MAX98090's pins (as documented in its binding), and the jacks
> +  on the board:
> +
> +  * Headphones
> +  * Speakers
> +  * Mic Jack
> +  * Int Mic

I don't see 'Int Mic' used anywhere in the example. Is this really a
physical jack?

> +
> +- nvidia,i2s-controller : The phandle of the Tegra I2S controller that's
> +  connected to the CODEC.
> +- nvidia,audio-codec : The phandle of the MAX98090 audio codec.
> +
> +Optional properties:
> +- nvidia,hp-det-gpios : The GPIO that detect headphones are plugged in
> +- nvidia,mic-det-gpios : The GPIO that detect microphones are plugged in
> +
> +Example:
> +
> +sound {
> +	compatible = "nvidia,tegra-audio-max98090-venice2",
> +		     "nvidia,tegra-audio-max98090";
> +	nvidia,model = "NVIDIA Tegra Venice2";
> +
> +	nvidia,audio-routing =
> +		"Headphones", "HPR",
> +		"Headphones", "HPL",
> +		"Speakers", "SPKR",
> +		"Speakers", "SPKL",
> +		"Mic Jack", "MICBIAS",
> +		"IN34", "Mic Jack";
> +
> +	nvidia,i2s-controller = <&tegra_i2s1>;
> +	nvidia,audio-codec = <&acodec>;
> +
> +	clocks = <&tegra_car TEGRA124_CLK_PLL_A>,
> +		 <&tegra_car TEGRA124_CLK_PLL_A_OUT0>,
> +		 <&tegra_car TEGRA124_CLK_EXTERN1>;
> +	clock-names = "pll_a", "pll_a_out0", "mclk";
> +};
> 

Otherwise LGTM.

Cheers
Jon

-- 
nvpublic

  reply	other threads:[~2019-04-24  9:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-24  3:56 [U-Boot] [PATCH 1/3] sound: snow: Add the binding file for snow Simon Glass
2019-04-24  3:56 ` [U-Boot] [PATCH 2/3] sound: tegra: Add the binding file for tegra-audio Simon Glass
2019-04-24  9:15   ` Jon Hunter [this message]
2019-04-25  1:11     ` Simon Glass
2019-04-25  8:48       ` Jon Hunter
2019-04-24  3:56 ` [U-Boot] [PATCH 3/3] sound: Add codec enable to the sound bindings Simon Glass

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=66146192-e453-02b3-dc88-e9496cfb3bc1@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=u-boot@lists.denx.de \
    /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