From: 王颢 <howard_wang@realsil.com.cn>
To: Ferruh Yigit <ferruh.yigit@amd.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "pro_nic_dpdk@realtek.com" <pro_nic_dpdk@realtek.com>
Subject: 答复: [PATCH v6 08/17] net/r8169: add support for phy configuration
Date: Mon, 11 Nov 2024 08:18:48 +0000 [thread overview]
Message-ID: <9b59f9b4ca364500afe34cc0cf0485f5@realsil.com.cn> (raw)
In-Reply-To: <606cd6b0-6c68-4dd0-aa1b-e9b7fb1c3ee1@amd.com>
Dear Ferruh,
Regarding the commit message, I will think about how to write it.
I’m sorry, but for the registers in the PMD that do not use macro definitions, most of them are company confidential and their meanings will not be disclosed to the public. This part will be maintained by us.
Best Regards,
Howard Wang
-----邮件原件-----
发件人: Ferruh Yigit <ferruh.yigit@amd.com>
发送时间: 2024年11月11日 8:17
收件人: 王颢 <howard_wang@realsil.com.cn>; dev@dpdk.org
抄送: pro_nic_dpdk@realtek.com
主题: Re: [PATCH v6 08/17] net/r8169: add support for phy configuration
External mail.
On 11/8/2024 12:11 PM, Howard Wang wrote:
> This patch contains phy config, ephy config and so on.
>
> Signed-off-by: Howard Wang <howard_wang@realsil.com.cn>
>
<...>
> @@ -62,6 +62,12 @@ rtl_dev_start(struct rte_eth_dev *dev)
> struct rtl_hw *hw = &adapter->hw;
> int err;
>
> + rtl_powerup_pll(hw);
> +
> + rtl_hw_ephy_config(hw);
> +
> + rtl_hw_phy_config(hw);
> +
> rtl_hw_config(hw);
>
> /* Initialize transmission unit */ @@ -74,6 +80,8 @@
> rtl_dev_start(struct rte_eth_dev *dev)
> goto error;
> }
>
> + rtl_mdio_write(hw, 0x1F, 0x0000);
> +
>
It is very hard know what code like above does, which makes harder for anyone to read and understand your code, can you please either create macros for registers or comment as much as possible, so others can improve/fix your code when required.
next prev parent reply other threads:[~2024-11-11 8:18 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-08 12:11 [PATCH v6 00/17] Modify code as suggested by the maintainer Howard Wang
2024-11-08 12:11 ` [PATCH v6 01/17] net/r8169: add PMD driver skeleton Howard Wang
2024-11-08 15:58 ` Stephen Hemminger
2024-11-11 0:14 ` Ferruh Yigit
2024-11-11 3:46 ` 答复: " 王颢
2024-11-11 9:08 ` Ferruh Yigit
2024-11-11 9:24 ` 答复: " 王颢
2024-11-11 9:31 ` Ferruh Yigit
2024-11-08 12:11 ` [PATCH v6 02/17] net/r8169: add logging structure Howard Wang
2024-11-08 12:11 ` [PATCH v6 03/17] net/r8169: add hardware registers access routines Howard Wang
2024-11-08 12:11 ` [PATCH v6 04/17] net/r8169: implement core logic for Tx/Rx Howard Wang
2024-11-08 12:11 ` [PATCH v6 05/17] net/r8169: add support for hw config Howard Wang
2024-11-11 0:15 ` Ferruh Yigit
2024-11-11 9:44 ` 答复: " 王颢
2024-11-08 12:11 ` [PATCH v6 06/17] net/r8169: add phy registers access routines Howard Wang
2024-11-08 12:11 ` [PATCH v6 07/17] net/r8169: add support for hardware operations Howard Wang
2024-11-08 12:11 ` [PATCH v6 08/17] net/r8169: add support for phy configuration Howard Wang
2024-11-11 0:16 ` Ferruh Yigit
2024-11-11 8:18 ` 王颢 [this message]
2024-11-11 9:21 ` 答复: " Ferruh Yigit
2024-11-08 12:11 ` [PATCH v6 09/17] net/r8169: add support for hw initialization Howard Wang
2024-11-11 0:16 ` Ferruh Yigit
2024-11-08 12:11 ` [PATCH v6 10/17] net/r8169: add link status and interrupt management Howard Wang
2024-11-08 12:11 ` [PATCH v6 11/17] net/r8169: implement Rx path Howard Wang
2024-11-11 0:20 ` Ferruh Yigit
2024-11-08 12:11 ` [PATCH v6 12/17] net/r8169: implement Tx path Howard Wang
2024-11-11 0:20 ` Ferruh Yigit
2024-11-08 12:11 ` [PATCH v6 13/17] net/r8169: implement device statistics Howard Wang
2024-11-11 0:21 ` Ferruh Yigit
2024-11-08 12:11 ` [PATCH v6 14/17] net/r8169: implement promisc and allmulti modes Howard Wang
2024-11-08 12:11 ` [PATCH v6 15/17] net/r8169: implement MTU configuration Howard Wang
2024-11-08 12:11 ` [PATCH v6 16/17] net/r8169: add support for getting fw version Howard Wang
2024-11-08 12:11 ` [PATCH v6 17/17] net/r8169: add driver_start and driver_stop Howard Wang
2024-11-11 0:26 ` [PATCH v6 00/17] Modify code as suggested by the maintainer Ferruh Yigit
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=9b59f9b4ca364500afe34cc0cf0485f5@realsil.com.cn \
--to=howard_wang@realsil.com.cn \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=pro_nic_dpdk@realtek.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).