From: "Joakim Tjernlund" <joakim.tjernlund@transmode.se>
To: "'Andy Fleming'" <afleming@freescale.com>
Cc: linuxppc-dev@ozlabs.org, 'Jeff Garzik' <jgarzik@pobox.com>
Subject: RE: [PATCH] Slight refactor of interrupt mapping for FSL parts
Date: Fri, 20 Oct 2006 00:40:11 +0200 [thread overview]
Message-ID: <02d901c6f3cf$8952e990$1267a8c0@Jocke> (raw)
In-Reply-To: <E86BE632-0841-4572-BE65-C308B0E0BF78@freescale.com>
>
> On Oct 16, 2006, at 16:51, Joakim Tjernlund wrote:
>
> >>> -#define PHY_POLL -1
> >>> +#define PHY_POLL NO_IRQ
> >>> #define PHY_IGNORE_INTERRUPT -2
> >
> > What does PHY_IGNORE_INTERRUPT mean? Can I use that in a dummy PHY
> > driver that just pretends that all is well? Got a ethernet port that
> > is connect to a switch directly over MII.
> > How do I express -2 in a dts file?
>
>
> PHY_IGNORE_INTERRUPT means that the PHY Lib will not poll the
> interface, nor will it register for the interrupt. Actually, it
> would be best for a dummy PHY driver. Take a look at the driver in
> drivers/phy/fixed.c. It's there to provide that kind of interface.
> It looks like it uses -1, which is a problem, but my revision
> of this
> patch will fix that.
Great, thanks. I don't see how to connect this PHY to ucc_geth driver yet. I think
it needs some PHY work first.
Maybe this patch,http://ozlabs.org/pipermail/linuxppc-dev/2006-October/026690.html, will make it better?
Why hasn't it been applied yet?
Jocke
next prev parent reply other threads:[~2006-10-19 22:40 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 20:57 [PATCH] Slight refactor of interrupt mapping for FSL parts Andy Fleming
2006-10-16 21:37 ` Kumar Gala
2006-10-16 21:51 ` Joakim Tjernlund
2006-10-18 13:50 ` Vitaly Bordug
2006-10-19 19:14 ` Andy Fleming
2006-10-19 22:40 ` Joakim Tjernlund [this message]
2006-10-20 0:54 ` Andy Fleming
2006-10-16 21:54 ` Kumar Gala
2006-10-16 22:58 ` Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2006-10-17 6:27 Andy Fleming
2006-10-17 15:50 ` Kumar Gala
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='02d901c6f3cf$8952e990$1267a8c0@Jocke' \
--to=joakim.tjernlund@transmode.se \
--cc=afleming@freescale.com \
--cc=jgarzik@pobox.com \
--cc=linuxppc-dev@ozlabs.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox