Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Shubhi Garg <shgarg@nvidia.com>, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] arm64: tegra: Sort properties more logically
Date: Fri, 9 Jun 2023 12:04:38 +0100	[thread overview]
Message-ID: <a268d4bc-74d1-c98c-51f1-8a183a405620@nvidia.com> (raw)
In-Reply-To: <20230609105543.3730161-1-thierry.reding@gmail.com>


On 09/06/2023 11:55, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
> 
> We typically sort the "compatible" property first because it defines
> what the remainder of the properties can be. For the sound node on the
> Jetson AGX Orin this wasn't done, so fix that up.
> 
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
>   arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts | 3 +--
>   1 file changed, 1 insertion(+), 2 deletions(-)
> 
> diff --git a/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts b/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts
> index ac64dac287de..e499010fc673 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts
> +++ b/arch/arm64/boot/dts/nvidia/tegra234-p3737-0000+p3701-0000.dts
> @@ -2345,9 +2345,8 @@ serial {
>   	};
>   
>   	sound {
> -		status = "okay";
> -
>   		compatible = "nvidia,tegra186-audio-graph-card";
> +		status = "okay";
>   
>   		dais = /* ADMAIF (FE) Ports */
>   		       <&admaif0_port>, <&admaif1_port>, <&admaif2_port>, <&admaif3_port>,


Acked-by: Jon Hunter <jonathanh@nvidia.com>

Jon
-- 
nvpublic

      parent reply	other threads:[~2023-06-09 11:05 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-09 10:55 [PATCH 1/2] arm64: tegra: Sort properties more logically Thierry Reding
2023-06-09 10:55 ` [PATCH 2/2] arm64: tegra: Add a few blank lines for better readability Thierry Reding
2023-06-09 11:04   ` Jon Hunter
2023-06-09 11:04 ` Jon Hunter [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=a268d4bc-74d1-c98c-51f1-8a183a405620@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=linux-tegra@vger.kernel.org \
    --cc=shgarg@nvidia.com \
    --cc=thierry.reding@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox