From: "Andy Yan" <andyshrk@163.com>
To: "Heiko Stübner" <heiko@sntech.de>
Cc: "Krzysztof Kozlowski" <krzk@kernel.org>,
cristian.ciocaltea@collabora.com, detlev.casanova@collabora.com,
krzk+dt@kernel.org, vkoul@kernel.org, kishon@kernel.org,
robh@kernel.org, sebastian.reichel@collabora.com,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org,
"Andy Yan" <andy.yan@rock-chips.com>
Subject: Re:Re: [PATCH] dt-bindings: phy: add rk3576 hdptx phy
Date: Sat, 28 Dec 2024 15:00:29 +0800 (CST) [thread overview]
Message-ID: <50a70e66.1b76.1940c1104c8.Coremail.andyshrk@163.com> (raw)
In-Reply-To: <3255768.PYKUYFuaPT@diego>
Hi Heikio, Krzysztof,
At 2024-12-28 04:08:41, "Heiko Stübner" <heiko@sntech.de> wrote:
>Hi Krzysztof, Andy,
>
>Am Freitag, 27. Dezember 2024, 09:55:59 CET schrieb Krzysztof Kozlowski:
>> On Tue, Dec 24, 2024 at 05:19:13PM +0800, Andy Yan wrote:
>> > From: Andy Yan <andy.yan@rock-chips.com>
>> >
>> > The HDPTX PHY on rk3576 is compatible with it on
>> > rk3588.
>> >
>> > Add compatible for it.
>> >
>> > Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
>> > ---
>> >
>> > .../devicetree/bindings/phy/rockchip,rk3588-hdptx-phy.yaml | 7 +++++--
>> > 1 file changed, 5 insertions(+), 2 deletions(-)
>>
>> Also: where are any users of this binding?
>>
>> We don't take bindings without *UPSTREAM* users.
>
>Andy, can you do a (separate) DTS series that binds all the display stuff
>together on one rk3576 board? (iommu, hdptxphy, vop, hdmi)
>
>Depending on how the driver sides go, this may be need to be revised at
>the end, but should hopefully satisfy that "show a user" thing.
>
>I guess Kever's EVB-series [0] might be a good base to build upon, with it
>being a Rockchip EVB?
As EVB patch series is still WIP, I will use rk3576-armsom-sige5.dts which is already
in mainline as the base to collect all display related dts。
>
>
>For people reading along, that whole display chain consists of:
>- iommu [1]
>- core display-controller additions for the rk3576 [2]
>- this hdptxphy binding
>- additions for the dw-hdmi-qp glue [3]
>
>Heiko
>
>
>[0] https://lore.kernel.org/lkml/20241220101551.3505917-1-kever.yang@rock-chips.com/
>[1] https://lore.kernel.org/lkml/20240920094947.7566-1-andyshrk@163.com/
>[2] https://lore.kernel.org/lkml/20241214081831.3330714-1-andyshrk@163.com/
>[3} https://lore.kernel.org/lkml/20241225103741.364597-1-andyshrk@163.com/
>
>
>
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
prev parent reply other threads:[~2024-12-28 7:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-24 9:19 [PATCH] dt-bindings: phy: add rk3576 hdptx phy Andy Yan
2024-12-27 8:55 ` Krzysztof Kozlowski
2024-12-27 10:46 ` Andy Yan
2024-12-28 9:36 ` Krzysztof Kozlowski
2024-12-27 8:55 ` Krzysztof Kozlowski
2024-12-27 20:08 ` Heiko Stübner
2024-12-28 7:00 ` Andy Yan [this message]
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=50a70e66.1b76.1940c1104c8.Coremail.andyshrk@163.com \
--to=andyshrk@163.com \
--cc=andy.yan@rock-chips.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=vkoul@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