From: "Heiko Stübner" <heiko@sntech.de>
To: Chukun Pan <amadeus@jmu.edu.cn>,
"David S . Miller" <davem@davemloft.net>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Giuseppe Cavallaro <peppe.cavallaro@st.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Jose Abreu <joabreu@synopsys.com>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
David Wu <david.wu@rock-chips.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] dt-bindings: net: rockchip-dwmac: add rk3568 xpcs compatible
Date: Tue, 29 Nov 2022 10:56:39 +0100 [thread overview]
Message-ID: <4692527.5fSG56mABF@diego> (raw)
In-Reply-To: <6f601615-deab-a1df-b951-dca8467039f8@linaro.org>
Am Dienstag, 29. November 2022, 09:49:08 CET schrieb Krzysztof Kozlowski:
> On 29/11/2022 08:27, Chukun Pan wrote:
> > The gmac of RK3568 supports RGMII/SGMII/QSGMII interface.
> > This patch adds a compatible string for the required clock.
> >
> > Signed-off-by: Chukun Pan <amadeus@jmu.edu.cn>
> > ---
> > Documentation/devicetree/bindings/net/rockchip-dwmac.yaml | 6 ++++++
> > 1 file changed, 6 insertions(+)
> >
> > diff --git a/Documentation/devicetree/bindings/net/rockchip-dwmac.yaml b/Documentation/devicetree/bindings/net/rockchip-dwmac.yaml
> > index 42fb72b6909d..36b1e82212e7 100644
> > --- a/Documentation/devicetree/bindings/net/rockchip-dwmac.yaml
> > +++ b/Documentation/devicetree/bindings/net/rockchip-dwmac.yaml
> > @@ -68,6 +68,7 @@ properties:
> > - mac_clk_rx
> > - aclk_mac
> > - pclk_mac
> > + - pclk_xpcs
> > - clk_mac_ref
> > - clk_mac_refout
> > - clk_mac_speed
> > @@ -90,6 +91,11 @@ properties:
> > The phandle of the syscon node for the peripheral general register file.
> > $ref: /schemas/types.yaml#/definitions/phandle
> >
> > + rockchip,xpcs:
> > + description:
> > + The phandle of the syscon node for the peripheral general register file.
>
> You used the same description as above, so no, you cannot have two
> properties which are the same. syscons for GRF are called
> "rockchip,grf", aren't they?
Not necessarily :-) .
The GRF is Rockchip's way of not sorting their own invented
additional registers. (aka a bunch of registers
While on the older models there only ever was the one GRF
as dumping ground, newer SoCs now end up with multiple ones :-)
These are still iomem areas separate from the actual device-iomem they
work with/for but SoCs like the rk3568 now have at least 13 of them.
_But_ for the patch in question I fail to see what this set does at all.
The rk3568 (only) has XPCS_CON0 and XPCS_STATUS in its PIPE_GRF syscon
(according to the TRM), but the patch2 does strange things with
offset calculations and names that do not seem to have a match in the TRM.
So definitely more explanation on what happens here would be necessary.
Heiko
next prev parent reply other threads:[~2022-11-29 9:57 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-29 7:27 [PATCH 1/2] dt-bindings: net: rockchip-dwmac: add rk3568 xpcs compatible Chukun Pan
2022-11-29 7:27 ` [PATCH 2/2] ethernet: stmicro: stmmac: Add SGMII/QSGMII support for RK3568 Chukun Pan
2022-11-29 8:53 ` Krzysztof Kozlowski
2022-11-29 18:31 ` Andrew Lunn
2022-11-29 8:49 ` [PATCH 1/2] dt-bindings: net: rockchip-dwmac: add rk3568 xpcs compatible Krzysztof Kozlowski
2022-11-29 8:51 ` Krzysztof Kozlowski
2022-11-29 9:56 ` Heiko Stübner [this message]
2022-11-29 9:59 ` Krzysztof Kozlowski
2022-11-29 10:22 ` Heiko Stübner
2022-12-01 23:22 ` Rob Herring
2022-12-03 9:00 ` Chukun Pan
2022-12-03 17:27 ` Andrew Lunn
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=4692527.5fSG56mABF@diego \
--to=heiko@sntech.de \
--cc=alexandre.torgue@foss.st.com \
--cc=amadeus@jmu.edu.cn \
--cc=davem@davemloft.net \
--cc=david.wu@rock-chips.com \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=joabreu@synopsys.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=peppe.cavallaro@st.com \
--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).