Message ID | 20221027044920.23194-3-hayashi.kunihiko@socionext.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a5d:6687:0:0:0:0:0 with SMTP id l7csp29998wru; Wed, 26 Oct 2022 21:54:46 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4ZY4mG1LuR99ZxImHxgSiuQrmhQgUZJu2o9o+UTa7Qp+xXozoZ9V6TDbSxTkkObzXQCPDg X-Received: by 2002:a17:907:74a:b0:77e:9455:b4e1 with SMTP id xc10-20020a170907074a00b0077e9455b4e1mr41332647ejb.462.1666846486118; Wed, 26 Oct 2022 21:54:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666846486; cv=none; d=google.com; s=arc-20160816; b=HcYpngMA8pV8IC1S0hDUnNM/QT1FR4EjdqBmfaI2J2aI4FAqkkfyqXWS4POIhxNtiw CLNjaPU84Poi8Er4VvFFiH/6yckADXO17861AgK6vJkBtSF7IHcAYKGZxyWg5uhpxR8F S4+HXc2bHFl5nvV2fe3CIvxaDVYtyybAlg2cP5DNdQOtVPpR4zYXZGaxsuyrelGAhKp+ EeeIvygIqY7eUTuJw+kBlrUjkAzkR1CsVC0V9Qxl09p1GpAWQ70hg+CU4KxQ5wptwLoR X/kOqeoKoV55JYLwYYbcnLLSMLGTGNNOgGDLGU0muzsU1M4GZVbvTyKME9DiKY9x9xs5 XGlg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:date:subject:cc:to:from; bh=+D+xflOZE73dO28tAZRd3RIiMSY6GTIxc6SIAYzBepo=; b=f53BGVNLqhF0mZru5CONx86vFCYmZe34cNxr+wl9EMad8arzSZ4cXKltEOdVzNkvDB JfU4gtSSMhxW+uyxhNqihfgRkk0G2MWg62Scph8/Tp9ePPiR89Xe0FkAqrT52cLGw7PY zvUdEb9DjfBSSytkBr3tWBo6I4Ki27P1DJsGU16EoPR9hYPzE1gToTcc8hIhPMrLAFjs dGXZDGiJCZYGYLE8KN9z5f9d8ovpYj89zjpbiyZ6Y+ne3LolN+LcjLtX/AXlAfwtjk3F kv9xQcuinwuwExm9Hldty/ijRBGv8BWId8CTfiamOu1V4aIBd9Fp1xnd+nQjj1nTILKA NyDQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id j5-20020aa7ca45000000b00459a0a21965si425944edt.516.2022.10.26.21.54.21; Wed, 26 Oct 2022 21:54:46 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233971AbiJ0Ett (ORCPT <rfc822;hiifong.im@gmail.com> + 99 others); Thu, 27 Oct 2022 00:49:49 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233963AbiJ0Eti (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 27 Oct 2022 00:49:38 -0400 Received: from mx.socionext.com (mx.socionext.com [202.248.49.38]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id BCDABB1C4; Wed, 26 Oct 2022 21:49:32 -0700 (PDT) Received: from unknown (HELO iyokan2-ex.css.socionext.com) ([172.31.9.54]) by mx.socionext.com with ESMTP; 27 Oct 2022 13:49:31 +0900 Received: from mail.mfilter.local (m-filter-2 [10.213.24.62]) by iyokan2-ex.css.socionext.com (Postfix) with ESMTP id A167220584CE; Thu, 27 Oct 2022 13:49:31 +0900 (JST) Received: from 172.31.9.51 (172.31.9.51) by m-FILTER with ESMTP; Thu, 27 Oct 2022 13:49:31 +0900 Received: from plum.e01.socionext.com (unknown [10.212.243.119]) by kinkan2.css.socionext.com (Postfix) with ESMTP id 531E4B62A4; Thu, 27 Oct 2022 13:49:31 +0900 (JST) From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> To: Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Vinod Koul <vkoul@kernel.org>, Kishon Vijay Abraham I <kishon@kernel.org>, Masami Hiramatsu <mhiramat@kernel.org> Cc: devicetree@vger.kernel.org, linux-phy@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Kunihiko Hayashi <hayashi.kunihiko@socionext.com> Subject: [PATCH 2/2] dt-bindings: phy: Fix UniPhier SATA controller node names in example Date: Thu, 27 Oct 2022 13:49:20 +0900 Message-Id: <20221027044920.23194-3-hayashi.kunihiko@socionext.com> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20221027044920.23194-1-hayashi.kunihiko@socionext.com> References: <20221027044920.23194-1-hayashi.kunihiko@socionext.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS autolearn=ham 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: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1747815221411756101?= X-GMAIL-MSGID: =?utf-8?q?1747815221411756101?= |
Series |
dt-bindings: phy: Fix UniPhier controller node names
|
|
Commit Message
Kunihiko Hayashi
Oct. 27, 2022, 4:49 a.m. UTC
The word "glue" is ambiguous for the controller node name. Should put
"sata-controller" instead of "ahci-glue" on the controller node.
And rename a phy node to "sata-phy".
Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
---
.../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
Comments
On Thu, Oct 27, 2022 at 01:49:20PM +0900, Kunihiko Hayashi wrote: > The word "glue" is ambiguous for the controller node name. Should put > "sata-controller" instead of "ahci-glue" on the controller node. > And rename a phy node to "sata-phy". > > Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> > --- > .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > index a3cd45acea28..89b8b133777a 100644 > --- a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > +++ b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > @@ -117,14 +117,14 @@ additionalProperties: false > > examples: > - | > - ahci-glue@65700000 { > + sata-controller@65700000 { But is this really the SATA controller aka AHCI? In cases where we don't have a standardized name, I don't think it makes sense changing node names from one non-standard name to another. > compatible = "socionext,uniphier-pxs3-ahci-glue", > "simple-mfd"; > #address-cells = <1>; > #size-cells = <1>; > ranges = <0 0x65700000 0x100>; > > - ahci_phy: phy@10 { > + ahci_phy: sata-phy@10 { > compatible = "socionext,uniphier-pxs3-ahci-phy"; > reg = <0x10 0x10>; > #phy-cells = <0>; > -- > 2.25.1 > >
Hi Rob, On 2022/10/29 4:38, Rob Herring wrote: > On Thu, Oct 27, 2022 at 01:49:20PM +0900, Kunihiko Hayashi wrote: >> The word "glue" is ambiguous for the controller node name. Should put >> "sata-controller" instead of "ahci-glue" on the controller node. >> And rename a phy node to "sata-phy". >> >> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> >> --- >> .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml | 4 ++-- >> 1 file changed, 2 insertions(+), 2 deletions(-) >> >> diff --git > a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml >> index a3cd45acea28..89b8b133777a 100644 >> --- a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. > yaml >> +++ b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. > yaml >> @@ -117,14 +117,14 @@ additionalProperties: false >> >> examples: >> - | >> - ahci-glue@65700000 { >> + sata-controller@65700000 { > > But is this really the SATA controller aka AHCI? > > In cases where we don't have a standardized name, I don't think it makes > sense changing node names from one non-standard name to another. I see. This can't be named generic, so this change will drop. And "sata-phy" in the same way. Thank you, --- Best Regards Kunihiko Hayashi
On Tue, Nov 1, 2022 at 4:10 AM Kunihiko Hayashi <hayashi.kunihiko@socionext.com> wrote: > > Hi Rob, > > On 2022/10/29 4:38, Rob Herring wrote: > > On Thu, Oct 27, 2022 at 01:49:20PM +0900, Kunihiko Hayashi wrote: > >> The word "glue" is ambiguous for the controller node name. Should put > >> "sata-controller" instead of "ahci-glue" on the controller node. > >> And rename a phy node to "sata-phy". > >> > >> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> > >> --- > >> .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml | 4 ++-- > >> 1 file changed, 2 insertions(+), 2 deletions(-) > >> > >> diff --git > > a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > > b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > >> index a3cd45acea28..89b8b133777a 100644 > >> --- a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. > > yaml > >> +++ b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. > > yaml > >> @@ -117,14 +117,14 @@ additionalProperties: false > >> > >> examples: > >> - | > >> - ahci-glue@65700000 { > >> + sata-controller@65700000 { > > > > But is this really the SATA controller aka AHCI? > > > > In cases where we don't have a standardized name, I don't think it makes > > sense changing node names from one non-standard name to another. > > I see. This can't be named generic, so this change will drop. > And "sata-phy" in the same way. I think sata-phy is fine. It may not be added, but usb3-phy or pcie-phy are common already. Rob
On 2022/11/02 4:31, Rob Herring wrote: > On Tue, Nov 1, 2022 at 4:10 AM Kunihiko Hayashi > <hayashi.kunihiko@socionext.com> wrote: >> >> Hi Rob, >> >> On 2022/10/29 4:38, Rob Herring wrote: >>> On Thu, Oct 27, 2022 at 01:49:20PM +0900, Kunihiko Hayashi wrote: >>>> The word "glue" is ambiguous for the controller node name. Should put >>>> "sata-controller" instead of "ahci-glue" on the controller node. >>>> And rename a phy node to "sata-phy". >>>> >>>> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> >>>> --- >>>> .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml | 4 >>>> ++-- >>>> 1 file changed, 2 insertions(+), 2 deletions(-) >>>> >>>> diff --git >>> a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml >>> b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml >>>> index a3cd45acea28..89b8b133777a 100644 >>>> --- >>>> a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. >>> yaml >>>> +++ >>>> b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. >>> yaml >>>> @@ -117,14 +117,14 @@ additionalProperties: false >>>> >>>> examples: >>>> - | >>>> - ahci-glue@65700000 { >>>> + sata-controller@65700000 { >>> >>> But is this really the SATA controller aka AHCI? >>> >>> In cases where we don't have a standardized name, I don't think it makes >>> sense changing node names from one non-standard name to another. >> >> I see. This can't be named generic, so this change will drop. >> And "sata-phy" in the same way. > > I think sata-phy is fine. It may not be added, but usb3-phy or > pcie-phy are common already. I understand. But of cource "phy" is also common, so I defer the change from "phy" to "sata-phy". Thank you, --- Best Regards Kunihiko Hayashi
On 02-11-22, 08:14, Kunihiko Hayashi wrote: > On 2022/11/02 4:31, Rob Herring wrote: > > On Tue, Nov 1, 2022 at 4:10 AM Kunihiko Hayashi > > <hayashi.kunihiko@socionext.com> wrote: > > > > > > Hi Rob, > > > > > > On 2022/10/29 4:38, Rob Herring wrote: > > > > On Thu, Oct 27, 2022 at 01:49:20PM +0900, Kunihiko Hayashi wrote: > > > > > The word "glue" is ambiguous for the controller node name. Should put > > > > > "sata-controller" instead of "ahci-glue" on the controller node. > > > > > And rename a phy node to "sata-phy". > > > > > > > > > > Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> > > > > > --- > > > > > .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml | 4 > > > > > ++-- > > > > > 1 file changed, 2 insertions(+), 2 deletions(-) > > > > > > > > > > diff --git > > > > a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > > > > b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > > > > > index a3cd45acea28..89b8b133777a 100644 > > > > > --- > > > > > a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. > > > > yaml > > > > > +++ > > > > > b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. > > > > yaml > > > > > @@ -117,14 +117,14 @@ additionalProperties: false > > > > > > > > > > examples: > > > > > - | > > > > > - ahci-glue@65700000 { > > > > > + sata-controller@65700000 { > > > > > > > > But is this really the SATA controller aka AHCI? > > > > > > > > In cases where we don't have a standardized name, I don't think it makes > > > > sense changing node names from one non-standard name to another. > > > > > > I see. This can't be named generic, so this change will drop. > > > And "sata-phy" in the same way. > > > > I think sata-phy is fine. It may not be added, but usb3-phy or > > pcie-phy are common already. > I understand. But of cource "phy" is also common, so I defer the change > from "phy" to "sata-phy". Should it not be just phy@xxx does it really need to be foo-phy?
Hi Vinod, On 2022/11/05 16:34, Vinod Koul wrote: > On 02-11-22, 08:14, Kunihiko Hayashi wrote: >> On 2022/11/02 4:31, Rob Herring wrote: >>> On Tue, Nov 1, 2022 at 4:10 AM Kunihiko Hayashi >>> <hayashi.kunihiko@socionext.com> wrote: >>>> >>>> Hi Rob, >>>> >>>> On 2022/10/29 4:38, Rob Herring wrote: >>>>> On Thu, Oct 27, 2022 at 01:49:20PM +0900, Kunihiko Hayashi wrote: >>>>>> The word "glue" is ambiguous for the controller node name. > Should put >>>>>> "sata-controller" instead of "ahci-glue" on the controller node. >>>>>> And rename a phy node to "sata-phy". >>>>>> >>>>>> Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com> >>>>>> --- >>>>>> .../devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml > | 4 >>>>>> ++-- >>>>>> 1 file changed, 2 insertions(+), 2 deletions(-) >>>>>> >>>>>> diff --git >>>>> > a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml >>>>> > b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml >>>>>> index a3cd45acea28..89b8b133777a 100644 >>>>>> --- >>>>>> > a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. >>>>> yaml >>>>>> +++ >>>>>> > b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy. >>>>> yaml >>>>>> @@ -117,14 +117,14 @@ additionalProperties: false >>>>>> >>>>>> examples: >>>>>> - | >>>>>> - ahci-glue@65700000 { >>>>>> + sata-controller@65700000 { >>>>> >>>>> But is this really the SATA controller aka AHCI? >>>>> >>>>> In cases where we don't have a standardized name, I don't think it > makes >>>>> sense changing node names from one non-standard name to another. >>>> >>>> I see. This can't be named generic, so this change will drop. >>>> And "sata-phy" in the same way. >>> >>> I think sata-phy is fine. It may not be added, but usb3-phy or >>> pcie-phy are common already. >> I understand. But of cource "phy" is also common, so I defer the change >> from "phy" to "sata-phy". > > Should it not be just phy@xxx does it really need to be foo-phy? This change was pointed out in the previous review for our devicetree, so I made this change in the devicetree, however, I think I can leave it as "phy" until the properties that depend on "sata-phy" are defined. Thank you, --- Best Regards Kunihiko Hayashi
diff --git a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml index a3cd45acea28..89b8b133777a 100644 --- a/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml +++ b/Documentation/devicetree/bindings/phy/socionext,uniphier-ahci-phy.yaml @@ -117,14 +117,14 @@ additionalProperties: false examples: - | - ahci-glue@65700000 { + sata-controller@65700000 { compatible = "socionext,uniphier-pxs3-ahci-glue", "simple-mfd"; #address-cells = <1>; #size-cells = <1>; ranges = <0 0x65700000 0x100>; - ahci_phy: phy@10 { + ahci_phy: sata-phy@10 { compatible = "socionext,uniphier-pxs3-ahci-phy"; reg = <0x10 0x10>; #phy-cells = <0>;