From: Armin Kuster <akuster@mvista.com>
To: Kent Borg <kentborg@borg.org>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] New PHY for ppc405_phy.c
Date: Thu, 29 Nov 2001 09:28:59 -0800 [thread overview]
Message-ID: <3C06705B.15147A92@mvista.com> (raw)
In-Reply-To: 20011129110530.E3091@borg.org
Kent Borg wrote:
>
> I hope I am sending this to the right place, someone please correct me
> if I am doing this wrong...
>
> Our 405 board has a different PHY from those supported in the current
> sources, the following patch makes our PHY work. If it looks
> sensible, please apply.
>
> Thanks,
>
> -kb
>
> --- linuxppc_2_4_devel/drivers/net/ppc405_phy.c Thu Nov 29 10:34:53 2001
> +++ linux-penguinppc4/drivers/net/ppc405_phy.c Thu Nov 29 10:48:07 2001
> @@ -579,6 +579,75 @@
> },
> };
>
> +/* ------------------------------------------------------------------------- */
> +/* The Lucent Technologies LU3X31FT */
> +
> +/* register definitions */
> +
> +#define MII_LU3X31FT_PHYCTRLSTS 0x17 /* PHY Control/Status Register */
> +#define MII_LU3X31FT_IER 0x1D /* PHY interrupt enable Register */
> +#define MII_LU3X31FT_ISR 0x1E /* PHY interrupt status Register */
> +
> +static void mii_parse_lu3x31ft_pcr(uint mii_reg, struct net_device *dev)
> +{
> + struct fec_enet_private *fep = dev->priv;
> + volatile uint *s = &(fep->phy_status);
> +
> + *s &= ~(PHY_STAT_SPMASK);
> +
> + switch((mii_reg >> 8) & 3) {
> + case 0:
> + *s |= PHY_STAT_10HDX;
> + break;
> + case 1:
> + *s |= PHY_STAT_10FDX;
> + break;
> + case 2:
> + *s |= PHY_STAT_100HDX;
> + break;
> + case 3:
> + *s |= PHY_STAT_100FDX;
> + break;
> + }
> +}
> +
> +static phy_info_t phy_info_lu3x31ft = {
> + 0x90307421,
> + "LU3X31FT",
> + 0,
> + (const phy_cmd_t []) { /* config */
> +
> + /* parse cr and anar to get some info */
> +
> + { mk_mii_read(MII_REG_CR), mii_parse_cr },
> + { mk_mii_read(MII_REG_ANAR), mii_parse_anar },
> + { mk_mii_end, }
> + },
> + (const phy_cmd_t []) { /* startup - enable interrupts */
> + { mk_mii_write(MII_LU3X31FT_IER, 0x0000), NULL },
> + { mk_mii_write(MII_REG_CR, PHY_BMCR_RST_NEG), NULL }, /* autonegotiate */
> + { mk_mii_end, }
> + },
> + ( const phy_cmd_t []) { /* ack_int */
> +
> + /* we need to read ISR, SR and ANER to acknowledge */
> +
> + { mk_mii_read(MII_LU3X31FT_ISR), NULL },
> + { mk_mii_read(MII_REG_SR), mii_parse_sr },
> + { mk_mii_read(MII_REG_ANAR), mii_parse_anar },
> +
> + /* read pcr to get info */
> +
> + { mk_mii_read(MII_LU3X31FT_PHYCTRLSTS), mii_parse_lu3x31ft_pcr },
> + { mk_mii_end, }
> + },
> + ( const phy_cmd_t []) { /* shutdown - disable interrupts */
> + { mk_mii_write(MII_LU3X31FT_IER, 0xff80), NULL },
> + { mk_mii_end, }
> + },
> +};
> +
> +
>
> /* ------------------------------------------------------------------------- */
> /* The AMD Am79C875*/
> @@ -659,6 +728,7 @@
> &phy_info_lxt971a,
> &phy_info_cs8952,
> &phy_info_dp83846A,
> + &phy_info_lu3x31ft,
> &phy_info_Am79C875,
> NULL
> };
>
Thanks,
-- armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-11-29 17:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-29 16:05 [PATCH] New PHY for ppc405_phy.c Kent Borg
2001-11-29 16:41 ` Tom Rini
2001-11-29 17:28 ` Armin Kuster [this message]
2001-12-03 17:00 ` Debugging message through FDC37C672-COM of MBX860?? Okehee Goh
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=3C06705B.15147A92@mvista.com \
--to=akuster@mvista.com \
--cc=kentborg@borg.org \
--cc=linuxppc-embedded@lists.linuxppc.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.