On 06/14/2016 04:56 PM, Sergei Shtylyov wrote:
On 06/15/2016 12:53 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
On 06/14/2016 05:26 PM, Andrew Lunn wrote:
This was DT as well with a recent fedora/NetworkManager. It
actually seems to be timing related to how fast the device gets
configured after the initial phy probe. There is something like a 1
second window or so where it will work, but if
> This was DT as well with a recent fedora/NetworkManager. It
> actually seems to be timing related to how fast the device gets
> configured after the initial phy probe. There is something like a 1
> second window or so where it will work, but if network manager takes
> longer than that, the
On 06/15/2016 12:53 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
What address your internal PHY is at? Mine is at
On 06/14/2016 04:42 PM, Sergei Shtylyov wrote:
On 06/15/2016 12:40 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
On 06/15/2016 12:40 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
What address your internal PHY is at? Mine is at
On 06/14/2016 04:34 PM, Sergei Shtylyov wrote:
On 06/15/2016 12:29 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
On 06/15/2016 12:29 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
What address your internal PHY is at? Mine is at
On 06/14/2016 03:44 PM, Sergei Shtylyov wrote:
On 06/14/2016 07:16 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
On 06/15/2016 12:12 AM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
AFAIK, I think that its set when the device is configured as a platform
device, or there is an external phy/interrupt setup in DT. I
On 06/14/2016 11:59 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
What address your internal PHY is at? Mine is at
On 06/14/2016 03:44 PM, Sergei Shtylyov wrote:
On 06/14/2016 07:16 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
AFAIK, I think that its set when the device is configured as a platform
device, or
On 06/14/2016 03:44 PM, Sergei Shtylyov wrote:
On 06/14/2016 07:16 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
On 06/14/2016 03:44 PM, Sergei Shtylyov wrote:
On 06/14/2016 07:16 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
On 06/14/2016 01:42 PM, Andrew Lunn wrote:
On Tue, Jun 14, 2016 at 11:16:02AM -0500, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Hi Jeremy
Why does the external phy not
On 06/14/2016 07:16 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
It's never set, judging by the driver code.
internal phy, then we need to poll the phy to reliably detect
phy state changes.
What address your internal PHY is at? Mine is at 1,
On 06/14/2016 11:12 PM, Andrew Lunn wrote:
On Tue, Jun 14, 2016 at 10:49:20PM +0300, Sergei Shtylyov wrote:
On 06/14/2016 10:27 PM, Sergei Shtylyov wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state
On 06/14/2016 02:49 PM, Sergei Shtylyov wrote:
On 06/14/2016 10:27 PM, Sergei Shtylyov wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Signed-off-by: Jeremy Linton
---
On Tue, Jun 14, 2016 at 10:49:20PM +0300, Sergei Shtylyov wrote:
> On 06/14/2016 10:27 PM, Sergei Shtylyov wrote:
>
> >>>If the interrupt configuration isn't set and we are using the
> >>>internal phy, then we need to poll the phy to reliably detect
> >>>phy state changes.
> >>>
>
On 06/14/2016 10:27 PM, Sergei Shtylyov wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Signed-off-by: Jeremy Linton
---
drivers/net/ethernet/smsc/smsc911x.c | 3 +++
On 06/14/2016 09:30 PM, Sergei Shtylyov wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Signed-off-by: Jeremy Linton
---
drivers/net/ethernet/smsc/smsc911x.c | 3 +++
On Tue, Jun 14, 2016 at 11:16:02AM -0500, Jeremy Linton wrote:
> If the interrupt configuration isn't set and we are using the
> internal phy, then we need to poll the phy to reliably detect
> phy state changes.
Hi Jeremy
Why does the external phy not have the exact same problem?
Andrew
On 06/14/2016 07:16 PM, Jeremy Linton wrote:
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Signed-off-by: Jeremy Linton
---
drivers/net/ethernet/smsc/smsc911x.c | 3 +++
1
If the interrupt configuration isn't set and we are using the
internal phy, then we need to poll the phy to reliably detect
phy state changes.
Signed-off-by: Jeremy Linton
---
drivers/net/ethernet/smsc/smsc911x.c | 3 +++
1 file changed, 3 insertions(+)
diff --git
24 matches
Mail list logo