Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp56553rwl; Wed, 4 Jan 2023 15:08:14 -0800 (PST) X-Google-Smtp-Source: AMrXdXtDos750f0gBEq/h48bdvZN/QrTuDEltzjM3P5NSHv+ar0FOkDQdQzdj3MSaUFpsRPmXTf1 X-Received: by 2002:a17:906:a1d2:b0:7c0:fd1a:79ef with SMTP id bx18-20020a170906a1d200b007c0fd1a79efmr42797799ejb.48.1672873693971; Wed, 04 Jan 2023 15:08:13 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1672873693; cv=none; d=google.com; s=arc-20160816; b=TxRdEpfJZrNMzNVKaM0mCIo8bJJLaBevJVyXusU2bbj0O0gUUu5ALsycw4gefpR4zb LgXW0iQ4lrezK5kl479Nj4LVGd5sA/wAYSPWWzBAMzC5ezfm8l2ncfpjZEGcwopZUbJa upX/3JcWs1rjmtiBUKJpOlky7kN30v4Bqn/blda12zUVzXdpq4e/qfIvMKsTdVeYaXBm DKtWVSemECNY/HuDoUiFbCBXfNvNG+LsUtGTL4DzH0RFqPjJKtWorzZGYRHtvDNjlK62 XDnHR6g4WvHvERaQ1bztYbO7RQ+Pt3UBL4Xaxd82Fw85/acBOmtaR9geTwXRjRCJdGDw YjEQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=YcNoql4sxZAAG0Z9x382x27f16j/NJH8gvjDj7DBfeY=; b=Gt19rXB05x/2KFYzcVULcgRahMnZGWFiT4z9XMFjqP66zogciXdBdLwoKiTafiN5FR VOfIVy/ZjJSWwbfIn/K1FIXQ0lnG4X6DKNItpsUDnqpIXu7q+9CSSdUWwLORR5qXeo+j /4ArfkW0REwJvD2fGqF1rpBGZoWXxSnclEhg1yTkd0D4naw2qn+D2yb80KEBqY1qaw8A 3Pd6z8JDzf301T1/uxOTv8MmT+6rOuhZekWRy3AvJh/yw74W+gMohiCGP3RiPhuHtsjm wOEIn1aZNQWsvShcpEGAyu/6dhegtW+8Dxvullw3H/qeygH/2J+v+6H+1CB1LWvGESFf SZPg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=ohe7m4zr; 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 xj11-20020a170906db0b00b0078d3b940ec5si31994944ejb.373.2023.01.04.15.07.58; Wed, 04 Jan 2023 15:08:13 -0800 (PST) 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=ohe7m4zr; 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 S240341AbjADWiC (ORCPT + 58 others); Wed, 4 Jan 2023 17:38:02 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51986 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235536AbjADWh7 (ORCPT ); Wed, 4 Jan 2023 17:37:59 -0500 Received: from mail-il1-x131.google.com (mail-il1-x131.google.com [IPv6:2607:f8b0:4864:20::131]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BB1971D0DE for ; Wed, 4 Jan 2023 14:37:58 -0800 (PST) Received: by mail-il1-x131.google.com with SMTP id d10so20236533ilc.12 for ; Wed, 04 Jan 2023 14:37:58 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=YcNoql4sxZAAG0Z9x382x27f16j/NJH8gvjDj7DBfeY=; b=ohe7m4zraaZuCG6StlOr3NDElGbtNTt/AgB57cgRJ7fR/62RRKlU/4Kkq1hw+ths9X H+IwFo9T4WLorbzXH15hXAuWYP0qA7UDgvG6zA0vgTCHsVQaPXB9tzFAp3rNEU/pjGFP Aj6X4ML3gX7K7csd049yNiopXlnTHatPghoj0= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=YcNoql4sxZAAG0Z9x382x27f16j/NJH8gvjDj7DBfeY=; b=LoR3pS/R1SV5L/oCA2Dk+4HX4k1ZebEsixh6NS0QkI7K+/7BXHTQqisNRNcMmL6jCh qC82dNxT5B1UR+8LITtLaho1izG7O4SAF168mxahuldPDSZ/AaY4WvuTVEzEu0EbmWnw QoPpaGPlHm4oZEOg52eUm1+eG5uTq/7NW6ah87bA233QLZFchU9pBQSAzRiFNj2tiZyP wqnPgkIc0QTU1Sb5fw6j2aSR/uX4SZ7PrvH+6n06VqexuVN6cwXzc1FZdN9ehsLwPGwN szKjfeqJETr+IcF2N+MVEQtsLfLkEN6tiF54wz48okoxw8w/EiTO7NnhpZPfErcCsTO7 C7yA== X-Gm-Message-State: AFqh2kolvEE67UGqmiYSu6QrtgbO6LAFL3vLDHFhmtMFKZHWyqiRjddv WnQclVf9mpPgYfFq4c32uNsZAbarGYEwMLSa X-Received: by 2002:a05:6e02:b2c:b0:304:c95e:8c36 with SMTP id e12-20020a056e020b2c00b00304c95e8c36mr39114239ilu.14.1672871878123; Wed, 04 Jan 2023 14:37:58 -0800 (PST) Received: from localhost (30.23.70.34.bc.googleusercontent.com. [34.70.23.30]) by smtp.gmail.com with UTF8SMTPSA id r22-20020a02b116000000b00363ec4dcaacsm11304062jah.22.2023.01.04.14.37.57 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Jan 2023 14:37:57 -0800 (PST) Date: Wed, 4 Jan 2023 22:37:57 +0000 From: Matthias Kaehlcke To: Anand Moon Cc: Greg Kroah-Hartman , Rob Herring , Krzysztof Kozlowski , linux-amlogic@lists.infradead.org, linux-usb@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v1 08/11] dt-bindings: usb: Add binding for Via lab VL817Q7 hub controller Message-ID: References: <20221228100321.15949-1-linux.amoon@gmail.com> <20221228100321.15949-9-linux.amoon@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20221228100321.15949-9-linux.amoon@gmail.com> X-Spam-Status: No, score=-2.1 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 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: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 28, 2022 at 10:03:17AM +0000, Anand Moon wrote: > The VIA Lab VL817-Q7 is a USB 3.1 Gen 1 4-Port hub controller that > features 4 downstream ports, an internal 5V regulator and has > external reset pin. > > Add a device tree binding for its USB protocol part. > The internal LDO is not covered by this and can just be modelled > as a fixed regulator. > > Signed-off-by: Anand Moon > --- > .../bindings/usb/vialab,vl817q7.yaml | 47 +++++++++++++++++++ > 1 file changed, 47 insertions(+) > create mode 100644 Documentation/devicetree/bindings/usb/vialab,vl817q7.yaml > > diff --git a/Documentation/devicetree/bindings/usb/vialab,vl817q7.yaml b/Documentation/devicetree/bindings/usb/vialab,vl817q7.yaml > new file mode 100644 > index 000000000000..4ae995160fd5 > --- /dev/null > +++ b/Documentation/devicetree/bindings/usb/vialab,vl817q7.yaml > @@ -0,0 +1,47 @@ > +# SPDX-License-Identifier: GPL-2.0-only or BSD-2-Clause > +%YAML 1.2 > +--- > +$schema: http://devicetree.org/meta-schemas/core.yaml# > + > +title: Via labs VL817Q7 USB 3.1 hub controller nit: VIA Labs VL817-Q7 > + > +maintainers: > + - Anand Moon > + > +allOf: > + - $ref: usb-device.yaml# > + > +properties: > + compatible: > + enum: > + - vialab,usb2109 This is not a valid compatible string as Johan already noted. Besides that the VL817-Q7 provides both a 3.1 and a 2.0 USB hub, which are enumerated separately. Please also add a compatible string for the 2.0 hub (assuming 0x2109 is the 3.1 hub). > + > + reg: true > + > + reset-gpios: > + description: GPIO controlling the RESET# pin. > + > + vdd-supply: > + description: > + the regulator that provides 5.0V core power to the hub. > + > +required: > + - compatible > + - reg > + > +additionalProperties: false > + > +examples: > + - | > + #include > + usb { > + dr_mode = "host"; > + #address-cells = <1>; > + #size-cells = <0>; > + > + hub: hub@1 { > + compatible = "vialab,usb2109" > + reg = <1>; > + reset-gpios = <&gpio GPIOH_4 GPIO_ACTIVE_LOW>; > + }; Please also add a node for the other hub and link the two nodes with each other through the 'peer-hub' property. See realtek,rts5411.yaml for reference.