Received: by 2002:a6b:fb09:0:0:0:0:0 with SMTP id h9csp914451iog; Thu, 30 Jun 2022 12:44:33 -0700 (PDT) X-Google-Smtp-Source: AGRyM1vSUeiVFT/Lpx9PpYGFfhUI2Kh+bR6Dwdqk/QRO+NIOtCzTcsymlU6GhQRGhDUhL8wIQ+3S X-Received: by 2002:a17:907:76b2:b0:726:d02f:dee with SMTP id jw18-20020a17090776b200b00726d02f0deemr10208613ejc.249.1656618272792; Thu, 30 Jun 2022 12:44:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1656618272; cv=none; d=google.com; s=arc-20160816; b=LmcCVvEfn/KuQmG31WImSIMtTyiNugb1Wq8P0OaM09oXsLbEGtCaspcYNfDNuN2wZ0 ZUo80qMVj2l7zhJfzpQx8IPB1qOq1sE+BbmTXhLf2zi6PYNQ8Crd545rnaHNBOGHjQar GormHADYs2RP9sjnFp3KwN9wEMSXrj9azZpDHENY2sDv/WQtWekE8fNzYxpZR+oGAq/n j5fCDWWOlN0mnaa8ejKzT9FyypoQXjLqUd2pFiwlbSxeLrnqSEyIo3eqPffsYXyBM1nw aYXpearyMkVjmV9phhvlHhA5RaXgogIHt1jEre+ZffhFCTvNv64hjKKl7aHnw0TENpT3 KQCw== 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 :dkim-signature; bh=JB7sx4mYBlVrOKCS+hcQc2JLyuj+tIa+zut8Qu0t/NQ=; b=IWbRAK2vjoN9YDOJ6RJdcIGK8bFAsFNeM0iKFsj5Vs01eqECdQaIzxxgOuJZBrfkr0 cfjQ3IueXp49QUPD3J1xklplN1Kcd408gicbJ6ObbEB4y7rCUn7Q7n9WOg5UHOobButv n9Tk/YsSxytuxvPXkoe0QF72SsBr0x7oA7s4RniOyFz15ZtY7ZtHDFFQ8uU49ehOKLlx K+H2Cpg3lGlvNJlPx1vuZMaaLgkKtoEiy+JopA5DkEDGy0N36SgdcDg0LbgPtx2Phe8T juWUuqI8cunxca/Wm5obnVX30Vqds9u6CEEUKlR1ukIkLY/h5sA+jQBYJczeCGpyEvBt 3m2g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=lI5oEWJO; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id m1-20020a170906848100b007120eea6a89si6260333ejx.12.2022.06.30.12.44.06; Thu, 30 Jun 2022 12:44:32 -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; dkim=pass header.i=@chromium.org header.s=google header.b=lI5oEWJO; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236896AbiF3Tfo (ORCPT + 99 others); Thu, 30 Jun 2022 15:35:44 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37098 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236875AbiF3Tfk (ORCPT ); Thu, 30 Jun 2022 15:35:40 -0400 Received: from mail-pg1-x52c.google.com (mail-pg1-x52c.google.com [IPv6:2607:f8b0:4864:20::52c]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 89EA743AE9 for ; Thu, 30 Jun 2022 12:35:38 -0700 (PDT) Received: by mail-pg1-x52c.google.com with SMTP id s206so297697pgs.3 for ; Thu, 30 Jun 2022 12:35:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding; bh=JB7sx4mYBlVrOKCS+hcQc2JLyuj+tIa+zut8Qu0t/NQ=; b=lI5oEWJOZMQcBNCfOvOZqTJ/Xl9N3knwLAWjgxn1/3cbDPAoNOY+3/iBboZZ+jvyNm dEycEuE3YzIoxRltEQ7aisfjD1TnMi9lyN0Z/NH64Glv97odgVJ5s+5O7xcnFt27vSyl gGzfij4gfHgf0/CsUhpli7JnrYaXCi2C4Crhk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:in-reply-to :references:mime-version:content-transfer-encoding; bh=JB7sx4mYBlVrOKCS+hcQc2JLyuj+tIa+zut8Qu0t/NQ=; b=YFRrd3Tjqp8QaYgtv4BEtpyLf7oa2B4d1bIB5GCcvhE2sGWq7Zj2i03OFr8ohw4p5+ G37GYN+TByT8YpvGwUyx2N+D8GMo3xXxDacmhRBmWGcIJ+rAOX+KaP7EMayBWE37+oMH P058JG5LME0aiC6/kMc/0JQC8xsYq9nsUlatYP12QiNgW+aR3KFRmyyxNDvAj0qJuaZS X+SswL2S64q334U5OXDTLhOZXrC6dLA0fjTY5T7ASIPRf+OXkcjOXGFwW0hCRCjR3D9x UfnElGo6o3p3KyOyzfufL+roiRjtUnVsEwrQqM9CZUhjgfndW/9MYHKZLeFlZLZNCkZW 6p/g== X-Gm-Message-State: AJIora9wHDpkojDhuJ4IkFbknSj6Svu5BQ2LHWqSCzUmFcDxvXw7os9K z0BG9RXXDjJDubkbPajXK3JBIA== X-Received: by 2002:a63:82c3:0:b0:40c:c340:318d with SMTP id w186-20020a6382c3000000b0040cc340318dmr9035922pgd.191.1656617738025; Thu, 30 Jun 2022 12:35:38 -0700 (PDT) Received: from localhost ([2620:15c:11a:202:9fbf:277c:23e1:eabb]) by smtp.gmail.com with UTF8SMTPSA id p31-20020a056a000a1f00b0051bdb735647sm13936598pfh.159.2022.06.30.12.35.36 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 30 Jun 2022 12:35:37 -0700 (PDT) From: Matthias Kaehlcke To: Greg Kroah-Hartman , Alan Stern , Rob Herring , Frank Rowand , Mathias Nyman , Felipe Balbi Cc: linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, Douglas Anderson , Michal Simek , linux-usb@vger.kernel.org, Ravi Chandra Sadineni , Roger Quadros , Bastien Nocera , Peter Chen , Stephen Boyd , Krzysztof Kozlowski , Matthias Kaehlcke , Krzysztof Kozlowski Subject: [PATCH v24 2/4] dt-bindings: usb: rts5411: Rename property 'companion-hub' to 'peer-hub' Date: Thu, 30 Jun 2022 12:35:28 -0700 Message-Id: <20220630123445.v24.2.Ie2bbbd3f690826404b8f1059d24edcab33ed898f@changeid> X-Mailer: git-send-email 2.37.0.rc0.161.g10f37bed90-goog In-Reply-To: <20220630193530.2608178-1-mka@chromium.org> References: <20220630193530.2608178-1-mka@chromium.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.5 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=unavailable 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 In the context of USB the term 'companion-hub' is misleading, change the name of the property to 'peer-hub'. There are no upstream users of the 'companion-hub' property, neither in the device tree, nor on the driver side, so renaming it shouldn't cause any compatibility issues with existing device trees. Changes in v24: - patch added to the series Signed-off-by: Matthias Kaehlcke --- (no changes since v1) .../devicetree/bindings/usb/realtek,rts5411.yaml | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/Documentation/devicetree/bindings/usb/realtek,rts5411.yaml b/Documentation/devicetree/bindings/usb/realtek,rts5411.yaml index 04ee255eb4f0..50f2b505bdeb 100644 --- a/Documentation/devicetree/bindings/usb/realtek,rts5411.yaml +++ b/Documentation/devicetree/bindings/usb/realtek,rts5411.yaml @@ -25,13 +25,13 @@ properties: description: phandle to the regulator that provides power to the hub. - companion-hub: + peer-hub: $ref: '/schemas/types.yaml#/definitions/phandle' description: - phandle to the companion hub on the controller. + phandle to the peer hub on the controller. required: - - companion-hub + - peer-hub - compatible - reg @@ -49,7 +49,7 @@ examples: compatible = "usbbda,5411"; reg = <1>; vdd-supply = <&pp3300_hub>; - companion-hub = <&hub_3_0>; + peer-hub = <&hub_3_0>; }; /* 3.0 hub on port 2 */ @@ -57,6 +57,6 @@ examples: compatible = "usbbda,411"; reg = <2>; vdd-supply = <&pp3300_hub>; - companion-hub = <&hub_2_0>; + peer-hub = <&hub_2_0>; }; }; -- 2.37.0.rc0.161.g10f37bed90-goog