From: "Heiko Stübner" <heiko@sntech.de>
To: Andy Yan <andyshrk@163.com>,
Detlev Casanova <detlev.casanova@collabora.com>
Cc: cristian.ciocaltea@collabora.com, krzk+dt@kernel.org,
mripard@kernel.org, hjc@rock-chips.com,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.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: [PATCH 3/3] drm/rockchip: Add basic RK3576 HDMI output support
Date: Thu, 02 Jan 2025 12:56:55 +0100 [thread overview]
Message-ID: <15367137.tv2OnDr8pf@diego> (raw)
In-Reply-To: <20241225103741.364597-4-andyshrk@163.com>
Am Mittwoch, 25. Dezember 2024, 11:37:31 CET schrieb Andy Yan:
> From: Andy Yan <andy.yan@rock-chips.com>
>
> The HDMI on RK3576 shares the same IP block (PHY and Controller)
> with rk3588.
> However, there are some control bits scattered in different GRF.
>
> Signed-off-by: Andy Yan <andy.yan@rock-chips.com>
> Signed-off-by: Detlev Casanova <detlev.casanova@collabora.com>
> Tested-by: Detlev Casanova <detlev.casanova@collabora.com>
The attribution is strange. Where does the Signed-off from Detlev come
from?
At that position it would mean that he's the sender, but that's obviously
not the case.
I guess it's either just the Tested-by ... or you need an additional
Co-Developed-by if Detlev contributed to this patch.
> ---
>
> .../gpu/drm/rockchip/dw_hdmi_qp-rockchip.c | 143 +++++++++++++++++-
> 1 file changed, 141 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c b/drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c
> index b21e868e7c16..bd9216e45e74 100644
> --- a/drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c
> +++ b/drivers/gpu/drm/rockchip/dw_hdmi_qp-rockchip.c
[...]
> @@ -287,8 +422,12 @@ static const struct rockchip_hdmi_qp_cfg rk3588_hdmi_cfg = {
> };
>
> static const struct of_device_id dw_hdmi_qp_rockchip_dt_ids[] = {
> - { .compatible = "rockchip,rk3588-dw-hdmi-qp",
> - .data = &rk3588_hdmi_cfg },
> + { .compatible = "rockchip,rk3576-dw-hdmi-qp",
> + .data = &rk3576_hdmi_cfg
> + }, {
> + .compatible = "rockchip,rk3588-dw-hdmi-qp",
> + .data = &rk3588_hdmi_cfg
> + },
nit: please keep consistent styling between the listentries. Right now the
rk3576 and changed rk3588 entries use different styles.
Heiko
prev parent reply other threads:[~2025-01-02 11:58 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-25 10:37 [PATCH 0/3] Add HDMI support for rk3576 Andy Yan
2024-12-25 10:37 ` [PATCH 1/3] drm/rockchip: dw_hdmi_qp: Add platform ctrl callback Andy Yan
2025-01-02 11:51 ` Heiko Stübner
2025-01-06 8:35 ` Andy Yan
2025-01-06 9:23 ` Heiko Stübner
2024-12-25 10:37 ` [PATCH 2/3] dt-bindings: display: rockchip: Add support for RK3576 HDMI TX Controller Andy Yan
2025-01-02 7:58 ` Krzysztof Kozlowski
2024-12-25 10:37 ` [PATCH 3/3] drm/rockchip: Add basic RK3576 HDMI output support Andy Yan
2025-01-02 11:56 ` Heiko Stübner [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=15367137.tv2OnDr8pf@diego \
--to=heiko@sntech.de \
--cc=andy.yan@rock-chips.com \
--cc=andyshrk@163.com \
--cc=cristian.ciocaltea@collabora.com \
--cc=detlev.casanova@collabora.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=hjc@rock-chips.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=mripard@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;
as well as URLs for NNTP newsgroup(s).