From: Conor Dooley <conor@kernel.org>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Jonathan Hunter <jonathanh@nvidia.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Svyatoslav Ryhel <clamor95@gmail.com>,
devicetree@vger.kernel.org, linux-tegra@vger.kernel.org
Subject: Re: [PATCH 1/2] dt-bindings: display: tegra: Document Tegra124 MIPI
Date: Fri, 7 Mar 2025 15:47:07 +0000 [thread overview]
Message-ID: <20250307-oops-anemia-814894c038f6@spud> (raw)
In-Reply-To: <20250306175931.2028613-1-thierry.reding@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1060 bytes --]
On Thu, Mar 06, 2025 at 06:59:30PM +0100, Thierry Reding wrote:
> From: Thierry Reding <treding@nvidia.com>
>
> The Tegra124 MIPI hardware block is very similar to the one found on
> earlier chip generations. Add a corresponding compatible string.
>
> Signed-off-by: Thierry Reding <treding@nvidia.com>
> ---
> .../devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml
> index f448624dd779..193ddb105283 100644
> --- a/Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml
> +++ b/Documentation/devicetree/bindings/display/tegra/nvidia,tegra114-mipi.yaml
> @@ -17,6 +17,7 @@ properties:
> compatible:
> enum:
> - nvidia,tegra114-mipi
> + - nvidia,tegra124-mipi
> - nvidia,tegra210-mipi
> - nvidia,tegra186-mipi
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
prev parent reply other threads:[~2025-03-07 15:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 17:59 [PATCH 1/2] dt-bindings: display: tegra: Document Tegra124 MIPI Thierry Reding
2025-03-06 17:59 ` [PATCH 2/2] dt-bindings: Document Tegra114 HDA support Thierry Reding
2025-03-07 15:43 ` Conor Dooley
2025-03-07 15:47 ` Conor Dooley [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=20250307-oops-anemia-814894c038f6@spud \
--to=conor@kernel.org \
--cc=clamor95@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).