Add bindings for the Tianma TA066VVHM03 6.59" 1080x2340 AMOLED DSI
panel with DSC compression, found in the ASUS ROG Phone 3.

Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
Signed-off-by: Alexander Koskovich <akoskovich@pm.me>
---
 .../bindings/display/panel/tianma,ta066vvhm03.yaml | 67 ++++++++++++++++++++++
 1 file changed, 67 insertions(+)

diff --git a/Documentation/devicetree/bindings/display/panel/tianma,ta066vvhm03.yaml b/Documentation/devicetree/bindings/display/panel/tianma,ta066vvhm03.yaml
new file mode 100644
index 000000000000..9bd80cd9662f
--- /dev/null
+++ b/Documentation/devicetree/bindings/display/panel/tianma,ta066vvhm03.yaml
@@ -0,0 +1,67 @@
+# SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/display/panel/tianma,ta066vvhm03.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: Tianma TA066VVHM03 AMOLED DSI Panel
+
+maintainers:
+  - Alexander Koskovich <akoskovich@pm.me>
+
+allOf:
+  - $ref: panel-common.yaml#
+
+properties:
+  compatible:
+    const: tianma,ta066vvhm03
+
+  reg:
+    maxItems: 1
+    description: DSI virtual channel
+
+  vddio-supply: true
+  vci-supply: true
+  vdd-supply: true
+  port: true
+  enable-gpios: true
+  reset-gpios: true
+
+required:
+  - compatible
+  - reg
+  - vddio-supply
+  - vci-supply
+  - vdd-supply
+  - reset-gpios
+  - port
+
+additionalProperties: false
+
+examples:
+  - |
+    #include <dt-bindings/gpio/gpio.h>
+
+    dsi {
+        #address-cells = <1>;
+        #size-cells = <0>;
+
+        panel@0 {
+            compatible = "tianma,ta066vvhm03";
+            reg = <0>;
+
+            enable-gpios = <&tlmm 12 GPIO_ACTIVE_HIGH>;
+            reset-gpios = <&tlmm 75 GPIO_ACTIVE_LOW>;
+
+            vci-supply = <&vreg_l10a>;
+            vdd-supply = <&vreg_l3c>;
+            vddio-supply = <&vreg_l14a>;
+
+            port {
+                panel_in: endpoint {
+                    remote-endpoint = <&mdss_dsi0_out>;
+                };
+            };
+        };
+    };
+...

-- 
2.53.0

On Sun, Mar 08, 2026 at 09:09:00PM +0000, Alexander Koskovich wrote:
> Add bindings for the Tianma TA066VVHM03 6.59" 1080x2340 AMOLED DSI
> panel with DSC compression, found in the ASUS ROG Phone 3.
> 
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>
> Signed-off-by: Alexander Koskovich <akoskovich@pm.me>

BTW, all of your patches have mismatched From and SoB cases. It passes
the checks but I do not see reason why different case should be used.
Especially that it is manual process to achieve that - none of the
standard ways of using git produce such result, because SoB is added
automatically based on From name. Unless your mail server is changing
these, but that's also odd.

This should be fixed in all of your patches, IMO.

Best regards,
Krzysztof

On Monday, March 9th, 2026 at 3:35 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> 
> BTW, all of your patches have mismatched From and SoB cases. It passes
> the checks but I do not see reason why different case should be used.
> Especially that it is manual process to achieve that - none of the
> standard ways of using git produce such result, because SoB is added
> automatically based on From name. Unless your mail server is changing
> these, but that's also odd.
> 
> This should be fixed in all of your patches, IMO.

I did notice that, looked into it briefly the other day and it appears to be Protonmail Bridge that is doing it, I always use "akoskovich@pm.me", but Protonmail seems to be sending out as "AKoskovich@pm.me".

It also made some linux-media CI checks fail :(

Would you suggest I change my git identity to use uppercase here and then resend all patches?

> 
> Best regards,
> Krzysztof
> 

Thanks,
Alex

On 09/03/2026 08:41, Alexander Koskovich wrote:
> On Monday, March 9th, 2026 at 3:35 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
>>
>> BTW, all of your patches have mismatched From and SoB cases. It passes
>> the checks but I do not see reason why different case should be used.
>> Especially that it is manual process to achieve that - none of the
>> standard ways of using git produce such result, because SoB is added
>> automatically based on From name. Unless your mail server is changing
>> these, but that's also odd.
>>
>> This should be fixed in all of your patches, IMO.
> 
> I did notice that, looked into it briefly the other day and it appears to be Protonmail Bridge that is doing it, I always use "akoskovich@pm.me", but Protonmail seems to be sending out as "AKoskovich@pm.me".
> 
> It also made some linux-media CI checks fail :(
> 
> Would you suggest I change my git identity to use uppercase here and then resend all patches?
> 

Just change it in Proton settings to lowercase. Or don't use Proton for
kernel development - in the past it was causing a lot of troubles, so
here we have another reason - mangling silently with headers.

Best regards,
Krzysztof

On Monday, March 9th, 2026 at 3:54 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:

> On 09/03/2026 08:41, Alexander Koskovich wrote:
> > On Monday, March 9th, 2026 at 3:35 AM, Krzysztof Kozlowski <krzk@kernel.org> wrote:
> >>
> >> BTW, all of your patches have mismatched From and SoB cases. It passes
> >> the checks but I do not see reason why different case should be used.
> >> Especially that it is manual process to achieve that - none of the
> >> standard ways of using git produce such result, because SoB is added
> >> automatically based on From name. Unless your mail server is changing
> >> these, but that's also odd.
> >>
> >> This should be fixed in all of your patches, IMO.
> >
> > I did notice that, looked into it briefly the other day and it appears to be Protonmail Bridge that is doing it, I always use "akoskovich@pm.me", but Protonmail seems to be sending out as "AKoskovich@pm.me".
> >
> > It also made some linux-media CI checks fail :(
> >
> > Would you suggest I change my git identity to use uppercase here and then resend all patches?
> >
> 
> Just change it in Proton settings to lowercase. Or don't use Proton for
> kernel development - in the past it was causing a lot of troubles, so
> here we have another reason - mangling silently with headers.

Thanks, I see in Proton's settings that I can just change the case. Done, will resubmit changes in a bit.

On the header mangling thing, I think I've already seen that. I noticed that when I send via git send-email, it strips out the "In-Reply-To" from the headers leading to the threading getting lost.

Will try to look into getting a different email provider for Linux contributions set up at some point.

> Best regards,
> Krzysztof
> 

Thanks,
Alex