From: Maxime Ripard <mripard@kernel.org>
To: Kory Maincent <kory.maincent@bootlin.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Thomas Zimmermann <tzimmermann@suse.de>,
David Airlie <airlied@gmail.com>,
Simona Vetter <simona@ffwll.ch>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thomas Petazzoni <thomas.petazzoni@bootlin.com>,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH 1/4] dt-bindings: display: panel: ili9881c: Add dsi-lanes property
Date: Tue, 8 Apr 2025 17:44:32 +0200 [thread overview]
Message-ID: <20250408-statuesque-poised-firefly-ed8db1@houat> (raw)
In-Reply-To: <20250408-feature_sfto340xc-v1-1-f303d1b9a996@bootlin.com>
[-- Attachment #1: Type: text/plain, Size: 1145 bytes --]
hi,
On Tue, Apr 08, 2025 at 05:27:00PM +0200, Kory Maincent wrote:
> Add the dsi-lanes property to specify the number of DSI lanes used by the
> panel. This allows configuring the panel for either two, three or four
> lanes.
>
> Signed-off-by: Kory Maincent <kory.maincent@bootlin.com>
> ---
> Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml | 5 +++++
> 1 file changed, 5 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml b/Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml
> index baf5dfe5f5ebdd92f460a78d0e56e1b45e7dd323..e36550616f6aac86c79832a48132ce8c11ebcf7a 100644
> --- a/Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml
> +++ b/Documentation/devicetree/bindings/display/panel/ilitek,ili9881c.yaml
> @@ -27,6 +27,11 @@ properties:
> reg:
> maxItems: 1
>
> + dsi-lanes:
> + description: Number of DSI lanes to be used must be <2>, <3> or <4>
> + $ref: /schemas/types.yaml#/definitions/uint32
> + enum: [2, 3, 4]
> +
We have the data-lanes property for that already
Maxime
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-04-08 15:44 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 15:26 [PATCH 0/4] Add support for Saef SFTO340XC panel Kory Maincent
2025-04-08 15:27 ` [PATCH 1/4] dt-bindings: display: panel: ili9881c: Add dsi-lanes property Kory Maincent
2025-04-08 15:44 ` Maxime Ripard [this message]
2025-04-09 9:28 ` Kory Maincent
2025-04-10 9:33 ` Dmitry Baryshkov
2025-04-10 9:47 ` Dmitry Baryshkov
2025-04-08 15:27 ` [PATCH 2/4] drm/panel: ilitek-ili9881c: Add support for two-lane configuration Kory Maincent
2025-04-10 9:34 ` Dmitry Baryshkov
2025-04-10 9:47 ` Dmitry Baryshkov
2025-04-08 15:27 ` [PATCH 3/4] dt-bindings: ili9881c: Add Saef SFTO340XC support Kory Maincent
2025-04-08 16:07 ` Conor Dooley
2025-04-08 15:27 ` [PATCH 4/4] drm: panel: Add Saef SFTO340XC LCD panel Kory Maincent
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=20250408-statuesque-poised-firefly-ed8db1@houat \
--to=mripard@kernel.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=kory.maincent@bootlin.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--cc=thomas.petazzoni@bootlin.com \
--cc=tzimmermann@suse.de \
/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