From: Anatolij Gustschin <agust@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/6] net: phy: mv88e61xx: rework to enable detection of 88E6071 devices
Date: Tue, 9 Jul 2019 10:13:20 +0200 [thread overview]
Message-ID: <20190709101320.7bfa5885@crub> (raw)
In-Reply-To: <CAFOYHZDNkzixY2o5ARQF6ixNU86-hB05QrJgQe_ziMqA-ME6_w@mail.gmail.com>
Hi Chris,
On Tue, 9 Jul 2019 19:34:37 +1200
Chris Packham judge.packham at gmail.com wrote:
> > priv->id = mv88e61xx_get_switch_id(phydev);
> > + debug("%s ID 0x%x\n", __func__, priv->id);
> > +
> > + switch (priv->id) {
> > + case PORT_SWITCH_ID_6172:
> > + case PORT_SWITCH_ID_6176:
> > + case PORT_SWITCH_ID_6240:
> > + case PORT_SWITCH_ID_6352:
>
> 6096 and 6097 are missing. These both have 11 ports (8x10/100M with
> integrated PHY and 3 x 1G with external PHY).
Thanks for review! I didn't notice it, will extend in v2 series.
Thanks,
Anatolij
next prev parent reply other threads:[~2019-07-09 8:13 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-08 13:03 [U-Boot] [PATCH 0/6] Extend mv88e61xx driver to support 88E6071 Anatolij Gustschin
2019-07-08 13:03 ` [U-Boot] [PATCH 1/6] net: phy: mv88e61xx: rework to enable detection of 88E6071 devices Anatolij Gustschin
2019-07-09 7:34 ` Chris Packham
2019-07-09 8:13 ` Anatolij Gustschin [this message]
2019-07-08 13:03 ` [U-Boot] [PATCH 2/6] net: phy: mv88e61xx: add CPU port parameter init for 88E6071 Anatolij Gustschin
2019-07-08 13:03 ` [U-Boot] [PATCH 3/6] net: phy: mv88E61xx: fix ENERGY_DET init for mv88E6071 Anatolij Gustschin
2019-07-08 13:03 ` [U-Boot] [PATCH 4/6] net: phy: mv88E61xx: add config option for mv88E6071 support Anatolij Gustschin
2019-07-08 13:03 ` [U-Boot] [PATCH 5/6] net: phy: mv88e61xx: register phy_driver struct for 88E6071 Anatolij Gustschin
2019-07-08 13:03 ` [U-Boot] [PATCH 6/6] net: phy: fix switch vendor name Anatolij Gustschin
2019-07-09 7:41 ` [U-Boot] [PATCH 0/6] Extend mv88e61xx driver to support 88E6071 Chris Packham
2019-07-09 8:17 ` Anatolij Gustschin
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=20190709101320.7bfa5885@crub \
--to=agust@denx.de \
--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.