Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp3603058imj; Tue, 19 Feb 2019 06:24:28 -0800 (PST) X-Google-Smtp-Source: AHgI3IZIsTADknDWRy/nJFDlli5QW7EhN/XnUoHUFmX61Gen5hQX+2O+ol+Q5kn/+mrzWdg6aAbt X-Received: by 2002:a63:4342:: with SMTP id q63mr24309296pga.63.1550586268847; Tue, 19 Feb 2019 06:24:28 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550586268; cv=none; d=google.com; s=arc-20160816; b=N/bz779Xoo4FEHO7ZsOhkTWdD4hPuiK4IO3QwDBOK98+EDbi5x6ViB3Fwa1EA7RI3T G8/Kn7GBSSWCXxCoWIKPlH9zbfOy4FfMwTm4d25Y4MHWmRtUV0+L3Ukw5pTpNNXBT1fw agsYrJBBfzXSCJ04zszbK9wWgOMfwmR+0hPbKG0SENZW4hAYrswzspwFsQSE9lPLOXCr b0PUavU7/HY1muHpbbyjqn5dbydzM+NGpNdz/01h1CyZcgNyl949PoRwyzvOw7ljkoG6 pUxh2gWv89aIr9A5cljMuoEmYlACQkbFu+JoZaviZp8RRrZy/0lp6oaUaqr1wgqdTJ1j sL8Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=Hok0X3RcwpSMn7pqxoVditH3kQS8ueHntgFTiWwDsrY=; b=piQXVqU3SZy6uUt1YyFXAZ7oP8sRWAICPOOe4kVBmrv7gXakHQxo5T8kygrtJsUkIB 31FyiGjkSpkpRpQUPnevx+5mGnD7T59DYtho63UzOloH8+4b9+c2NdCKsJXU4FXM/+4B dxvfOprXMTi8E3Y5K48eVSaS6rQxg+iFYcO4yQ1hDFYAdafRy/+3we9LzisAdrd/SRRY s7CIM6DVmoBwZc5JkpCBwTWNsPJt5HkRXQq6rmqWCJr6qPi5n1FFkUHSl4LXgtk6aJQ1 vBe+/Y7fwYQLV1sfqwDoSOGSLnpftjFD403foogOeWBEs3w8jubKbz3u9cxqM4gLesVt duVA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=KmcM1Dd8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t9si15079092pgu.103.2019.02.19.06.24.13; Tue, 19 Feb 2019 06:24:28 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=KmcM1Dd8; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727645AbfBSOWc (ORCPT + 99 others); Tue, 19 Feb 2019 09:22:32 -0500 Received: from mail.kernel.org ([198.145.29.99]:59686 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725767AbfBSOWb (ORCPT ); Tue, 19 Feb 2019 09:22:31 -0500 Received: from mail-qk1-f182.google.com (mail-qk1-f182.google.com [209.85.222.182]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 73508217D7; Tue, 19 Feb 2019 14:22:30 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1550586150; bh=q8IAGCGPndn6ZY5trkXqM325/UglqRESL1pRQffvHFM=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=KmcM1Dd84KcsRlcDgdZ4QwHYYE1qhMTT1efH5W8wH5aw+uKLUKoO1Vt93fW/oyPTh vJFsNbOuZ6UwFXNedX9N6w8ocPrG4HfEUtmE7RiHA6p5/m8sD6K8fANPyfwDDeOe47 qPdaRDMhXRg9DEn2J2tAFOEeZ7xLDpUS0+YuiYWo= Received: by mail-qk1-f182.google.com with SMTP id u188so12075832qkh.8; Tue, 19 Feb 2019 06:22:30 -0800 (PST) X-Gm-Message-State: AHQUAub81tBk+/H1KBniiv6ExzxN9TomGG6UiqpMSDvAFXqGCLR/Htdp qszpMMz8l/muLiwGNTYRWiOJmrI4lOaUad6JkQ== X-Received: by 2002:a37:94d:: with SMTP id 74mr3980596qkj.79.1550586149646; Tue, 19 Feb 2019 06:22:29 -0800 (PST) MIME-Version: 1.0 References: <20190218112310.17860-1-chenyu56@huawei.com> <20190218112310.17860-2-chenyu56@huawei.com> <20190218201824.GA23724@bogus> <1550545405.2210.30.camel@mhfsdcap03> In-Reply-To: <1550545405.2210.30.camel@mhfsdcap03> From: Rob Herring Date: Tue, 19 Feb 2019 08:22:18 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 01/10] dt-bindings: phy: Add support for HiSilicon's hi3660 USB PHY To: Chunfeng Yun Cc: Chen Yu , liuyu712@hisilicon.com, Linux USB List , devicetree@vger.kernel.org, "linux-kernel@vger.kernel.org" , John Stultz , Suzhuangluan , kongfei@hisilicon.com, wanghu17@hisilicon.com, butao@hisilicon.com, chenyao11@huawei.com, fangshengzhou@hisilicon.com, Li Pengcheng , Song Xiaowei , Yiping Xu , xuyoujun4@huawei.com, yudongbin@hisilicon.com, zangleigang , Mark Rutland , Binghui Wang Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Feb 18, 2019 at 9:03 PM Chunfeng Yun wrote: > > Hi, > On Tue, 2019-02-19 at 09:50 +0800, Chen Yu wrote: > > Hi, > > > > On 2019/2/19 4:18, Rob Herring wrote: > > > On Mon, Feb 18, 2019 at 07:23:01PM +0800, Yu Chen wrote: > > >> This patch adds binding documentation for supporting the hi3660 usb > > >> phy on boards like the HiKey960. > > >> > > >> Cc: Rob Herring > > >> Cc: Mark Rutland > > >> Cc: John Stultz > > >> Cc: Binghui Wang > > >> Signed-off-by: Yu Chen > > >> --- > > >> v1: > > >> * Fix some format error as suggested by Rob. > > >> v2: > > >> * Change hi3660 usb PHY to hi3660 USB PHY > > >> --- > > >> --- > > >> .../devicetree/bindings/phy/phy-hi3660-usb3.txt | 21 +++++++++++++++++++++ > > >> 1 file changed, 21 insertions(+) > > >> create mode 100644 Documentation/devicetree/bindings/phy/phy-hi3660-usb3.txt > > >> > > >> diff --git a/Documentation/devicetree/bindings/phy/phy-hi3660-usb3.txt b/Documentation/devicetree/bindings/phy/phy-hi3660-usb3.txt > > >> new file mode 100644 > > >> index 000000000000..f9a3d56cfdd2 > > >> --- /dev/null > > >> +++ b/Documentation/devicetree/bindings/phy/phy-hi3660-usb3.txt > > >> @@ -0,0 +1,21 @@ > > >> +Hisilicon hi3660 USB PHY > > >> +----------------------- > > >> + > > >> +Required properties: > > >> +- compatible: should be "hisilicon,hi3660-usb-phy" > > >> +- #phy-cells: must be 0 > > >> +- hisilicon,pericrg-syscon: phandle of syscon used to control phy. > > >> +- hisilicon,pctrl-syscon: phandle of syscon used to control phy. > > >> +- hisilicon,usb3-otg-bc-syscon: phandle of syscon used to control phy. > > >> +- hisilicon,eye-diagram-param: parameter set for phy > > >> +Refer to phy/phy-bindings.txt for the generic PHY binding properties > > >> + > > >> +Example: > > >> + usb-phy { > > >> + compatible = "hisilicon,hi3660-usb-phy"; > > >> + #phy-cells = <0>; > > >> + hisilicon,pericrg-syscon = <&crg_ctrl>; > > >> + hisilicon,pctrl-syscon = <&pctrl>; > > >> + hisilicon,usb3-otg-bc-syscon = <&usb3_otg_bc>; > > > > > > Are most of the registers within one of these blocks? If so, make this > > > node a child of that node. > > I met a problem when I made this node a child of the syscon node, > > the driver "phy-hi3660-usb3" was not probed. > > Do you have any idea about how to make it probed when it is a child node? > call of_platform_populate() in parent node's driver, > but I don't know whether it's a standard way It is. The other way is adding 'simple-mfd' compatible if there is no driver for the parent. Rob