All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Woojung.Huh@microchip.com
Cc: marc.zyngier@arm.com, eric@anholt.net, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	UNGLinuxDriver@microchip.com
Subject: RE: lan78xx: WARNING: irq 79 handler enabled interrupts
Date: Tue, 1 Jan 2019 22:31:47 +0100 (CET)	[thread overview]
Message-ID: <958035754.310420.1546378307673@email.ionos.de> (raw)
In-Reply-To: <BN6PR1101MB21305BBBB3F617C9C49141E4E7B10@BN6PR1101MB2130.namprd11.prod.outlook.com>

Hi Woojung,

> Woojung.Huh@microchip.com hat am 30. Dezember 2018 um 04:25 geschrieben:
> 
> 
> HI Marc & Stephen,
> 
> Most of engineers are out until New Year's Day.

thanks. I didn't expect a reply that fast.

>  
> LAN78xx driver uses irq_domain for phy interrupt, but smsc95xx uses polling.
> Need to check flow again, you can try that comment out "lan78xx_setup_irq_domain" to
> make dev->domain_data.phyirq = 0 which forces PHY polling.

I tested your suggestion with multi_v7_defconfig (32 bit) and arm64/defconfig.
The warning disappeared and Ethernet is still working.

Only the old issue that we can't receive until a first packet has been send out reappear. But this should be manageable.

>  
> Can you share if this is filed on RPI forum?

I didn't submit this to the raspberrypi.org forum / github. They mostly care about the next LTS release 4.19 and not really about arm64.

But an Arch Linux user (aarch64 using Mainline kernel) already discovered this issue:
https://archlinuxarm.org/forum/viewtopic.php?f=65&t=13302

> Also, it would be appreciated if you can create a ticket on Microchip site at
> https://www.microchip.com/technical-support/hot-topics

Done

Best regards
Stefan

> 
> Best Regards,
> Woojung
>

WARNING: multiple messages have this Message-ID (diff)
From: Stefan Wahren <stefan.wahren@i2se.com>
To: Woojung.Huh@microchip.com
Cc: marc.zyngier@arm.com, eric@anholt.net, netdev@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	UNGLinuxDriver@microchip.com
Subject: RE: lan78xx: WARNING: irq 79 handler enabled interrupts
Date: Tue, 1 Jan 2019 22:31:47 +0100 (CET)	[thread overview]
Message-ID: <958035754.310420.1546378307673@email.ionos.de> (raw)
In-Reply-To: <BN6PR1101MB21305BBBB3F617C9C49141E4E7B10@BN6PR1101MB2130.namprd11.prod.outlook.com>

Hi Woojung,

> Woojung.Huh@microchip.com hat am 30. Dezember 2018 um 04:25 geschrieben:
> 
> 
> HI Marc & Stephen,
> 
> Most of engineers are out until New Year's Day.

thanks. I didn't expect a reply that fast.

>  
> LAN78xx driver uses irq_domain for phy interrupt, but smsc95xx uses polling.
> Need to check flow again, you can try that comment out "lan78xx_setup_irq_domain" to
> make dev->domain_data.phyirq = 0 which forces PHY polling.

I tested your suggestion with multi_v7_defconfig (32 bit) and arm64/defconfig.
The warning disappeared and Ethernet is still working.

Only the old issue that we can't receive until a first packet has been send out reappear. But this should be manageable.

>  
> Can you share if this is filed on RPI forum?

I didn't submit this to the raspberrypi.org forum / github. They mostly care about the next LTS release 4.19 and not really about arm64.

But an Arch Linux user (aarch64 using Mainline kernel) already discovered this issue:
https://archlinuxarm.org/forum/viewtopic.php?f=65&t=13302

> Also, it would be appreciated if you can create a ticket on Microchip site at
> https://www.microchip.com/technical-support/hot-topics

Done

Best regards
Stefan

> 
> Best Regards,
> Woojung
>

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2019-01-01 21:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-29  0:02 lan78xx: WARNING: irq 79 handler enabled interrupts Stefan Wahren
2018-12-29  0:02 ` Stefan Wahren
2018-12-29  9:41 ` Marc Zyngier
2018-12-29  9:41   ` Marc Zyngier
2018-12-30  3:25   ` Woojung.Huh
2018-12-30  3:25     ` Woojung.Huh
2019-01-01 21:31     ` Stefan Wahren [this message]
2019-01-01 21:31       ` Stefan Wahren
2019-01-02 21:42       ` Woojung.Huh
2019-01-02 21:42         ` Woojung.Huh
2019-02-05 19:57       ` Stefan Wahren
2019-02-05 19:57         ` Stefan Wahren

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=958035754.310420.1546378307673@email.ionos.de \
    --to=stefan.wahren@i2se.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=Woojung.Huh@microchip.com \
    --cc=eric@anholt.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=marc.zyngier@arm.com \
    --cc=netdev@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.