devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: quentin.schulz@theobroma-systems.com
Cc: thierry.reding@gmail.com, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, daniel@ffwll.ch,
	robh+dt@kernel.org, sam@ravnborg.org,
	dri-devel@lists.freedesktop.org,
	Quentin Schulz <foss+kernel@0leil.net>,
	airlied@linux.ie
Subject: Re: [PATCH 3/3] dt-bindings: ltk050h3146w: add compatible for LTK050H3148W-CTA6 variant
Date: Fri, 11 Feb 2022 07:30:41 -0600	[thread overview]
Message-ID: <YgZlASpL4uurqroZ@robh.at.kernel.org> (raw)
In-Reply-To: <20220131164723.714836-3-quentin.schulz@theobroma-systems.com>

On Mon, 31 Jan 2022 17:47:23 +0100, 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.
> 
> Cc: Quentin Schulz <foss+kernel@0leil.net>
> Signed-off-by: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> ---
>  .../devicetree/bindings/display/panel/leadtek,ltk050h3146w.yaml  | 1 +
>  1 file changed, 1 insertion(+)
> 

Acked-by: Rob Herring <robh@kernel.org>

  reply	other threads:[~2022-02-11 13:30 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 [this message]
2022-06-09  8:52   ` Paul Kocialkowski
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=YgZlASpL4uurqroZ@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=airlied@linux.ie \
    --cc=daniel@ffwll.ch \
    --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).