From: "Heiko Stübner" <heiko@sntech.de>
To: quentin.schulz@theobroma-systems.com
Cc: thierry.reding@gmail.com, airlied@linux.ie, sam@ravnborg.org,
robh+dt@kernel.org, dri-devel@lists.freedesktop.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Quentin Schulz <foss+kernel@0leil.net>,
daniel@ffwll.ch
Subject: Re: [PATCH 1/3] drm/panel: ltk050h3146w: add mipi_dsi_device.mode_flags to of_match_data
Date: Tue, 10 Oct 2023 18:55:42 +0200 [thread overview]
Message-ID: <2369051.yKrmzQ4Hd0@diego> (raw)
In-Reply-To: <169695678310.350877.5388571923561270631.b4-ty@sntech.de>
Am Dienstag, 10. Oktober 2023, 18:54:11 CEST schrieb Heiko Stuebner:
> On Mon, 31 Jan 2022 17:47:21 +0100, quentin.schulz@theobroma-systems.com wrote:
> > From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> >
> > To prepare for a new display to be supported by this driver which has a
> > slightly different set of DSI mode related flags, let's move the
> > currently hardcoded mode flags to the .data field of of_device_id
> > structure.
> >
> > [...]
>
> Applied, thanks!
>
> [1/3] drm/panel: ltk050h3146w: add mipi_dsi_device.mode_flags to of_match_data
> commit: 99403d747ae8c7b3bfb5cd14c8908930ec6801c6
> [2/3] drm/panel: ltk050h3146w: add support for Leadtek LTK050H3148W-CTA6 variant
> commit: e5f9d543419c78ac58f3b3557bc5a76b20ff600b
> [3/3] dt-bindings: ltk050h3146w: add compatible for LTK050H3148W-CTA6 variant
> commit: 29d8e38c36cb662331a833699c359ec1af1edbec
forgot to add, I included the move to the generic mipi_dsi_dcs_write_seq()
for the new sequence.
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: quentin.schulz@theobroma-systems.com
Cc: devicetree@vger.kernel.org,
Quentin Schulz <foss+kernel@0leil.net>,
airlied@linux.ie, linux-kernel@vger.kernel.org,
dri-devel@lists.freedesktop.org, robh+dt@kernel.org,
thierry.reding@gmail.com, sam@ravnborg.org
Subject: Re: [PATCH 1/3] drm/panel: ltk050h3146w: add mipi_dsi_device.mode_flags to of_match_data
Date: Tue, 10 Oct 2023 18:55:42 +0200 [thread overview]
Message-ID: <2369051.yKrmzQ4Hd0@diego> (raw)
In-Reply-To: <169695678310.350877.5388571923561270631.b4-ty@sntech.de>
Am Dienstag, 10. Oktober 2023, 18:54:11 CEST schrieb Heiko Stuebner:
> On Mon, 31 Jan 2022 17:47:21 +0100, quentin.schulz@theobroma-systems.com wrote:
> > From: Quentin Schulz <quentin.schulz@theobroma-systems.com>
> >
> > To prepare for a new display to be supported by this driver which has a
> > slightly different set of DSI mode related flags, let's move the
> > currently hardcoded mode flags to the .data field of of_device_id
> > structure.
> >
> > [...]
>
> Applied, thanks!
>
> [1/3] drm/panel: ltk050h3146w: add mipi_dsi_device.mode_flags to of_match_data
> commit: 99403d747ae8c7b3bfb5cd14c8908930ec6801c6
> [2/3] drm/panel: ltk050h3146w: add support for Leadtek LTK050H3148W-CTA6 variant
> commit: e5f9d543419c78ac58f3b3557bc5a76b20ff600b
> [3/3] dt-bindings: ltk050h3146w: add compatible for LTK050H3148W-CTA6 variant
> commit: 29d8e38c36cb662331a833699c359ec1af1edbec
forgot to add, I included the move to the generic mipi_dsi_dcs_write_seq()
for the new sequence.
next prev parent reply other threads:[~2023-10-10 16:55 UTC|newest]
Thread overview: 17+ 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 ` quentin.schulz
2022-01-31 16:47 ` [PATCH 2/3] drm/panel: ltk050h3146w: add support for Leadtek LTK050H3148W-CTA6 variant quentin.schulz
2022-01-31 16:47 ` 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-01-31 16:47 ` quentin.schulz
2022-02-11 13:30 ` Rob Herring
2022-02-11 13:30 ` Rob Herring
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-05-03 15:23 ` Quentin Schulz
2022-06-09 8:50 ` Paul Kocialkowski
2023-10-10 16:54 ` Heiko Stuebner
2023-10-10 16:54 ` Heiko Stuebner
2023-10-10 16:55 ` Heiko Stübner [this message]
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=2369051.yKrmzQ4Hd0@diego \
--to=heiko@sntech.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.