From: Heiko Stuebner <heiko@sntech.de>
To: Johan Jonker <jbx6244@gmail.com>
Cc: Heiko Stuebner <heiko@sntech.de>,
devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
robh+dt@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: dts: rockchip: fix phy nodename for rk3328
Date: Tue, 19 May 2020 00:28:01 +0200 [thread overview]
Message-ID: <158984064169.2259329.15579989069543124777.b4-ty@sntech.de> (raw)
In-Reply-To: <20200505170227.6503-1-jbx6244@gmail.com>
On Tue, 5 May 2020 19:02:27 +0200, Johan Jonker wrote:
> A test with the command below gives for example this error:
>
> arch/arm64/boot/dts/rockchip/rk3328-evb.dt.yaml: phy@0:
> '#phy-cells' is a required property
>
> The phy nodename is normally used by a phy-handle.
> This node is however compatible with
> "ethernet-phy-id1234.d400", "ethernet-phy-ieee802.3-c22"
> which is just been added to 'ethernet-phy.yaml'.
> So change nodename to 'ethernet-phy' for which '#phy-cells'
> is not a required property
>
> [...]
Applied, thanks!
[1/1] arm64: dts: rockchip: fix phy nodename for rk3328
commit: 8370cc5533b3baa5e0f18075ae638b050458aabd
Best regards,
--
Heiko Stuebner <heiko@sntech.de>
next prev parent reply other threads:[~2020-05-18 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-21 21:54 [PATCH 1/6] arm64: dts: rockchip: fix phy nodename for rk3328 Johan Jonker
2020-03-21 21:54 ` [PATCH 2/6] arm64: dts: rockchip: fix rtl8211f nodename for rk3328 Beelink A1 Johan Jonker
2020-03-21 21:54 ` [PATCH 3/6] arm64: dts: rockchip: fix rtl8211e nodename for rk3399-nanopi4 Johan Jonker
2020-03-21 21:54 ` [PATCH 4/6] arm64: dts: rockchip: fix &pinctrl phy sub " Johan Jonker
2020-03-21 21:54 ` [PATCH 5/6] arm64: dts: rockchip: fix rtl8211e nodename for rk3399-orangepi Johan Jonker
2020-03-21 21:54 ` [PATCH 6/6] arm64: dts: rockchip: fix &pinctrl phy sub " Johan Jonker
2020-05-05 17:02 ` [PATCH v2] arm64: dts: rockchip: fix phy nodename for rk3328 Johan Jonker
2020-05-18 22:28 ` Heiko Stuebner [this message]
2020-05-18 22:27 ` [PATCH 1/6] " Heiko Stuebner
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=158984064169.2259329.15579989069543124777.b4-ty@sntech.de \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=jbx6244@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=robh+dt@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).