[ARM] Orion: avoid setting ->force_phy_addr
The mv643xx_eth platform data field ->force_phy_addr only needs to be set if the passed-in ->phy_addr field is zero (to distinguish the case of not having specified a phy address (force_phy_addr = 0) from the case where a phy address of zero needs to be used (force_phy_addr = 1.)) Also, the ->force_phy_addr field will hopefully disappear in a future mv643xx_eth reorganisation. Therefore, this patch deletes the ->force_phy_addr field initialiser from all Orion board code. Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
This commit is contained in:

committed by
Lennert Buytenhek

父節點
b206ed0462
當前提交
2850a03773
@@ -222,7 +222,6 @@ subsys_initcall(rd88f5182_pci_init);
|
||||
|
||||
static struct mv643xx_eth_platform_data rd88f5182_eth_data = {
|
||||
.phy_addr = 8,
|
||||
.force_phy_addr = 1,
|
||||
};
|
||||
|
||||
/*****************************************************************************
|
||||
|
Reference in New Issue
Block a user