net: hns3: fix a bug when getting phy address from NCL_config file
Driver gets phy address from NCL_config file and uses the phy address
to initialize phydev. There are 5 bits for phy address. And C22 phy
address has 5 bits. So 0-31 are all valid address for phy. If there
is no phy, it will crash. Because driver always get a valid phy address.
This patch fixes the phy address to 8 bits, and use 0xff to indicate
invalid phy address.
Fixes: 46a3df9f97
(net: hns3: Add HNS3 Acceleration Engine & Compatibility Layer Support)
Signed-off-by: Fuyun Liang <liangfuyun1@huawei.com>
Signed-off-by: Lipeng <lipeng321@huawei.com>
Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
parent
28033ae4e0
commit
39e2151f10
|
@ -390,7 +390,7 @@ struct hclge_pf_res_cmd {
|
|||
#define HCLGE_CFG_TQP_DESC_N_S 16
|
||||
#define HCLGE_CFG_TQP_DESC_N_M GENMASK(31, 16)
|
||||
#define HCLGE_CFG_PHY_ADDR_S 0
|
||||
#define HCLGE_CFG_PHY_ADDR_M GENMASK(4, 0)
|
||||
#define HCLGE_CFG_PHY_ADDR_M GENMASK(7, 0)
|
||||
#define HCLGE_CFG_MEDIA_TP_S 8
|
||||
#define HCLGE_CFG_MEDIA_TP_M GENMASK(15, 8)
|
||||
#define HCLGE_CFG_RX_BUF_LEN_S 16
|
||||
|
|
Loading…
Reference in New Issue