From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751880AbcGUJ1V (ORCPT ); Thu, 21 Jul 2016 05:27:21 -0400 Received: from gloria.sntech.de ([95.129.55.99]:45665 "EHLO gloria.sntech.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751126AbcGUJ1S (ORCPT ); Thu, 21 Jul 2016 05:27:18 -0400 From: Heiko =?ISO-8859-1?Q?St=FCbner?= To: Frank Wang Cc: Doug Anderson , Guenter Roeck , Guenter Roeck , Julius Werner , Kishon Vijay Abraham I , Rob Herring , Pawel Moll , Mark Rutland , Ian Campbell , Kumar Gala , "linux-kernel@vger.kernel.org" , "devicetree@vger.kernel.org" , "linux-usb@vger.kernel.org" , "open list:ARM/Rockchip SoC..." , Ziyuan Xu , Kever Yang , Tao Huang , =?utf-8?B?5ZC06Imv5bOw?= , daniel.meng@rock-chips.com Subject: Re: [PATCH v8 3/3] arm64: dts: rockchip: add usb2-phy support for rk3399 Date: Thu, 21 Jul 2016 11:26:49 +0200 Message-ID: <3513562.kdo4J8AU27@diego> User-Agent: KMail/4.14.10 (Linux/4.5.0-2-amd64; KDE/4.14.14; x86_64; ; ) In-Reply-To: References: <1468913311-23977-1-git-send-email-frank.wang@rock-chips.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Frank, Am Donnerstag, 21. Juli 2016, 10:49:53 schrieb Frank Wang: > >> @@ -69,6 +69,15 @@ > >> > >> regulator-max-microvolt = <3300000>; > >> > >> }; > >> > >> + vbus_host: vbus-host-regulator { > >> + compatible = "regulator-fixed"; > >> + enable-active-high; > >> + gpio = <&gpio4 25 GPIO_ACTIVE_HIGH>; > >> + pinctrl-names = "default"; > >> + pinctrl-0 = <&host_vbus_drv>; > >> + regulator-name = "vbus_host"; > >> + }; > >> + > > > > To match my schematics, this would probably be "vcc5v0_host". > > Technically there are two regulators but since they are the same > > voltage and enabled by the same GPIO it seems like modeling it as one > > regulator is fine. > > Yep, you are right, I will rename it. > > > If you really wanted to model things you could also include the input > > supply (VCC5V0_SYS). Not sure how much you care to model in EVB. > > Actually, from > "Documentation/devicetree/bindings/regulator/fixed-regulator.txt" show, > input supply name is just optional property, and it seems that only do > assign "vin" value for input_supply (the second member of struct > fixed_voltage_config) if "vin-supply" is specified. > > So is input supply name (VCC5V0_SYS) required here? Would you like to > give more comments please? While vin-supply is optional, I think that is meant for real top-level regulators (our vcc_sys or whatever) that really don't have a parent regulator. It is always nicer to model the whole power-tree [in a sane way], as it makes following the schematics a lot easier. If you mount a debugfs these days you can even get a nice tree graph of the regulator infrastructure ... where the parent-relationship is also needed to create something meaningful. Heiko