Received: by 2002:a05:6a10:1d13:0:0:0:0 with SMTP id pp19csp2142281pxb; Mon, 23 Aug 2021 13:01:10 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwQKnUf0QoxdU2Ba+A8KVuZPrQ51o0ImB0OHE2hX5YaRfGw+9Nd07WHuXR3wQX5bwJaNBhu X-Received: by 2002:a17:906:b4d:: with SMTP id v13mr6474472ejg.468.1629748870126; Mon, 23 Aug 2021 13:01:10 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1629748870; cv=none; d=google.com; s=arc-20160816; b=FGVYF2pc0sb+AXKuyOLUXUn+ApsXAUERcdDwCVXvD9ZyoaM18ZBtIg4AT6DwldMe4i Cfte+p1jI2jCh7rIgbkV2MB3+I3dTnzSmEF2pkfdO2lb5aACpGImaw5vYLro18uwTPPQ jZetpzIU3bVDGfT+slv8yhFKLg8TXJXjZxtpXglRj4kZrnSMuBS5Ur3MpQSXHMGPSaio 3DM9olvXo5PEDekpBHLfMh6QAODp/c6Cf17xslv5Mhr5NtfnNInc/il2JUiQJfrTkiJ0 MaAzk8ySvO2Zk2U6NCl2dXyk5E03GXVMhuW50URL1YEb/kp358fkHJ/vjGSsrcvOUQDF wjVQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=GpyOlPjzkVman/xz6U9nRO0hrxXvVycp3ftxTY9a7NE=; b=iu2Nq52m/zZraJiQvg2DTqEWEdw1buutqvjpjDHLJqlkzIHVAAK2SjF4LKeG3u8MTX 91S5zxyxVA1h4o3ybKNtErIp9H5rOQu8J1jIT8ktRKK6nGS4wBFIgen8b8BLBMMGsXt2 J5huROnDx4X/QA+RL8gN/th6E42r3xPABcQWvz1dDQCX1xRU92cYe8d21jyF7geQbMdB Vovd01FpUmPTngV2rOKx0+17W24Nj/XL43QNUAbaoyK55CwNW9uJ+ocJ8MOBVUpPYGAc DkOiQM4FlvaFrL3/winszCVBva6JLnTS6XL090JR4F/+RiF4AZ9/GDmwdOlJFImmGd2K WfdA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b="KA2u/854"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id b7si243462edz.334.2021.08.23.13.00.42; Mon, 23 Aug 2021 13:01:10 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b="KA2u/854"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231496AbhHWT7D (ORCPT + 99 others); Mon, 23 Aug 2021 15:59:03 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:37348 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229622AbhHWT7D (ORCPT ); Mon, 23 Aug 2021 15:59:03 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=GpyOlPjzkVman/xz6U9nRO0hrxXvVycp3ftxTY9a7NE=; b=KA2u/854Aag+RH3uz7vKq/MMSv rhyn0HsPvD6jQ6R5qbpNU6feqBmdpCE/utd3Fc7QUNTfasXY0+S7AlD/IIekWVdh6W5e78QKCcXs5 Xu26CuvkmjF6Wgw5ClUibFJqPzx+oZfVEMPYP1AFibW7pdv9ehRX/7KantFyCCRIJBlQ=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1mIG5E-003Vi4-U5; Mon, 23 Aug 2021 21:58:12 +0200 Date: Mon, 23 Aug 2021 21:58:12 +0200 From: Andrew Lunn To: Saravana Kannan Cc: Marek Szyprowski , Rob Herring , Frank Rowand , netdev@vger.kernel.org, kernel-team@android.com, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Neil Armstrong , linux-amlogic@lists.infradead.org Subject: Re: [PATCH v2] of: property: fw_devlink: Add support for "phy-handle" property Message-ID: References: <20210818021717.3268255-1-saravanak@google.com> <0a2c4106-7f48-2bb5-048e-8c001a7c3fda@samsung.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > PHY seems to be one of those cases where it's okay to have the > compatible property but also okay to not have it. Correct. They are like PCI or USB devices. You can ask it, what are you? There are two registers in standard locations which give you a vendor and product ID. We use that to find the correct driver. You only need a compatible when things are not so simple. 1) The IDs are wrong. Some silicon vendors do stupid things 2) Chicken/egg problems, you cannot read the ID registers until you load the driver and some resource is enabled. 3) It is a C45 devices, e.g. part of clause 45 of 802.3, which requires a different protocol to be talked over the bus. So the compatible string tells you to talk C45 to get the IDs. 4) It is not a PHY, but some sort of other MDIO device, and hence there are no ID registers. Andrew