From: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
To: quentin.schulz@theobroma-systems.com
Cc: devicetree@vger.kernel.org, airlied@linux.ie,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
Quentin Schulz <foss+kernel@0leil.net>,
robh+dt@kernel.org, thierry.reding@gmail.com, sam@ravnborg.org
Subject: Re: [PATCH 3/3] dt-bindings: ltk050h3146w: add compatible for LTK050H3148W-CTA6 variant
Date: Thu, 9 Jun 2022 10:52:24 +0200 [thread overview]
Message-ID: <YqG0yL7nnUkTrnN1@aptenodytes> (raw)
In-Reply-To: <20220131164723.714836-3-quentin.schulz@theobroma-systems.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
Hi,
On Mon 31 Jan 22, 17:47, quentin.schulz@theobroma-systems.com wrote:
> From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
>
> The LTK050H3148W-CTA6 is a 5.0" 720x1280 DSI display, whose driving
> controller is a Himax HX8394-F, slightly different from LTK050H3146W by
> its init sequence, mode details and mode flags.
No difference needed in the binding at all then, I suppose.
> Cc: Quentin Schulz <foss+kernel@0leil.net>
> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
Reviewed-by: Paul Kocialkowski <paul.kocialkowski@bootlin.com>
Cheers,
Paul
> ---
> .../devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/Documentation/devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml b/Documentation/devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml
> index 3715882b63b6..63d2a00348e9 100644
> --- a/Documentation/devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml
> @@ -17,6 +17,7 @@ properties:
> enum:
> - leadtek,ltk050h3146w
> - leadtek,ltk050h3146w-a2
> + - leadtek,ltk050h3148w
> reg: true
> backlight: true
> reset-gpios: true
> --
> 2.34.1
>
--
Paul Kocialkowski, Bootlin
Embedded Linux and kernel engineering
https://bootlin.com
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-06-09 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 16:47 [PATCH 1/3] drm/panel: ltk050h3146w: add mipi_dsi_device.mode_flags to of_match_data quentin.schulz
2022-01-31 16:47 ` [PATCH 2/3] drm/panel: ltk050h3146w: add support for Leadtek LTK050H3148W-CTA6 variant quentin.schulz
2022-06-09 8:51 ` Paul Kocialkowski
2022-01-31 16:47 ` [PATCH 3/3] dt-bindings: ltk050h3146w: add compatible for " quentin.schulz
2022-02-11 13:30 ` Rob Herring
2022-06-09 8:52 ` Paul Kocialkowski [this message]
2022-05-03 15:23 ` [PATCH 1/3] drm/panel: ltk050h3146w: add mipi_dsi_device.mode_flags to of_match_data Quentin Schulz
2022-06-09 8:50 ` Paul Kocialkowski
2023-10-10 16:54 ` Heiko Stuebner
2023-10-10 16:55 ` Heiko Stübner
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=YqG0yL7nnUkTrnN1@aptenodytes \
--to=paul.kocialkowski@bootlin.com \
--cc=airlied@linux.ie \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=foss+kernel@0leil.net \
--cc=linux-kernel@vger.kernel.org \
--cc=quentin.schulz@theobroma-systems.com \
--cc=robh+dt@kernel.org \
--cc=sam@ravnborg.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).