Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp4956318iob; Mon, 9 May 2022 05:44:06 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwczjy+MuHS/wZSVpkz7+XdIBoTGuVm7MUv98/AmjcLNLYZRTR/XtiTV/U8ur/yUX+vEg26 X-Received: by 2002:a63:2b91:0:b0:3ab:3da7:b5ac with SMTP id r139-20020a632b91000000b003ab3da7b5acmr13148749pgr.36.1652100246403; Mon, 09 May 2022 05:44:06 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652100246; cv=none; d=google.com; s=arc-20160816; b=yu6zWZPYEeDf1nclNjLLyBXwrm6p/kbaYoQ4t8qr09Ww/PvR6nCiTo3kBNmpMzPGwE zYjMyKfF2HkrXOECeap8JezAT44Pud0nGHjpvg6tWijNjUpvii2bhTzxK8eChkkKXg7S zLCVRGhLLchfq1/B+9caU81Pgg2e86wC2ucHT1Yg4/y/0FWJNUlFHidukjpmIfTffRFi Zm0m8+74LVi/YdC5gOicV1IJe0Rxk8kv33DvjwNjXL0amH6ZTBZv+6EHSnAcPT9YMzAK 5yUWqF41249HznxN7wCojWpxN3Iflj6U60ugXnAfCR0pfkZs729dPWPc59wfsC8WWaMB KQKQ== 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=EjfCEa0TLF8f/I9bli8jlfniBJovZSdwbAn5Oa++DzA=; b=dv8LsOlq9k4CXJjLmk65d8l7LTd0ovhsPAG2wo+ePeWp4B8JEEWEAotb3M6P3lb7DY /DhqEIUqyts3LnN9LytMErseJ+k9zfHqMjaD9I7J8jVu/77hWCGofHdsw6RdvfhtTOfK FgqyW7wJDzMwJ2AmVIW6F9HbqGjnl3gTVS+KqW1ZEH7dDZv/mK7o7sau7Z4P0miXl4Rs Mi4v23OLMGl+2vJxXabx7eP7NksNCKfkSWNPaZ5WcmDgUjq5396hWXJBtV4oEu/JJ+ee r4UkNXnEN38bPKUkvyD3BmI85zHEjl3NkVzX9ySdLUBXsjslMYY7EJrUxrQUWGN6e0KC F17g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=Koa8tVPa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from lindbergh.monkeyblade.net (lindbergh.monkeyblade.net. [2620:137:e000::1:18]) by mx.google.com with ESMTPS id c12-20020a170902d48c00b0015d10bd48c2si14270059plg.32.2022.05.09.05.44.05 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 09 May 2022 05:44:06 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=Koa8tVPa; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 8D1A3274A13; Mon, 9 May 2022 05:29:32 -0700 (PDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S234528AbiEIMdM (ORCPT + 99 others); Mon, 9 May 2022 08:33:12 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40172 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234456AbiEIMdK (ORCPT ); Mon, 9 May 2022 08:33:10 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 2AF132734F4; Mon, 9 May 2022 05:29:17 -0700 (PDT) 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=EjfCEa0TLF8f/I9bli8jlfniBJovZSdwbAn5Oa++DzA=; b=Koa8tVPalAIu3bexYHIhXrbTFN tvqrLD17DhSh6hOmIiztzWbxz8ZcLc7UisgrgEqlPh35Umr7E4nA58jNORasJalkMNlFtVWhM2kjD dzxcx+1lnfGHkmP5XnTFlWvJ9hO2NTYlW9WyfXPsGgG1+057FDoeXM513XFiK8MvReFs=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1no2KN-001wGb-G4; Mon, 09 May 2022 14:17:27 +0200 Date: Mon, 9 May 2022 14:17:27 +0200 From: Andrew Lunn To: Corentin Labbe Cc: alexandre.torgue@foss.st.com, broonie@kernel.org, calvin.johnson@oss.nxp.com, davem@davemloft.net, edumazet@google.com, hkallweit1@gmail.com, jernej.skrabec@gmail.com, joabreu@synopsys.com, krzysztof.kozlowski+dt@linaro.org, kuba@kernel.org, lgirdwood@gmail.com, linux@armlinux.org.uk, pabeni@redhat.com, peppe.cavallaro@st.com, robh+dt@kernel.org, samuel@sholland.org, wens@csie.org, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-sunxi@lists.linux.dev Subject: Re: [PATCH 3/6] dt-bindings: net: Add documentation for phy-supply Message-ID: References: <20220509074857.195302-1-clabbe@baylibre.com> <20220509074857.195302-4-clabbe@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220509074857.195302-4-clabbe@baylibre.com> X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,RDNS_NONE,SPF_HELO_NONE,T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, May 09, 2022 at 07:48:54AM +0000, Corentin Labbe wrote: > Add entries for the 2 new phy-supply and phy-io-supply. > > Signed-off-by: Corentin Labbe > --- > .../devicetree/bindings/net/ethernet-phy.yaml | 10 ++++++++++ > 1 file changed, 10 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/ethernet-phy.yaml b/Documentation/devicetree/bindings/net/ethernet-phy.yaml > index ed1415a4381f..2a6b45ddf010 100644 > --- a/Documentation/devicetree/bindings/net/ethernet-phy.yaml > +++ b/Documentation/devicetree/bindings/net/ethernet-phy.yaml > @@ -153,6 +153,16 @@ properties: > used. The absence of this property indicates the muxers > should be configured so that the external PHY is used. > > + phy-supply: > + description: > + Phandle to a regulator that provides power to the PHY. This > + regulator will be managed during the PHY power on/off sequence. > + > + phy-io-supply: > + description: > + Phandle to a regulator that provides power to the PHY. This > + regulator will be managed during the PHY power on/off sequence. If you need two differently named regulators, you need to make it clear how they differ. My _guess_ would be, you only need the io variant in order to talk to the PHY registers. However, to talk to a link partner, you need the other one enabled as well. Which means handling that regulator probably should be in the PHY driver, so it is enabled only when the interface is configured up. Andrew