From: Roger Quadros <rogerq@kernel.org>
To: Md Danish Anwar <a0501179@ti.com>, Andrew Lunn <andrew@lunn.ch>,
MD Danish Anwar <danishanwar@ti.com>
Cc: "Andrew F. Davis" <afd@ti.com>, Suman Anna <s-anna@ti.com>,
YueHaibing <yuehaibing@huawei.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Rob Herring <robh+dt@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Jakub Kicinski <kuba@kernel.org>,
Eric Dumazet <edumazet@google.com>,
"David S. Miller" <davem@davemloft.net>,
nm@ti.com, ssantosh@kernel.org, srk@ti.com,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
netdev@vger.kernel.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [EXTERNAL] Re: [PATCH v4 2/2] net: ti: icssg-prueth: Add ICSSG ethernet driver
Date: Tue, 7 Feb 2023 21:56:57 +0200 [thread overview]
Message-ID: <e8158969-08d0-1edc-24be-8c300a71adbd@kernel.org> (raw)
In-Reply-To: <42503a0d-b434-bbcc-553d-a326af5b4918@ti.com>
Danish,
On 07/02/2023 17:29, Md Danish Anwar wrote:
> Hi Andrew,
>
> On 06/02/23 19:45, Andrew Lunn wrote:
>>> +enum mii_mode {
>>> + MII_MODE_MII = 0,
>>> + MII_MODE_RGMII,
>>> + MII_MODE_SGMII
>>
>> There is no mention of SGMII anywhere else. And in a couple of places,
>> the code makes the assumption that if it is not RGMII it is MII.
>>
>> Does the hardware really support SGMII?
>>
>
> As far as I know, the hardware does support SGMII but it's not yet supported by
> the driver. I will drop the SGMII because it's not needed as of now. If in
> future support for SGMII is there, I'll add it.
>
>>> +static int prueth_config_rgmiidelay(struct prueth *prueth,
>>> + struct device_node *eth_np,
>>> + phy_interface_t phy_if)
>>> +{
>>
>> ...
>>
>>> + if (phy_if == PHY_INTERFACE_MODE_RGMII_ID ||
>>> + phy_if == PHY_INTERFACE_MODE_RGMII_TXID)
>>> + rgmii_tx_id |= ICSSG_CTRL_RGMII_ID_MODE;
>>> +
>>> + regmap_update_bits(ctrl_mmr, icssgctrl_reg, ICSSG_CTRL_RGMII_ID_MODE, rgmii_tx_id);
This is only applicable to some devices so you need to restrict this only
to those devices.
And only when you enable MAC TX delay you need to change emac->phy_if to PHY_INTERFACE_MODE_RGMII_RXID
if it was PHY_INTERFACE_MODE_RGMII_ID.
>>
>> Here you are adding the TX delay if the phy-mode indicates it should
>> be added.
>>
>>> +static int prueth_netdev_init(struct prueth *prueth,
>>> + struct device_node *eth_node)
>>> +{
>>
>>> + ret = of_get_phy_mode(eth_node, &emac->phy_if);
>>> + if (ret) {
>>> + dev_err(prueth->dev, "could not get phy-mode property\n");
>>> + goto free;
>>> + }
>>
>>> + ret = prueth_config_rgmiidelay(prueth, eth_node, emac->phy_if);
>>> + if (ret)
>>> + goto free;
>>> +
>>
>> Reading it from DT and calling the delay function.
>>
>>> +static int prueth_probe(struct platform_device *pdev)
>>> +{
>>
>>
>>> + /* register the network devices */
>>> + if (eth0_node) {
>>> + ret = register_netdev(prueth->emac[PRUETH_MAC0]->ndev);
>>> + if (ret) {
>>> + dev_err(dev, "can't register netdev for port MII0");
>>> + goto netdev_exit;
>>> + }
>>> +
>>> + prueth->registered_netdevs[PRUETH_MAC0] = prueth->emac[PRUETH_MAC0]->ndev;
>>> +
>>> + emac_phy_connect(prueth->emac[PRUETH_MAC0]);
>>
>> And this is connecting the MAC and the PHY, where emac_phy_connect()
>> passes emac->phy_if to phylib.
>>
>> What i don't see anywhere is you changing emac->phy_if to indicate the
>> MAC has inserted the TX delay, and so the PHY should not.
>>
>
> Yes, there is no indication whether MAC has enabled TX delay or not. I have
> changed the phy-mode in DT from "rgmii-rxid" to "rgmii-id" as per your
> suggestion in previous revision. I will keep Tx Internal delay as it is(getting
> configured in MAC) and inside emac_phy_connect() API, while calling
> of_phy_connect() instead of passing emac->phy_if (which is rgmii-id as per DT),
> I will pass PHY_INTERFACE_MODE_RGMII_RXID. This will make sure that phy only
> enables Rx delay and keep the existing approach of keepping Tx delay in MAC.
>
> Currently, in emac_phy_connect() API,
>
> /* connect PHY */
> ndev->phydev = of_phy_connect(emac->ndev, emac->phy_node,
> &emac_adjust_link, 0,
> emac->phy_if);
> I will change it to,
>
> /* connect PHY */
> ndev->phydev = of_phy_connect(emac->ndev, emac->phy_node,
> &emac_adjust_link, 0,
> PHY_INTERFACE_MODE_RGMII_RXID);
>
> Let me know if this looks OK.
No, this is not OK.
Please keep this as emac->phy_if.
In prueth_config_rgmiidelay(), you can change emac->phy_if to
PHY_INTERFACE_MODE_RGMII_RXID only if it was RGMII mode
*and* MAC TX delay was enabled.
cheers,
-roger
next prev parent reply other threads:[~2023-02-07 19:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 6:07 [PATCH v4 0/2] Introduce ICSSG based ethernet Driver MD Danish Anwar
2023-02-06 6:07 ` [PATCH v4 1/2] dt-bindings: net: Add ICSSG Ethernet Driver bindings MD Danish Anwar
2023-02-06 7:50 ` Krzysztof Kozlowski
2023-02-06 10:39 ` [EXTERNAL] " Md Danish Anwar
2023-02-06 10:41 ` Krzysztof Kozlowski
2023-02-07 5:07 ` Md Danish Anwar
2023-02-06 13:46 ` Rob Herring
2023-02-07 5:00 ` [EXTERNAL] " Md Danish Anwar
2023-02-06 6:07 ` [PATCH v4 2/2] net: ti: icssg-prueth: Add ICSSG ethernet driver MD Danish Anwar
2023-02-06 14:15 ` Andrew Lunn
2023-02-07 15:29 ` [EXTERNAL] " Md Danish Anwar
2023-02-07 19:56 ` Roger Quadros [this message]
2023-02-08 7:46 ` [EXTERNAL] " Md Danish Anwar
2023-02-08 9:17 ` Roger Quadros
2023-02-08 12:56 ` Andrew Lunn
2023-02-09 10:29 ` [EXTERNAL] " Md Danish Anwar
2023-02-09 12:58 ` Roger Quadros
2023-02-09 13:43 ` [EXTERNAL] " Md Danish Anwar
2023-02-09 13:54 ` Andrew Lunn
2023-02-10 6:26 ` [EXTERNAL] " Md Danish Anwar
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=e8158969-08d0-1edc-24be-8c300a71adbd@kernel.org \
--to=rogerq@kernel.org \
--cc=a0501179@ti.com \
--cc=afd@ti.com \
--cc=andrew@lunn.ch \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=srk@ti.com \
--cc=ssantosh@kernel.org \
--cc=vigneshr@ti.com \
--cc=yuehaibing@huawei.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).