On Thu, Jun 01, 2017 at 10:28:04AM -0700, Florian Fainelli wrote:
> On 06/01/2017 03:26 AM, Russell King wrote:
> > Add phylib support for the Marvell Alaska X 10 Gigabit PHY (MV88X3310).
> > This phy is able to operate at 10G, 1G, 100M and 10M speeds, and only
> > supports Clause 45 accesses.
> >
On 06/01/2017 03:26 AM, Russell King wrote:
> Add phylib support for the Marvell Alaska X 10 Gigabit PHY (MV88X3310).
> This phy is able to operate at 10G, 1G, 100M and 10M speeds, and only
> supports Clause 45 accesses.
>
> The PHY appears (based on the vendor IDs) to be two different vendors
> I
On Thu, Jun 01, 2017 at 02:51:50PM +0200, Andrew Lunn wrote:
> > +static int mv3310_read_status(struct phy_device *phydev)
> > +{
> > + u32 mmd_mask = phydev->c45_ids.devices_in_package;
> > + int val;
> > +
> > + /* The vendor devads do not report link status. Avoid the PHYXS
> > +* ins
> +static int mv3310_read_status(struct phy_device *phydev)
> +{
> + u32 mmd_mask = phydev->c45_ids.devices_in_package;
> + int val;
> +
> + /* The vendor devads do not report link status. Avoid the PHYXS
> + * instance as there are three, and its status depends on the MAC
> +
Add phylib support for the Marvell Alaska X 10 Gigabit PHY (MV88X3310).
This phy is able to operate at 10G, 1G, 100M and 10M speeds, and only
supports Clause 45 accesses.
The PHY appears (based on the vendor IDs) to be two different vendors
IP, with each devad containing several instances.
This P
