[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <DAQHCWR6W4LD.2Q1H9B9JO2LJZ@cknow.org>
Date: Thu, 19 Jun 2025 13:41:03 +0200
From: "Diederik de Haas" <didi.debian@...ow.org>
To: "Olivier Benjamin" <olivier.benjamin@...tlin.com>, "Heiko Stuebner"
<heiko@...ech.de>, "Rob Herring" <robh@...nel.org>, "Krzysztof Kozlowski"
<krzk+dt@...nel.org>, "Conor Dooley" <conor+dt@...nel.org>
Cc: "Thomas Petazzoni" <thomas.petazzoni@...tlin.com>,
<devicetree@...r.kernel.org>, <linux-arm-kernel@...ts.infradead.org>,
<linux-rockchip@...ts.infradead.org>, <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v2] arm64: dts: rockchip: Fix the PinePhone Pro DTS'
panel description
On Thu Jun 19, 2025 at 12:47 PM CEST, Olivier Benjamin wrote:
> On 6/19/25 12:31, Heiko Stuebner wrote:
>> Am Donnerstag, 19. Juni 2025, 11:46:15 Mitteleuropäische Sommerzeit schrieb Diederik de Haas:
>>> On Thu Jun 19, 2025 at 7:21 AM CEST, Olivier Benjamin wrote:
>>> Thanks for working on upstreaming PPP things :-)
>>>
> My pleasure. I also have
> https://lore.kernel.org/linux-rockchip/20250509-camera-v3-0-dab2772d229a@bootlin.com/
> pending = )
Happy about that too, but I 'happen' to research DSI connected displays
(for other devices), so I felt comfortable to chime in with that.
I haven't looked at camera stuff yet (and it's not high on my prio
list), so hopefully others will chime in for that :-)
>>>> Fix a few issues in the panel section of the PinePhone Pro DTS:
>>>> - add the second part of the Himax HX8394 LCD panel controller
>>>> compatible
>>>> - as proposed by Diederik de Haas, reuse the mipi_out and ports
>>>> definitions from rk3399-base.dtsi instead of redefining them
>>>> - add a pinctrl for the LCD_RST signal for LCD1, derived from
>>>> LCD1_RST, which is on GPIO4_D1, as documented on pages 11
>>>> and 16 of the PinePhone Pro schematic
>>>>
>>>> Signed-off-by: Olivier Benjamin <olivier.benjamin@...tlin.com>
>>
>>>> + lcd {
>>>> + lcd_reset_pin: reset-pin {
>>>
>>> I don't know if there's a 'hard rule' for it, but I'd recommend to use
>>> ``lcd1_rst_pin: lcd1-rst-pin {`` as that would match the naming from
>>> the schematics. I realize that some but not all (other) pinctrl nodes
>>> follow that 'rule', but it helps with traceability.
>>
>> not a "hard" rule, but a strong preference.
>> I.e. we want people to ideally be able to just hit search in the
>> schematics PDFs for the name they saw in the devicetree.
>>
>> But following the schematic names, is the general goal.
>>
> Very fair. I used "lcd_reset" because even the schematic is not super
> clear: it uses "LCD_RST" on page 16 and LCD1_RST on pages 11 and 16.
AIUI, the GPIO pin (GPIO4_D1) is labeled LCD1_RST and on page 16 you can
see that is connected to LCD_RST from BL102-G39-1FR.
The definition here is about the GPIO pin, hence LCD1_RST.
The other part of my suggestion was related to another 'convention':
the name and label/phandle are the same with ``s/-/_/`` (and 'reset-pin'
is not specific enough; there are a number of reset pins).
Afaic you don't need to mention that I suggested the mipi_out related
changes; the reason to do that (unneeded redefinition of already defined
things), is.
Cheers,
Diederik
>> If this stays the only suggestion though, I can fix that when
>> applying. Or you can send a v3 - up to you :-)
>>
> I'll correct to lcd1_rst_pin and send a v3 (most likely later today)
>
>>>> + rockchip,pins = <4 RK_PD1 RK_FUNC_GPIO &pcfg_pull_none>;
>>>> + };
>>>> + };
>>>> +
>>>> leds {
>>>> red_led_pin: red-led-pin {
>>>> rockchip,pins = <4 RK_PD2 RK_FUNC_GPIO &pcfg_pull_none>;
>>>
>>> Otherwise,
>>>
>>> Reviewed-by: Diederik de Haas <didi.debian@...ow.org>
>>>
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists