[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20191013.141450.1430066442611592842.davem@davemloft.net>
Date: Sun, 13 Oct 2019 14:14:50 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: marex@...x.de
Cc: hkallweit1@...il.com, netdev@...r.kernel.org, andrew@...n.ch,
f.fainelli@...il.com, george.mccollister@...il.com,
sean.nyekjaer@...vas.dk, Tristram.Ha@...rochip.com,
woojung.huh@...rochip.com
Subject: Re: [PATCH V3 1/2] net: phy: micrel: Discern KSZ8051 and KSZ8795
PHYs
From: Marek Vasut <marex@...x.de>
Date: Sun, 13 Oct 2019 22:29:31 +0200
> On 10/13/19 10:15 PM, Heiner Kallweit wrote:
>> On 13.10.2019 21:34, Marek Vasut wrote:
>>> The KSZ8051 PHY and the KSZ8794/KSZ8795/KSZ8765 switch share exactly the
>>> same PHY ID. Since KSZ8051 is higher in the ksphy_driver[] list of PHYs
>>> in the micrel PHY driver, it is used even with the KSZ87xx switch. This
>>> is wrong, since the KSZ8051 configures registers of the PHY which are
>>> not present on the simplified KSZ87xx switch PHYs and misconfigures
>>> other registers of the KSZ87xx switch PHYs.
>>>
>>> Fortunatelly, it is possible to tell apart the KSZ8051 PHY from the
>>> KSZ87xx switch by checking the Basic Status register Bit 0, which is
>>> read-only and indicates presence of the Extended Capability Registers.
>>> The KSZ8051 PHY has those registers while the KSZ87xx switch does not.
>>>
>>> This patch implements simple check for the presence of this bit for
>>> both the KSZ8051 PHY and KSZ87xx switch, to let both use the correct
>>> PHY driver instance.
>>>
>>> Signed-off-by: Marek Vasut <marex@...x.de>
>>> Cc: Andrew Lunn <andrew@...n.ch>
>>> Cc: David S. Miller <davem@...emloft.net>
>>> Cc: Florian Fainelli <f.fainelli@...il.com>
>>> Cc: George McCollister <george.mccollister@...il.com>
>>> Cc: Heiner Kallweit <hkallweit1@...il.com>
>>> Cc: Sean Nyekjaer <sean.nyekjaer@...vas.dk>
>>> Cc: Tristram Ha <Tristram.Ha@...rochip.com>
>>> Cc: Woojung Huh <woojung.huh@...rochip.com>
>>> Fixes: 9d162ed69f51 ("net: phy: micrel: add support for KSZ8795")
>>
>> The Fixes tag has to be the first one. And patch still misses
>> the "net" annotation. For an example just see other fix submissions
>> on the mailing list.
>
> The "net" annotation ? The net: tag is right there in the subject.
It also belongs in the [ PATCH ...] area as an indicator of the target
GIT tree.
Powered by blists - more mailing lists