From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Yibo Dong <dong100@mucse.com>
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
kuba@kernel.org, pabeni@redhat.com, horms@kernel.org,
corbet@lwn.net, gur.stavi@huawei.com, maddy@linux.ibm.com,
mpe@ellerman.id.au, danishanwar@ti.com, lee@trager.us,
gongfan1@huawei.com, lorenzo@kernel.org, geert+renesas@glider.be,
Parthiban.Veerasooran@microchip.com, lukas.bulwahn@redhat.com,
alexanderduyck@fb.com, richardcochran@gmail.com,
netdev@vger.kernel.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 5/5] net: rnpgbe: Add register_netdev
Date: Wed, 13 Aug 2025 13:50:34 +0100 [thread overview]
Message-ID: <354593d1-2504-407e-98fb-235fcaf61d87@linux.dev> (raw)
In-Reply-To: <B41E833713021188+20250813090405.GC965498@nic-Precision-5820-Tower>
On 13/08/2025 10:04, Yibo Dong wrote:
> On Tue, Aug 12, 2025 at 04:32:00PM +0100, Vadim Fedorenko wrote:
>> On 12/08/2025 10:39, Dong Yibo wrote:
>>> Initialize get mac from hw, register the netdev.
>>>
>>> Signed-off-by: Dong Yibo <dong100@mucse.com>
>>> ---
>>> drivers/net/ethernet/mucse/rnpgbe/rnpgbe.h | 22 ++++++
>>> .../net/ethernet/mucse/rnpgbe/rnpgbe_chip.c | 73 ++++++++++++++++++
>>> drivers/net/ethernet/mucse/rnpgbe/rnpgbe_hw.h | 1 +
>>> .../net/ethernet/mucse/rnpgbe/rnpgbe_main.c | 76 +++++++++++++++++++
>>> 4 files changed, 172 insertions(+)
>>>
>>> diff --git a/drivers/net/ethernet/mucse/rnpgbe/rnpgbe.h b/drivers/net/ethernet/mucse/rnpgbe/rnpgbe.h
>>> index 6cb14b79cbfe..644b8c85c29d 100644
>>> --- a/drivers/net/ethernet/mucse/rnpgbe/rnpgbe.h
>>> +++ b/drivers/net/ethernet/mucse/rnpgbe/rnpgbe.h
>>> @@ -6,6 +6,7 @@
>>> #include <linux/types.h>
>>> #include <linux/mutex.h>
>>> +#include <linux/netdevice.h>
>>> extern const struct rnpgbe_info rnpgbe_n500_info;
>>> extern const struct rnpgbe_info rnpgbe_n210_info;
>>> @@ -86,6 +87,18 @@ struct mucse_mbx_info {
>>> u32 fw2pf_mbox_vec;
>>> };
>>> +struct mucse_hw_operations {
>>> + int (*init_hw)(struct mucse_hw *hw);
>>> + int (*reset_hw)(struct mucse_hw *hw);
>>> + void (*start_hw)(struct mucse_hw *hw);
>>> + void (*init_rx_addrs)(struct mucse_hw *hw);
>>> + void (*driver_status)(struct mucse_hw *hw, bool enable, int mode);
>>> +};
>>> +
>>> +enum {
>>> + mucse_driver_insmod,
>>> +};
>>> +
>>> struct mucse_hw {
>>> void *back;
>>> u8 pfvfnum;
>>> @@ -96,12 +109,18 @@ struct mucse_hw {
>>> u32 axi_mhz;
>>> u32 bd_uid;
>>> enum rnpgbe_hw_type hw_type;
>>> + const struct mucse_hw_operations *ops;
>>> struct mucse_dma_info dma;
>>> struct mucse_eth_info eth;
>>> struct mucse_mac_info mac;
>>> struct mucse_mbx_info mbx;
>>> + u32 flags;
>>> +#define M_FLAGS_INIT_MAC_ADDRESS BIT(0)
>>> u32 driver_version;
>>> u16 usecstocount;
>>> + int lane;
>>> + u8 addr[ETH_ALEN];
>>> + u8 perm_addr[ETH_ALEN];
>>
>> why do you need both addresses if you have this info already in netdev?
>>
>
> 'perm_addr' is address from firmware (fixed, can't be changed by user).
> 'addr' is the current netdev address (It is Initialized the same with
> 'perm_addr', but can be changed by user)
> Maybe I should add 'addr' in the patch which support ndo_set_mac_address?
But why do you need 'addr' at all? Current netdev address can be
retrieved from netdev, why do you need to store it within driver's
structure?
next prev parent reply other threads:[~2025-08-13 12:51 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-12 9:39 [PATCH v3 0/5] Add driver for 1Gbe network chips from MUCSE Dong Yibo
2025-08-12 9:39 ` [PATCH v3 1/5] net: rnpgbe: Add build support for rnpgbe Dong Yibo
2025-08-12 15:37 ` Vadim Fedorenko
2025-08-13 6:18 ` Yibo Dong
2025-08-12 16:18 ` Anwar, Md Danish
2025-08-13 6:44 ` Yibo Dong
2025-08-13 7:51 ` MD Danish Anwar
2025-08-13 8:00 ` Yibo Dong
2025-08-12 9:39 ` [PATCH v3 2/5] net: rnpgbe: Add n500/n210 chip support Dong Yibo
2025-08-12 15:49 ` Vadim Fedorenko
2025-08-13 7:01 ` Yibo Dong
2025-08-12 16:25 ` Anwar, Md Danish
2025-08-13 7:07 ` Yibo Dong
2025-08-12 9:39 ` [PATCH v3 3/5] net: rnpgbe: Add basic mbx ops support Dong Yibo
2025-08-12 16:07 ` Vadim Fedorenko
2025-08-12 16:30 ` Anwar, Md Danish
2025-08-13 7:46 ` Yibo Dong
2025-08-14 23:55 ` Andrew Lunn
2025-08-15 1:31 ` Yibo Dong
2025-08-15 4:07 ` Andrew Lunn
2025-08-12 9:39 ` [PATCH v3 4/5] net: rnpgbe: Add basic mbx_fw support Dong Yibo
2025-08-12 16:14 ` Vadim Fedorenko
2025-08-13 8:12 ` Yibo Dong
2025-08-13 9:52 ` Yibo Dong
2025-08-13 11:05 ` Geert Uytterhoeven
2025-08-13 21:32 ` Jakub Kicinski
2025-08-13 13:33 ` Vadim Fedorenko
2025-08-14 1:53 ` Yibo Dong
2025-08-15 0:04 ` Andrew Lunn
2025-08-15 1:36 ` Yibo Dong
2025-08-13 8:20 ` MD Danish Anwar
2025-08-13 9:24 ` Yibo Dong
2025-08-12 9:39 ` [PATCH v3 5/5] net: rnpgbe: Add register_netdev Dong Yibo
2025-08-12 15:32 ` Vadim Fedorenko
2025-08-13 9:04 ` Yibo Dong
2025-08-13 12:50 ` Vadim Fedorenko [this message]
2025-08-14 1:52 ` Yibo Dong
2025-08-13 8:26 ` MD Danish Anwar
2025-08-13 9:49 ` Yibo Dong
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=354593d1-2504-407e-98fb-235fcaf61d87@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=Parthiban.Veerasooran@microchip.com \
--cc=alexanderduyck@fb.com \
--cc=andrew+netdev@lunn.ch \
--cc=corbet@lwn.net \
--cc=danishanwar@ti.com \
--cc=davem@davemloft.net \
--cc=dong100@mucse.com \
--cc=edumazet@google.com \
--cc=geert+renesas@glider.be \
--cc=gongfan1@huawei.com \
--cc=gur.stavi@huawei.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=lee@trager.us \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=maddy@linux.ibm.com \
--cc=mpe@ellerman.id.au \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=richardcochran@gmail.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).