From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.5 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id C1B7FC06511 for ; Wed, 3 Jul 2019 01:29:15 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id A518720B1F for ; Wed, 3 Jul 2019 01:29:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727407AbfGCB3O (ORCPT ); Tue, 2 Jul 2019 21:29:14 -0400 Received: from metis.ext.pengutronix.de ([85.220.165.71]:50097 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727206AbfGCB3N (ORCPT ); Tue, 2 Jul 2019 21:29:13 -0400 Received: from pty.hi.pengutronix.de ([2001:67c:670:100:1d::c5]) by metis.ext.pengutronix.de with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1hiPRS-0002Ke-Ln; Tue, 02 Jul 2019 22:31:54 +0200 Received: from ukl by pty.hi.pengutronix.de with local (Exim 4.89) (envelope-from ) id 1hiPRQ-0003zP-8H; Tue, 02 Jul 2019 22:31:52 +0200 Date: Tue, 2 Jul 2019 22:31:52 +0200 From: Uwe =?iso-8859-1?Q?Kleine-K=F6nig?= To: Yuiko Oshino Cc: netdev@vger.kernel.org, Andrew Lunn , Florian Fainelli , kernel@pengutronix.de, Heiner Kallweit Subject: Re: net: micrel: confusion about phyids used in driver Message-ID: <20190702203152.gviukfldjhdnmu7j@pengutronix.de> References: <20190509202929.wg3slwnrfhu4f6no@pengutronix.de> <20190509210745.GD11588@lunn.ch> <20190510072243.h6h3bgvr2ovsh5g5@pengutronix.de> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20190510072243.h6h3bgvr2ovsh5g5@pengutronix.de> User-Agent: NeoMutt/20170113 (1.7.2) X-SA-Exim-Connect-IP: 2001:67c:670:100:1d::c5 X-SA-Exim-Mail-From: ukl@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: netdev@vger.kernel.org Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org Hello Yuiko Oshino, On Fri, May 10, 2019 at 09:22:43AM +0200, Uwe Kleine-König wrote: > On Thu, May 09, 2019 at 11:07:45PM +0200, Andrew Lunn wrote: > > On Thu, May 09, 2019 at 10:55:29PM +0200, Heiner Kallweit wrote: > > > On 09.05.2019 22:29, Uwe Kleine-König wrote: > > > > I have a board here that has a KSZ8051MLL (datasheet: > > > > http://ww1.microchip.com/downloads/en/DeviceDoc/ksz8051mll.pdf, phyid: > > > > 0x0022155x) assembled. The actual phyid is 0x00221556. > > > > > > I think the datasheets are the source of the confusion. If the > > > datasheets for different chips list 0x0022155x as PHYID each, and > > > authors of support for additional chips don't check the existing code, > > > then happens what happened. > > > > > > However it's not a rare exception and not Microchip-specific that > > > sometimes vendors use the same PHYID for different chips. > > From the vendor's POV it is even sensible to reuse the phy IDs iff the > chips are "compatible". > > Assuming that the last nibble of the phy ID actually helps to > distinguish the different (not completely) compatible chips, we need > some more detailed information than available in the data sheets I have. > There is one person in the recipents of this mail with an @microchip.com > address (hint, hint!). can you give some input here or forward to a person who can? Best regards Uwe -- Pengutronix e.K. | Uwe Kleine-König | Industrial Linux Solutions | http://www.pengutronix.de/ |