From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 115E73515E6; Tue, 4 Aug 2026 14:54:35 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785855277; cv=none; b=KaQZZnWhUpnT1h0+gfbSR26UVEV4lHYabH0rfB83tGeICBqDnKwxOzgA83xrMX0bcqC+fPaC0B2xUXFS1UrcyE4ebe3vIYy7u0wEMlCAm2YHLWR3UMoeee20ewvTVezvp/f1hyeXVZmo1/0FLFf+5Tnm2mAFRnU0o+qaJJoos3M= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785855277; c=relaxed/simple; bh=LladUGeQqQO+Z/uhca5U89Of9v8zaoBpTmkeNyerAWQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=r9Zg2Z0ETdZ5HuGALZOmmGvdxALO83yn69fpCD7jJAv5iVa9APCJqeH2yRbMQRyk08bZ566CSedFrVvKUKf3oUfkbqPKDFR7DyUZBJxNUKCeR+rQdvvQ+/lJG+iqKbIqP1hOFOKYEKd4ysOQoA0CW4gD7KHTxz9RX9vGlBMU0T4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=G6RA/B6N; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="G6RA/B6N" 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=FVcysNhXi0SKuam3CXUhAeBuqKpKKoH5Agw3hOwh+OQ=; b=G6RA/B6N9QcAQXF9n5BBZcIvR6 udxKfvx1udCDq1mUllEsc1W+KanrgLjoCOw7n5czm5NayiKbRiyVAlPiVq39BhGrqwFxmSajG8VZJ WSCcdogKlJa3QF5eqLXoTNEgUkDQf5AUdxIoRjkFYOih/yukSGAQDR/E5KiB/sZOJGrA=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1wrGX6-00G0Oe-HM; Tue, 04 Aug 2026 16:54:20 +0200 Date: Tue, 4 Aug 2026 16:54:20 +0200 From: Andrew Lunn To: James Hilliard Cc: Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Chen-Yu Tsai , Jernej Skrabec , Samuel Holland , Andre Przywara , Richard Genoud , Maxime Ripard , Alexandre Torgue , Giuseppe Cavallaro , Jose Abreu , Maxime Chevallier , Maxime Coquelin , Heiner Kallweit , Russell King , Saravana Kannan , Lee Jones , Heiko Stuebner , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-sunxi@lists.linux.dev, linux-kernel@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, mfd@lists.linux.dev, linux-rockchip@lists.infradead.org Subject: Re: [PATCH 10/21] net: phy: add X-Powers AC200 EPHY control driver Message-ID: <205e9051-8e43-44bb-a4b5-4ec69a192fa3@lunn.ch> References: <20260802-submit-acx00-of-dynamic-v1-v1-0-0a53cd9e21cc@gmail.com> <20260802-submit-acx00-of-dynamic-v1-v1-10-0a53cd9e21cc@gmail.com> <05b1e6a2-725e-4b8e-8629-249637bbcb81@lunn.ch> <9b8be475-1fde-409c-a82e-be4b2e402650@lunn.ch> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: > I agree that the link PHY cannot be identified by reading its > registers before the package control sequence has run. I do not agree > that this means an arbitrary ID should be placed in DT, though. The ability to put the ID in DT is there for two reasons: 1) You cannot enumerate the PHY because of missing clocks etc. 2) The vendor messed up, and did not put a valid ID in registers 2 and 3. 2 does not happen very often, but this is one example. They are different PHYs, they need different driver code, when you consider the PHY as a whole. I also wound not put in an arbitrary ID, pick an unused ID in the vendors range. > Both AC200 and AC300 expose the same link-side PHY ID and register > layout. No they don't. There are extra registers in different address domains. Andrew