From: Guo Samin <samin.guo@starfivetech.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: <linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
<netdev@vger.kernel.org>, Peter Geis <pgwipeout@gmail.com>,
Frank <Frank.Sae@motor-comm.com>,
"David S . Miller" <davem@davemloft.net>,
"Eric Dumazet" <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Yanhong Wang <yanhong.wang@starfivetech.com>
Subject: Re: [PATCH v2 2/2] net: phy: motorcomm: Add pad drive strength cfg support
Date: Sat, 6 May 2023 15:13:51 +0800 [thread overview]
Message-ID: <f2b54fc5-81a6-45ae-0218-193a993333ab@starfivetech.com> (raw)
In-Reply-To: <fc516e65-cde2-4a65-a3c5-bd8c939e7eb1@lunn.ch>
Re: [PATCH v2 2/2] net: phy: motorcomm: Add pad drive strength cfg support
From: Andrew Lunn <andrew@lunn.ch>
to: Samin Guo <samin.guo@starfivetech.com>
data: 2023/5/5
>> #define YTPHY_DTS_OUTPUT_CLK_DIS 0
>> @@ -1495,6 +1504,7 @@ static int yt8531_config_init(struct phy_device *phydev)
>> {
>> struct device_node *node = phydev->mdio.dev.of_node;
>> int ret;
>> + u32 ds, val;
>
> Reverse Christmas tree. Sort these longest first, shortest last.
>
Thanks, will fix.
> Otherwise this looks O.K.
>
> The only open question is if real unit should be used, uA, not some
> magic numbers. Lets see what the DT Maintainers say.
>
> Andrew
Hi Andrew,
As I communicated with Frank, Motorcomm doesn't give specific units on their datasheet, except for magic numbers.
Tried to ask Motorcomm last week, but it seems that they themselves do not know what the unit is and have no response so far.
Below is all the relevant information I found:
Pad Drive Strength Cfg (EXT_0xA010)
Bit | Symbol | Access | Default | Description
15:13 | Rgmii_sw_dr_rx | RW | 0x3 | Drive strenght of rx_clk pad.
| 3'b111: strongest; 3'b000: weakest.
12 | Rgmii_sw_dr[2] | RW | 0x0 | Bit 2 of Rgmii_sw_dr[2:0], refer to ext A010[5:4]
5:4 | Rgmii_sw_dr[1:0] | RW | 0x3 | Bit 1 and 0 of Rgmii_sw_dr, Drive strenght of rxd/rx_ctl rgmii pad.
| 3'b111: strongest; 3'b000: weakest
Best regards,
Samin
next prev parent reply other threads:[~2023-05-06 7:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-05 9:05 [PATCH v2 0/2] Add motorcomm phy pad-driver-strength-cfg support Samin Guo
2023-05-05 9:05 ` [PATCH v2 1/2] dt-bindings: net: motorcomm: Add pad driver strength cfg Samin Guo
2023-05-05 17:52 ` Krzysztof Kozlowski
2023-05-05 9:05 ` [PATCH v2 2/2] net: phy: motorcomm: Add pad drive strength cfg support Samin Guo
2023-05-05 13:18 ` Andrew Lunn
2023-05-06 7:13 ` Guo Samin [this message]
2023-05-18 8:29 ` Guo Samin
2023-05-06 1:29 ` Frank Sae
2023-05-06 1:52 ` Guo Samin
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=f2b54fc5-81a6-45ae-0218-193a993333ab@starfivetech.com \
--to=samin.guo@starfivetech.com \
--cc=Frank.Sae@motor-comm.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pgwipeout@gmail.com \
--cc=robh+dt@kernel.org \
--cc=yanhong.wang@starfivetech.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).