From: Heiko Stuebner <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>,
Sebastian Reichel <sebastian.reichel@collabora.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Yifeng Zhao <yifeng.zhao@rock-chips.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org,
linux-phy@lists.infradead.org, devicetree@vger.kernel.org,
Chukun Pan <amadeus@jmu.edu.cn>
Subject: Re: [PATCH 1/2] arm64: dts: rockchip: rk3568: add reset-names for combphy
Date: Fri, 22 Nov 2024 08:56:17 +0100 [thread overview]
Message-ID: <12563257.O9o76ZdvQC@phil> (raw)
In-Reply-To: <20241122073006.99309-1-amadeus@jmu.edu.cn>
Am Freitag, 22. November 2024, 08:30:05 CET schrieb Chukun Pan:
> The reset-names of combphy are missing, add it.
>
> Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
Fixes: fd3ac6e80497 ("dt-bindings: phy: rockchip: rk3588 has two reset lines")
It does looks like, before that patch above, the phy did not use
nor require reset-names?
No need to resend for this, as I think b4 will just pick up this
addition when I grab the series from the list.
next prev parent reply other threads:[~2024-11-22 7:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-22 7:30 [PATCH 1/2] arm64: dts: rockchip: rk3568: add reset-names for combphy Chukun Pan
2024-11-22 7:30 ` [PATCH 2/2] phy: rockchip: naneng-combphy: fix phy reset Chukun Pan
2024-11-22 8:01 ` Heiko Stuebner
2024-11-23 22:28 ` FUKAUMI Naoki
2024-11-22 7:56 ` Heiko Stuebner [this message]
2024-11-22 8:12 ` [PATCH 1/2] arm64: dts: rockchip: rk3568: add reset-names for combphy Heiko Stuebner
2024-12-02 23:29 ` (subset) " Heiko Stuebner
2024-12-08 16:58 ` Vinod Koul
2025-01-02 15:16 ` Jianfeng Liu
2025-01-02 16:57 ` Jonas Karlman
2025-01-03 3:30 ` Chukun Pan
2025-01-03 10:26 ` Heiko Stübner
2025-01-03 17:11 ` Jianfeng Liu
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=12563257.O9o76ZdvQC@phil \
--to=heiko@sntech.de \
--cc=amadeus@jmu.edu.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kishon@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=vkoul@kernel.org \
--cc=yifeng.zhao@rock-chips.com \
/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).