From: Heiko Stuebner <heiko@sntech.de>
To: Diederik de Haas <diederik@cknow-tech.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Pedro Alves <pta2002@pta2002.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] arm64: dts: rockchip: configure hdmirx in Rock 5 ITX
Date: Wed, 04 Mar 2026 21:26:00 +0100 [thread overview]
Message-ID: <24285215.6Emhk5qWAg@phil> (raw)
In-Reply-To: <CAAEXfUVBVMmT3i+10F3uvmGOtMMLoQK4WXM7_0G88aL5DntOuw@mail.gmail.com>
Am Mittwoch, 4. März 2026, 21:05:52 Mitteleuropäische Normalzeit schrieb Pedro Alves:
> On 04/03/2026 18:38, Diederik de Haas wrote:
> > I have a strong suspicion that it was named 'hdmirx_det' because in the
> > schema its label is 'HDMIIRX_DET_L' where the extra 'I' was probably
> > dropped as that seems to be a spelling issue and the '_L' suffix is
> > quite often dropped.
> >
> > FWIW: The label in the schematic for Rock 5B, Rock 5B+, Rock 5T and Rock
> > 5 ITX+ are all 'HDMIIRX_DET_L', yet none of them follow the convention
> > to use the label from the schematics.
>
> That's a good point, and the other boards all have the hdmirx_det
> naming in the downstream kernel, so I guess that would be the most
> "correct" name to use.
>
> > So now the 'problem' is indeed: make it consistent with the other boards
> > or keep the one where the convention was followed.
>
> Also a third option of changing the other boards to all match. Either
> way, I can do those changes, just let me know what would be desirable.
I really want pin-names to reflect the schematics. This makes searching
so much easier. Sometimes things slip through where that doesn't match,
but the goal would be to always move to improve things.
So at least the newly added hdmirx here should follow the schematics,
and if you are keen to bring everything in line, you could also change
the other boards. But please make sure via the schematics of those :-)
Thanks
Heiko
next prev parent reply other threads:[~2026-03-04 20:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 13:54 [PATCH] arm64: dts: rockchip: configure hdmirx in Rock 5 ITX Pedro Alves
2026-03-04 18:38 ` Diederik de Haas
2026-03-04 20:05 ` Pedro Alves
2026-03-04 20:26 ` Heiko Stuebner [this message]
2026-03-04 20:48 ` Pedro Alves
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=24285215.6Emhk5qWAg@phil \
--to=heiko@sntech.de \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=diederik@cknow-tech.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pta2002@pta2002.com \
--cc=robh@kernel.org \
/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