From: Kaustabh Chakraborty <kauschluss@disroot.org>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: Neil Armstrong <neil.armstrong@linaro.org>,
Jessica Zhang <quic_jesszhan@quicinc.com>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Jessica Zhang <jessica.zhang@oss.qualcomm.com>,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 1/2] dt-bindings: display: panel: document Synaptics TDDI panel
Date: Wed, 06 Aug 2025 15:22:32 +0000 [thread overview]
Message-ID: <7f3098a04a6c709a5fff5869046512e5@disroot.org> (raw)
In-Reply-To: <7rk5cgjiublkrczl6khkjepixppbatee25w6gc5utfvrcl45o7@6oouraafet2f>
On 2025-08-03 12:02, Dmitry Baryshkov wrote:
> On Sun, Jul 20, 2025 at 05:31:54PM +0530, Kaustabh Chakraborty wrote:
>> Document the Synaptics TDDI (Touch/Display Integration) panel
>> hardware.
>> Along with the MIPI-DSI panel, these devices also have an in-built LED
>> backlight device and a touchscreen, all packed together in a single
>> chip.
>>
>> Also, add compatibles for supported panels - TD4101 and TD4300. Both
>> have the '-panel' suffix so as to remove any ambiguity between the
>> panel
>> and touchscreen chips.
>>
>> Signed-off-by: Kaustabh Chakraborty <kauschluss@disroot.org>
>> ---
>> .../display/panel/synaptics,td4300-panel.yaml | 89
>> ++++++++++++++++++++++
>> 1 file changed, 89 insertions(+)
>>
>> diff --git
>> a/Documentation/devicetree/bindings/display/panel/synaptics,td4300-panel.yaml
>> b/Documentation/devicetree/bindings/display/panel/synaptics,td4300-panel.yaml
>> new file mode 100644
>> index
>> 0000000000000000000000000000000000000000..152d94367130e9d80a885fe87a2da53db88e3393
>> --- /dev/null
>> +++
>> b/Documentation/devicetree/bindings/display/panel/synaptics,td4300-panel.yaml
>> @@ -0,0 +1,89 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id:
>> http://devicetree.org/schemas/display/panel/synaptics,td4300-panel.yaml#
>> +$schema: http://devicetree.org/meta-schemas/core.yaml#
>> +
>> +title: Synaptics TDDI Display Panel Controller
>> +
>> +maintainers:
>> + - Kaustabh Chakraborty <kauschluss@disroot.org>
>> +
>> +allOf:
>> + - $ref: panel-common.yaml#
>> +
>> +properties:
>> + compatible:
>> + enum:
>> + - syna,td4101-panel
>> + - syna,td4300-panel
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + vio-supply:
>> + description: core I/O voltage supply
>> +
>> + vsn-supply:
>> + description: negative voltage supply for analog circuits
>> +
>> + vsp-supply:
>> + description: positive voltage supply for analog circuits
>> +
>> + backlight-gpios:
>> + maxItems: 1
>> + description: backlight enable GPIO
>> +
>> + reset-gpios: true
>> + width-mm: true
>> + height-mm: true
>> + panel-timing: true
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - width-mm
>> + - height-mm
>> + - panel-timing
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/gpio/gpio.h>
>> +
>> + dsi {
>> + #address-cells = <1>;
>> + #size-cells = <0>;
>> +
>> + panel@0 {
>> + compatible = "syna,td4300-panel";
>> + reg = <0>;
>> +
>> + vio-supply = <&panel_vio_reg>;
>> + vsn-supply = <&panel_vsn_reg>;
>> + vsp-supply = <&panel_vsp_reg>;
>> +
>> + backlight-gpios = <&gpd3 5 GPIO_ACTIVE_LOW>;
>> + reset-gpios = <&gpd3 4 GPIO_ACTIVE_LOW>;
>> +
>> + width-mm = <68>;
>> + height-mm = <121>;
>> +
>> + panel-timing {
>
> Are the timings defined by the 'TD4300' name or might there be
> different
> panels with the same name but different timings?
Yes, if I recall correctly, the same panel was used by some Huawei
phones
with different panel timings. So this is just future-proofing.
>
>> + clock-frequency = <144389520>;
>> +
>> + hactive = <1080>;
>> + hsync-len = <4>;
>> + hfront-porch = <120>;
>> + hback-porch = <32>;
>> +
>> + vactive = <1920>;
>> + vsync-len = <2>;
>> + vfront-porch = <21>;
>> + vback-porch = <4>;
>> + };
>> + };
>> + };
>> +
>> +...
>>
>> --
>> 2.50.0
>>
>
> --
> With best wishes
> Dmitry
next prev parent reply other threads:[~2025-08-06 15:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-20 12:01 [PATCH v3 0/2] Support for Synaptics TDDI series panels Kaustabh Chakraborty
2025-07-20 12:01 ` [PATCH v3 1/2] dt-bindings: display: panel: document Synaptics TDDI panel Kaustabh Chakraborty
2025-07-21 7:48 ` Krzysztof Kozlowski
2025-08-03 12:02 ` Dmitry Baryshkov
2025-08-06 15:22 ` Kaustabh Chakraborty [this message]
2025-07-20 12:01 ` [PATCH v3 2/2] drm: panel: add support for Synaptics TDDI series DSI panels Kaustabh Chakraborty
2025-08-03 12:04 ` Dmitry Baryshkov
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=7f3098a04a6c709a5fff5869046512e5@disroot.org \
--to=kauschluss@disroot.org \
--cc=airlied@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jessica.zhang@oss.qualcomm.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=quic_jesszhan@quicinc.com \
--cc=robh@kernel.org \
--cc=simona@ffwll.ch \
--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
all inboxes | Powered by JetHome®