net: phy: realtek: clear interrupt during init for rtl8211f
Subsystems (3)
PATCH 1/1 net: phy: realtek: clear interrupt during init for rtl8211f
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling rtl8211f_ack_interrupt().
--- drivers/net/phy/realtek.c | 4 ++++ 1 file changed, 4 insertions(+)
drivers/net/phy/realtek.c +4 -0
@@ -179,6 +179,10 @@ static int rtl8211f_config_init(struct phy_device *phydev)u16 val_txdly, val_rxdly;int ret; + ret =rtl8211f_ack_interrupt (phydev); +if (ret <0 ) +return ret; +switch (phydev->interface) {case PHY_INTERFACE_MODE_RGMII : val_txdly =0 ;
Signature · 1 line
2.26.2
Heiner Kallweit
maintainerQuoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().
As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice? I'm asking because you don't provide a Fixes tag and you don't annotate your patch as net or net-next.
Once you provide more details we would also get an idea whether a change would have to be made to phylib, because what you describe doesn't seem to be specific to this one PHY model.
Quoted 22 lines
Signed-off-by Jisheng Zhang <[email protected]>--- drivers/net/phy/realtek.c | 4 ++++ 1 file changed, 4 insertions(+)drivers/net/phy/realtek.c +4
-0@@ -179,6 +179,10 @@ static int rtl8211f_config_init(struct phy_device *phydev)u16 val_txdly, val_rxdly;int ret; + ret =rtl8211f_ack_interrupt (phydev); +if (ret <0 ) +return ret; +switch (phydev->interface) {case PHY_INTERFACE_MODE_RGMII : val_txdly =0 ;
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?
The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LAN
The PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.
Quoted 2 lines
I'm asking because you don't provide a Fixes tag and you don't annotate your patch as net or net-next.
should be Fixes: 3447cf2e9a11 ("net/phy: Add support for Realtek RTL8211F")
Quoted 3 lines
Once you provide more details we would also get an idea whether a change would have to be made to phylib, because what you describe doesn't seem to be specific to this one PHY model.
Nope, we don't need this change in phylib, this is specific to rtl8211f
Thanks,
Jisheng
Heiner Kallweit
maintainerQuoted 16 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?
Quoted 9 lines
The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the set_wol callback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB? One more thing to consider when implementing set_wol would be that the PHY supports two WOL options:
1. INT/PMEB configured as PMEB
2. INT/PMEB configured as INT and WOL interrupt source active
Quoted 6 lines
Quoted 3 lines
I'm asking because you don't provide a Fixes tag and you don't annotate your patch as net or net-next.
should be Fixes:
3447cf2e9a11("net/phy: Add support for Realtek RTL8211F")
Quoted 9 lines
Quoted 3 lines
Once you provide more details we would also get an idea whether a change would have to be made to phylib, because what you describe doesn't seem to be specific to this one PHY model.
Nope, we don't need this change in phylib, this is specific to rtl8211f
Thanks,
Jisheng
Heiner
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 16 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?Quoted 9 lines
The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?
I think it's better to switch the pin function in set_wol callback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?
Quoted 21 lines
One more thing to consider when implementing
set_wolwould be that the PHY supports two WOL options:
1. INT/PMEB configured as PMEB
2. INT/PMEB configured as INT and WOL interrupt source activeQuoted 6 lines
Quoted 3 lines
I'm asking because you don't provide a Fixes tag and you don't annotate your patch as net or net-next.
should be Fixes:
3447cf2e9a11("net/phy: Add support for Realtek RTL8211F")Quoted 9 lines
Quoted 3 lines
Once you provide more details we would also get an idea whether a change would have to be made to phylib, because what you describe doesn't seem to be specific to this one PHY model.
Nope, we don't need this change in phylib, this is specific to rtl8211f
Thanks,
JishengHeiner
Heiner Kallweit
maintainerQuoted 29 lines · Jisheng Zhang
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 25 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.
Quoted 9 lines
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?I think it's better to switch the pin function in
set_wolcallback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?
It shouldn't hurt (at least it didn't hurt for the last years), because no listener should listen to the pin w/o having it configured before. So better extend the PHY driver first (set_wol, ..), and then do the follow-up platform changes (e.g. DT config of a connected GPIO).
Quoted 22 lines
Quoted 21 lines
One more thing to consider when implementing
set_wolwould be that the PHY supports two WOL options:
1. INT/PMEB configured as PMEB
2. INT/PMEB configured as INT and WOL interrupt source activeQuoted 6 lines
Quoted 3 lines
I'm asking because you don't provide a Fixes tag and you don't annotate your patch as net or net-next.
should be Fixes:
3447cf2e9a11("net/phy: Add support for Realtek RTL8211F")Quoted 9 lines
Quoted 3 lines
Once you provide more details we would also get an idea whether a change would have to be made to phylib, because what you describe doesn't seem to be specific to this one PHY model.
Nope, we don't need this change in phylib, this is specific to rtl8211f
Thanks,
JishengHeiner
Quoted 42 lines · On Thu, 14 May 2020 21:50:53 +0200 Heiner Kallweit wrote:
Quoted 29 lines · Jisheng Zhang
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 25 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.Quoted 9 lines
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?I think it's better to switch the pin function in
set_wolcallback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?
Quoted 4 lines
It shouldn't hurt (at least it didn't hurt for the last years), because no listener should listen to the pin w/o having it configured before. So better extend the PHY driver first (
set_wol, ..), and then do the follow-up platform changes (e.g. DT config of a connected GPIO).
There are two sides involved here: the listener, it should not listen to the pin as you pointed out; the phy side, this patch tries to make the phy side behave normally -- not keep the INTB/PMEB pin always active. The listener side behaves correctly doesn't mean the phy side could keep the pin active.
When .set_wol isn't implemented, this patch could make the system suspend/resume work properly.
PS: even with set_wol implemented as configure the pin mode, I think we still need to clear the interrupt for phy poll mode either in set_wol or as this patch does.
Quoted 54 lines · Jisheng Zhang
Quoted 42 lines · On Thu, 14 May 2020 21:50:53 +0200 Heiner Kallweit wrote:
Quoted 29 lines · Jisheng Zhang
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 25 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.Quoted 9 lines
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?I think it's better to switch the pin function in
set_wolcallback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?Quoted 4 lines
It shouldn't hurt (at least it didn't hurt for the last years), because no listener should listen to the pin w/o having it configured before. So better extend the PHY driver first (
set_wol, ..), and then do the follow-up platform changes (e.g. DT config of a connected GPIO).There are two sides involved here: the listener, it should not listen to the pin as you pointed out; the phy side, this patch tries to make the phy side behave normally -- not keep the INTB/PMEB pin always active. The listener side behaves correctly doesn't mean the phy side could keep the pin active.
Quoted 6 lines
When .set_wol isn't implemented, this patch could make the system suspend/resume work properly.
PS: even with
set_wolimplemented as configure the pin mode, I think we still need to clear the interrupt for phy poll mode either inset_wolor as this patch does.
I agree with Jisheng here, Heiner, is there a reason you are pushing back on the change? Acknowledging prior interrupts while configuring the PHY is a common and established practice.
Signature · 1 line
Florian
Heiner Kallweit
maintainerQuoted 60 lines · Florian Fainelli
Quoted 57 lines · Jisheng Zhang
Quoted 42 lines · On Thu, 14 May 2020 21:50:53 +0200 Heiner Kallweit wrote:
Quoted 29 lines · Jisheng Zhang
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 25 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.Quoted 9 lines
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?I think it's better to switch the pin function in
set_wolcallback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?Quoted 4 lines
It shouldn't hurt (at least it didn't hurt for the last years), because no listener should listen to the pin w/o having it configured before. So better extend the PHY driver first (
set_wol, ..), and then do the follow-up platform changes (e.g. DT config of a connected GPIO).There are two sides involved here: the listener, it should not listen to the pin as you pointed out; the phy side, this patch tries to make the phy side behave normally -- not keep the INTB/PMEB pin always active. The listener side behaves correctly doesn't mean the phy side could keep the pin active.
When .set_wol isn't implemented, this patch could make the system suspend/resume work properly.
Quoted 8 lines
Quoted 3 lines
PS: even with
set_wolimplemented as configure the pin mode, I think we still need to clear the interrupt for phy poll mode either inset_wolor as this patch does.I agree with Jisheng here, Heiner, is there a reason you are pushing back on the change? Acknowledging prior interrupts while configuring the PHY is a common and established practice.
First it's about the justification of the change as such, and second about the question whether the change should be in the driver or in phylib.
Acking interrupts we do already if the PHY is configured for interrupt mode, we call phy_clear_interrupt() at the beginning of phy_enable_interrupts() and at the end of phy_disable_interrupts().
When using polling mode there is no strict need to ack interrupts. If we say however that interrupts should be acked in general, then I think it's not specific to RTL8211F, but it's something for phylib. Most likely we would have to add a call to phy_clear_interrupt() to phy_init_hw().
Quoted 74 lines · On Fri, 15 May 2020 19:30:38 +0200 Heiner Kallweit wrote:
Quoted 60 lines · Florian Fainelli
Quoted 57 lines · Jisheng Zhang
Quoted 42 lines · On Thu, 14 May 2020 21:50:53 +0200 Heiner Kallweit wrote:
Quoted 29 lines · Jisheng Zhang
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 25 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.Quoted 9 lines
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?I think it's better to switch the pin function in
set_wolcallback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?Quoted 4 lines
It shouldn't hurt (at least it didn't hurt for the last years), because no listener should listen to the pin w/o having it configured before. So better extend the PHY driver first (
set_wol, ..), and then do the follow-up platform changes (e.g. DT config of a connected GPIO).There are two sides involved here: the listener, it should not listen to the pin as you pointed out; the phy side, this patch tries to make the phy side behave normally -- not keep the INTB/PMEB pin always active. The listener side behaves correctly doesn't mean the phy side could keep the pin active.
When .set_wol isn't implemented, this patch could make the system suspend/resume work properly.
Quoted 8 lines
Quoted 3 lines
PS: even with
set_wolimplemented as configure the pin mode, I think we still need to clear the interrupt for phy poll mode either inset_wolor as this patch does.I agree with Jisheng here, Heiner, is there a reason you are pushing back on the change? Acknowledging prior interrupts while configuring the PHY is a common and established practice.
First it's about the justification of the change as such, and second about the question whether the change should be in the driver or in phylib.
Quoted 7 lines
Acking interrupts we do already if the PHY is configured for interrupt mode, we call
phy_clear_interrupt()at the beginning ofphy_enable_interrupts()and at the end ofphy_disable_interrupts().
When using polling mode there is no strict need to ack interrupts. If we say however that interrupts should be acked in general, then I think it's not specific to RTL8211F, but it's something for phylib. Most likely we would have to add a call tophy_clear_interrupt()tophy_init_hw().
it's specific to RTL8211F from the following two PoV:
1. the PIN is shared between INTB and PMEB.
2. the PHY Register Accessible Interrupt is enabled by default
I didn't see such behaviors with other PHYs.
Thanks
Heiner Kallweit
maintainerQuoted 85 lines · Jisheng Zhang
Quoted 74 lines · On Fri, 15 May 2020 19:30:38 +0200 Heiner Kallweit wrote:
Quoted 60 lines · Florian Fainelli
Quoted 57 lines · Jisheng Zhang
Quoted 42 lines · On Thu, 14 May 2020 21:50:53 +0200 Heiner Kallweit wrote:
Quoted 29 lines · Jisheng Zhang
Quoted 27 lines · On Wed, 13 May 2020 20:45:13 +0200 Heiner Kallweit wrote:
Quoted 25 lines · Jisheng Zhang
Hi,
Quoted 10 lines · On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
Quoted 4 lines · Jisheng Zhang
The PHY Register Accessible Interrupt is enabled by default, so there's such an interrupt during init. In PHY POLL mode case, the INTB/PMEB pin is alway active, it is not good. Clear the interrupt by calling
rtl8211f_ack_interrupt().As you say "it's not good" w/o elaborating a little bit more on it:
Do you face any actual issue? Or do you just think that it's not nice?The INTB/PMEB pin can be used in two different modes:
INTB: used for interrupt
PMEB: special mode for Wake-on-LANThe PHY Register Accessible Interrupt is enabled by
default, there's always such an interrupt during the init. In PHY POLL mode case, the pin is always active. If platforms plans to use the INTB/PMEB pin as WOL, then the platform will see WOL active. It's not good.Quoted 9 lines
Quoted 4 lines
The platform should listen to this pin only once WOL has been configured and the pin has been switched to PMEB function. For the latter you first would have to implement the
set_wolcallback in the PHY driver.
Or where in which code do you plan to switch the pin function to PMEB?I think it's better to switch the pin function in
set_wolcallback. But this is another story. No matter WOL has been configured or not, keeping the INTB/PMEB pin active is not good. what do you think?Quoted 4 lines
It shouldn't hurt (at least it didn't hurt for the last years), because no listener should listen to the pin w/o having it configured before. So better extend the PHY driver first (
set_wol, ..), and then do the follow-up platform changes (e.g. DT config of a connected GPIO).There are two sides involved here: the listener, it should not listen to the pin as you pointed out; the phy side, this patch tries to make the phy side behave normally -- not keep the INTB/PMEB pin always active. The listener side behaves correctly doesn't mean the phy side could keep the pin active.
When .set_wol isn't implemented, this patch could make the system suspend/resume work properly.
Quoted 8 lines
Quoted 3 lines
PS: even with
set_wolimplemented as configure the pin mode, I think we still need to clear the interrupt for phy poll mode either inset_wolor as this patch does.I agree with Jisheng here, Heiner, is there a reason you are pushing back on the change? Acknowledging prior interrupts while configuring the PHY is a common and established practice.
First it's about the justification of the change as such, and second about the question whether the change should be in the driver or in phylib.
Quoted 7 lines
Acking interrupts we do already if the PHY is configured for interrupt mode, we call
phy_clear_interrupt()at the beginning ofphy_enable_interrupts()and at the end ofphy_disable_interrupts().
When using polling mode there is no strict need to ack interrupts. If we say however that interrupts should be acked in general, then I think it's not specific to RTL8211F, but it's something for phylib. Most likely we would have to add a call tophy_clear_interrupt()tophy_init_hw().
Quoted 4 lines
it's specific to RTL8211F from the following two PoV:
1. the PIN is shared between INTB and PMEB.
2. the PHY Register Accessible Interrupt is enabled by default
If we clear the interrupt in config_init() and one interrupt source is active per chip default, then wouldn't the irq pin be active soon again?
I was thinking about calling phy_disable_interrupts() in phy_init_hw(), to have a defined init state, as we don't know in which state the PHY is if the PHY driver is loaded. We shouldn't assume that it's the chip power-on defaults, BIOS or boot loader could have changed this. Or in case of dual-boot systems the other OS could leave the PHY in whatever state.
This made me think about an issue we may have currently:
Interrupts are enabled in phy_request_interrupt() only. If the system hibernates, then PHY may load power-on defaults on restore. And mdio_bus_phy_restore() just calls phy_init_hw() and doesn't care about interrupt config. Means after waking up from hibernation we may have lost PHY interrupt config.
Quoted 4 lines
I didn't see such behaviors with other PHYs.
Thanks
Heiner