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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A5646C433EF for ; Fri, 7 Jan 2022 13:52:14 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:References:In-Reply-To: Message-ID:Date:Subject:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=J1Nc+XD/IgPzJGfUfhLFQ7vwjrYVyh1P3hvaMbfeVe4=; b=N5NiFglEdPBNaF R7nmXRlPVg69u5Bb4oQkBaqMJyc7vau+9c6Utevh2iTcdFwMABLyhpRWw07n1hd7mV4pwkvEuMbLj 6iVGTAXAD+rAI8jirnd9VAacxD3TKo0XghXtAWpoSyUeGA2u0Co6nzkiJcCEtWLeMSS3ZPIIUNFb0 INVPyeD2XYt5CFOjTaFtl3GC0S9jZIkx9KuxLf+AndVY+RIXfLxzYn8eJRjLKpa/67gbf4S9Jc98I F9wSu41qfqgqmJI6nBhLXh/r2EIlUEecg/koXfyiCpEVoWJ7iJjUq0K+JSnqXMr/qyRrTU1os1o/t /v3ZoyHV5JiMTr2S5oxg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1n5pe2-0043Me-Ad; Fri, 07 Jan 2022 13:51:02 +0000 Received: from mx1.tq-group.com ([93.104.207.81]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1n5pdx-0043KT-P0; Fri, 07 Jan 2022 13:50:59 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tq-group.com; i=@tq-group.com; q=dns/txt; s=key1; t=1641563457; x=1673099457; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=D3ZeXQFnuKc/DhNBleBquRrkXlPC75Rm6tkHp7pWW80=; b=cM5knQqjD25/tUqm6Wnj+5AInE7tTY8uYJSeue0TYre16Qh0y0OQNnCs uyCXqzYZPtTOmY8NNZUQe3kuF4YZeLD8IJvr4odkbPBv/W4jFoIoKq+bu NRv4DgKE8HI/JslIW/zA7NeyDew+OLSM4BlUJNZE8v1rMdIJkw0X4xa19 zSopZUYQ5vdQrAP0/p60ZQ/lYqRaTrWsHaLxuBHiHIl51NRaDtLGIkGag Fvej1uwjv4tVrz/RRieLgAhFltSwFJsTCC2Wcl16N3OIZ29VnNf8gTpAf pWNBEw0E7ssEtrMyvuf74679VBrUgqbe+Z5diZ62uOpmYLEdb//MnfBBJ w==; X-IronPort-AV: E=Sophos;i="5.88,270,1635199200"; d="scan'208";a="21379106" Received: from unknown (HELO tq-pgp-pr1.tq-net.de) ([192.168.6.15]) by mx1-pgp.tq-group.com with ESMTP; 07 Jan 2022 14:50:55 +0100 Received: from mx1.tq-group.com ([192.168.6.7]) by tq-pgp-pr1.tq-net.de (PGP Universal service); Fri, 07 Jan 2022 14:50:56 +0100 X-PGP-Universal: processed; by tq-pgp-pr1.tq-net.de on Fri, 07 Jan 2022 14:50:56 +0100 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tq-group.com; i=@tq-group.com; q=dns/txt; s=key1; t=1641563455; x=1673099455; h=from:to:cc:subject:date:message-id:in-reply-to: references:mime-version:content-transfer-encoding; bh=D3ZeXQFnuKc/DhNBleBquRrkXlPC75Rm6tkHp7pWW80=; b=FF2wLpIzx//CIpC7GvbazYL6TrJ0u3GjsdDlbGLQpLYrGIY6tviIHBqm 2/+qpK8YZ/7EFP4MQsXEC0P4WWX6se6SWXHj/zduPQ+nsC9VJH1s8mKPT A3UlQTWGAtT/si4AiPhs4l3V38Dcn2ulYFsAN4DCbsBFc1mbghabo1pXw pfndWB4bHJXPmIWcOTaGQYNfTBk9mylTr25xH8GWC1/GrOUFVLNW8Bp1B ICBpAai9BrgzaQlCvg+bNEJOYiccibRRvdHLqOaAFFTooWWiKbvp6We2L HvFbVHDUmg5FuVVUgzDZaKwVDfTLy5enJ1dax883rVGofbX6tRpFQJuyS g==; X-IronPort-AV: E=Sophos;i="5.88,270,1635199200"; d="scan'208";a="21379105" Received: from vtuxmail01.tq-net.de ([10.115.0.20]) by mx1.tq-group.com with ESMTP; 07 Jan 2022 14:50:55 +0100 Received: from steina-w.localnet (unknown [10.123.49.12]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) (No client certificate requested) by vtuxmail01.tq-net.de (Postfix) with ESMTPSA id 7BE67280065; Fri, 7 Jan 2022 14:50:55 +0100 (CET) From: Alexander Stein To: linux-arm-kernel@lists.infradead.org Cc: Kishon Vijay Abraham I , Vinod Koul , Shawn Guo , Sascha Hauer , Fabio Estevam , NXP Linux Team , linux-phy@lists.infradead.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Rob Herring Subject: Re: (EXT) Re: [PATCH v2 1/3] dt-bindings: phy: imx8mq-usb-phy: Add imx8mp specific flags Date: Fri, 07 Jan 2022 14:50:55 +0100 Message-ID: <2245006.irdbgypaU6@steina-w> Organization: TQ-Systems GmbH In-Reply-To: References: <20211216160541.544974-1-alexander.stein@ew.tq-group.com> <20211216160541.544974-2-alexander.stein@ew.tq-group.com> MIME-Version: 1.0 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220107_055058_219857_AF11E153 X-CRM114-Status: GOOD ( 28.64 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org Hello, thanks for the review. Am Dienstag, 21. Dezember 2021, 17:59:52 CET schrieb Rob Herring: > On Thu, Dec 16, 2021 at 05:05:39PM +0100, Alexander Stein wrote: > > This adds bindings for features only available on imx8mp. They allow > > setting polarity of PWR and OC as well as disabling port power control. > > Also permanently atteched can be annotated as well. > > > > Signed-off-by: Alexander Stein > > --- > > Adding properties specific to one compatible globally and disabling them > > on > > other compatibles is the way to go? > > > > Are there any best practices on the usage of '-' and/or '_' in property > > names? > Yes, don't use '_'. Alright, got it. > > .../bindings/phy/fsl,imx8mq-usb-phy.yaml | 52 ++++++++++++++++++- > > 1 file changed, 51 insertions(+), 1 deletion(-) > > > > diff --git a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml > > b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml index > > 2936f3510a6a..1d28b7d1c413 100644 > > --- a/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml > > +++ b/Documentation/devicetree/bindings/phy/fsl,imx8mq-usb-phy.yaml > > > > @@ -16,7 +16,8 @@ properties: > > - fsl,imx8mp-usb-phy > > > > reg: > > - maxItems: 1 > > + minItems: 1 > > + maxItems: 2 > > > > "#phy-cells": > > const: 0 > > > > @@ -32,6 +33,28 @@ properties: > > description: > > A phandle to the regulator for USB VBUS. > > > > + fsl,permanently-attached: > > + type: boolean > > + description: > > + Indicates if the device atached to a downstream port is > > + permanently attached. > > Wouldn't just describing the downstream device be enough to indicate > this? Though that is in the host controller rather than the phy. You mean describing the downstream hub in device tree? I guess you are thinking about Documentation/devicetree/bindings/usb/usb-device.yaml, no? I'll try using this. This flag (and the others below) are used to set some specific flag in the host controller (not the PHY, see Li Jun's response). But I have to admit I do not know what they actually do. The description is pretty much everything written in the reference manual. > > + > > + fsl,disable-port-power-control: > > + type: boolean > > + description: > > + Indicates whether the host controller implementation includes port > > + power control. Defines Bit 3 in capability register (HCCPARAMS). > > + > > + fsl,over-current-active-low: > > + type: boolean > > + description: > > + Over current signal polarity is active low. > > + > > + fsl,power-active-low: > > + type: boolean > > + description: > > + Power pad (PWR) polarity is active low. > > + > > > > required: > > - compatible > > - reg > > > > @@ -39,6 +62,33 @@ required: > > - clocks > > - clock-names > > > > +if: > > + properties: > > + compatible: > > + contains: > > + enum: > > + - fsl,imx8mp-usb-phy > > + > > +then: > > + properties: > > + reg: > > + minItems: 2 > > + maxItems: 2 > > + items: > > + - description: PHY register base address > > + - description: Glue layer base address > > Move 'items' to the top level and then here you only need 'minItems: 2'. > > > + > > +else: > > + properties: > > + reg: > > + maxItems: 1 > > + items: > > + - description: PHY register base address > > And just 'maxItems' here. Thanks for the hints on how to write bindings, still fiddling with it. Best regards, Alexander _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel