[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87a8ag2mxx.fsf@free-electrons.com>
Date: Tue, 24 Jan 2017 22:00:10 +0100
From: Gregory CLEMENT <gregory.clement@...e-electrons.com>
To: Vivien Didelot <vivien.didelot@...oirfairelinux.com>
Cc: Andrew Lunn <andrew@...n.ch>, David Miller <davem@...emloft.net>,
netdev <netdev@...r.kernel.org>
Subject: Re: [PATCH net-next 5/8] net: dsa: mv88e6xxx: Workaround missing PHY ID on mv88e6390
Hi Vivien,
On sam., janv. 21 2017, Vivien Didelot <vivien.didelot@...oirfairelinux.com> wrote:
> Hi Andrew,
>
> Andrew Lunn <andrew@...n.ch> writes:
>
>> The internal PHYs of the mv88e6390 do not have a model ID. Trap any
>> calls to the ID register, and if it is zero, return the ID for the
>> mv88e6390. The Marvell PHY driver can then bind to this ID.
>
> This, in addition to the temperature code not working (despite what the
> datasheet says) makes me wonder if this is intentional from Marvell. Do
> we have a revision number for the 88E6390X's on the ZII Dev Rev C board?
>
> It would be interesting to ask Gregory maybe about that. This looks not
> "production-ready".
What I can say is that with the 88E6341, which seems to have the same
issue (ie incomplete PHY ID), reading the temperature worked.
Gregory
>
> Other than that, I have no objection on the patch itself if that is
> indeed expected from them...
>
> Thanks,
>
> Vivien
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
Powered by blists - more mailing lists