diff options
author | David S. Miller <davem@davemloft.net> | 2020-06-24 14:52:49 -0700 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2020-06-24 14:52:49 -0700 |
commit | 482f3bae5bf33522041590c0fde51c3e9651349f (patch) | |
tree | 5399a6c3e32d842c96e657c01a6431f40ce587d8 /crypto/asymmetric_keys | |
parent | 41c2b6b4f0f807803bb49f65835d136941a70f85 (diff) | |
parent | 9886a4dbd2aacf4b044e294e4cdebb43992d44b1 (diff) |
Merge branch 'net-phy-call-phy_disable_interrupts-in-phy_init_hw'
Jisheng Zhang says:
====================
net: phy: call phy_disable_interrupts() in phy_init_hw()
We face an issue with rtl8211f, a pin is shared between INTB and PMEB,
and the PHY Register Accessible Interrupt is enabled by default, so
the INTB/PMEB pin is always active in polling mode case.
As Heiner pointed out "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."
patch1 makes phy_disable_interrupts() non-static so that it could be used
in phy_init_hw() to have a defined init state.
patch2 calls phy_disable_interrupts() in phy_init_hw() to have a
defined init state.
Since v3:
- call phy_disable_interrupts() have interrupts disabled first then
config_init, thank Florian
Since v2:
- Don't export phy_disable_interrupts() but just make it non-static
Since v1:
- EXPORT the correct symbol
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/asymmetric_keys')
0 files changed, 0 insertions, 0 deletions