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 F2F6C19F43A; Tue, 27 May 2025 20:30:38 +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=1748377840; cv=none; b=M5maWHDu/hZezAMUdspD9c9+8d5v3gBy7uWca6Axwb5alblUZdU01imeXKKXXAR/Ez4N4cFsAwDTIKWsda938Z3iZ+PJnvxyBWPMWgAYI2XRH2GhlqYVRGn1MxaOM1MXiPVkb9t0qu+b6fILt31Ml3ZEI7EwNUO4j0nmkM+CJB8= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1748377840; c=relaxed/simple; bh=rPAIlHuBP4rjfXX4dXbfdZ6VKERKCLrxzIC/bqu4C2c=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=DvZ+qg2Sn70295Oq4WYdgDGuNJ+SCdd3URHrHjQaMp1AbUEa7FO050Mb6s6cUAougOqz0NK0rwXyLxC8aKtACPiLqlZwdn+gT9aoRERzIDAbSZDavlB8Dg6hu5nxDIaQu9gzhh8i763YCvWRBjf5/j1Jw55+vvWL1cIba/yY1Lg= 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=Ys+ytjXW; 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="Ys+ytjXW" 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=0em3nkfm7wr1wOy1RDHkE+4GaWVMw9u6qC9S4sIxQ1E=; b=Ys+ytjXWrhSjDAwUV4vBIAVZyB 5UizPo7fpEQ8quN42NJ613Czwy/nD3MQr2CWaJOQ2oc7id0R12wa8V96nKQt1QJgZqk9ITm4oYoE2 lMqWQdh9jz5ICMl3XRA3mzO9ogTVcMxz/n8EcfY8SW5Eex6mKo3jTOlr2fac1OfpFT1s=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1uK0wS-00E6h6-Od; Tue, 27 May 2025 22:30:32 +0200 Date: Tue, 27 May 2025 22:30:32 +0200 From: Andrew Lunn To: James Hilliard Cc: netdev@vger.kernel.org, linux-sunxi@lists.linux.dev, Andrew Lunn , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Maxime Coquelin , Alexandre Torgue , Russell King , "Russell King (Oracle)" , Furong Xu <0x1207@gmail.com>, Kunihiko Hayashi , linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/3] net: stmmac: allow drivers to explicitly select PHY device Message-ID: <014d8d63-bfb1-4911-9ea6-6f4cdabc46e5@lunn.ch> References: <20250527175558.2738342-1-james.hilliard1@gmail.com> <631ed4fe-f28a-443b-922b-7f41c20f31f3@lunn.ch> Precedence: bulk X-Mailing-List: linux-kernel@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: > Sure, that may make sense to do as well, but I still don't see > how that impacts the need to runtime select the PHY which > is configured for the correct MFD. If you know what variant you have, you only include the one PHY you actually have, and phy-handle points to it, just as normal. No runtime selection. Andrew