All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthias Fuchs <matthias.fuchs@esd-electronics.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] unhandled ethernet wakeup interrupt in 405 ethernet driver
Date: Fri, 06 May 2005 15:16:58 +0200	[thread overview]
Message-ID: <427B6E4A.9080402@esd-electronics.com> (raw)

Hi,

I noticed a networks problem with some of our 405EP platforms (u-boot 
config: PLU405). When doing tftp u-boot runs into an endless interrupt 
loop of the ethernet wakeup interrupt (VECNUM_EWU0).

So why is the wakeup interrupt enabled in 405gp_enet.c in general? The 
interrupt handler enetInt() does not care about this interrupt source at 
all. So when it occurs we end up in an interrupt loop. I found no hint 
about how to reset this interrupt in the 405EP manual.

When I do not install a handler on the wakeup interrupt source (EWU0) 
everything is fine. This is my current workaround.

The current 405 linux ethernet driver also does not attach to this 
interrupt.

I am astonished about two things:

1) The installation of the enetInt() handler for the wakeup interrupt is 
only done for 405EP platforms in ppc_4xx_eth_initialize():

#if defined(CONFIG_405EP)
			/* 405EP has one EWU interrupt */
			irq_install_handler (VECNUM_EWU0,
					     (interrupt_handler_t *) enetInt,
					     dev);
#endif

But it is not done for 405EP platforms in ppc_4xx_eth_init():

#if !defined(CONFIG_405EP)
		/* 405EP has one EWU interrupt */
		irq_install_handler (VECNUM_EWU0 + (hw_p->devnum * 2),
				     (interrupt_handler_t *) enetInt, dev);
#endif

This seems to be strange at all.

I suppose that no one is using the wakeup mechanism and so I propose to 
completely remove the wakeup stuff!


2) Why the hell do we get ethernet wakeup interrupts on some of our 
405EP boards :-(



So can we get rid of installing a wakeup interrupt that even does not 
handle the interrupt? If yes I will submit a patch.

Matthias

-- 
-------------------------------------------------------------------------

                             _/_/_/_/   Matthias Fuchs
                            _/_/_/_/   Dipl.-Ing.
                           _/_/_/_/   matthias.fuchs at esd-electronics.com

       _/_/_/   _/_/_/_/_/_/_/      esd electronic system design gmbh
     _/   _/  _/             _/    Vahrenwalder Str. 207
    _/   _/    _/_/_/   _/   _/   D-30165 Hannover
    _/             _/  _/   _/   Phone: +49-511-37298-0
     _/_/_/_/_/_/_/   _/_/_/    Fax:   +49-511-37298-68

-------------------------------------------------------------------------

             reply	other threads:[~2005-05-06 13:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-06 13:16 Matthias Fuchs [this message]
2005-05-10  8:23 ` [U-Boot-Users] unhandled ethernet wakeup interrupt in 405 ethernet driver Matthias Fuchs

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=427B6E4A.9080402@esd-electronics.com \
    --to=matthias.fuchs@esd-electronics.com \
    --cc=u-boot@lists.denx.de \
    /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.