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=-4.0 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 0E5C4C433E0 for ; Fri, 31 Jul 2020 15:31:25 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id E368E208E4 for ; Fri, 31 Jul 2020 15:31:24 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729258AbgGaPbY (ORCPT ); Fri, 31 Jul 2020 11:31:24 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:37108 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726502AbgGaPbX (ORCPT ); Fri, 31 Jul 2020 11:31:23 -0400 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1k1X0B-007iQT-KN; Fri, 31 Jul 2020 17:31:19 +0200 Date: Fri, 31 Jul 2020 17:31:19 +0200 From: Andrew Lunn To: Vikas Singh Cc: f.fainelli@gmail.com, hkallweit1@gmail.com, linux@armlinux.org.uk, netdev@vger.kernel.org, "Calvin Johnson (OSS)" , Kuldip Dwivedi , "Madalin Bucur (OSS)" , Vikas Singh Subject: Re: [PATCH 2/2] net: phy: Associate device node with fixed PHY Message-ID: <20200731153119.GJ1712415@lunn.ch> References: <1595938400-13279-1-git-send-email-vikas.singh@puresoftware.com> <1595938400-13279-3-git-send-email-vikas.singh@puresoftware.com> <20200728130001.GB1712415@lunn.ch> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Jul 29, 2020 at 07:34:19PM +0530, Vikas Singh wrote: > Hi Andrew, > > I understand your concern But my use case is pretty simple and straightforward. > As you are already aware of the fact that operating systems running on standard > server hardware requires standard firmware interfaces to be present in order to > boot > and function correctly. > Here SBBR describes these firmware requirements which covers UEFI & ACPI. > Therefore I would like to provide dual boot support to such systems which means > supporting ACPI along with existing DT. > Now kernels "__fixed_phy_registe() " being a wonderful implementation catters > almost every thing required for both ACPI & DT > But fails to register fixed PHYs in case of ACPI because it has no clue of the > fwnode (of_node in case of DT) to attach with a PHY device. You failed to answer my question. Why do you need a fixed PHY? Please could you point me at your DT files so i can at least understand your hardware. Andrew