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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id E4C70C7EE2A for ; Mon, 5 Jun 2023 12:55:12 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233655AbjFEMyu (ORCPT ); Mon, 5 Jun 2023 08:54:50 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46294 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232885AbjFEMyt (ORCPT ); Mon, 5 Jun 2023 08:54:49 -0400 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id DEF51113; Mon, 5 Jun 2023 05:54:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1685969679; x=1717505679; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=a+Tn4FBYo0QLrStvlRhVV+bb1iI8O3ndmJkkVSEip2g=; b=UrrUXL2U0aZ/WMYl2TJe4L43Ci0uiIw0ckuebDEMyk9b1eYP6uiGyDm1 QZRIV5jHc+n3XRaeYEk9uhNAYpdU2xGvA9w52JKjIivntKsEBbxQD2gtz qLodBXgsC8Dy07GEB+uZMJN37HwXju2ZVRXY/bIs1nLrGaza64xOwcBJQ G29brtYJmJpxPcnYi7M52et78zAPQL+akRqBoScTHRNyJDz4lM9jDd8g1 1LasS3xwWpcnIVFa5nO4dqBT6YxnWjGudYhHeJTwJ377WKs6Krxz7FUhu trA+KDCqek4yAFVl+Y/jpwvIaP/209vgvOlQBUweu+/2y2F8ZCCq5d+yY Q==; X-IronPort-AV: E=Sophos;i="6.00,217,1681196400"; d="scan'208";a="155562864" X-Amp-Result: SKIPPED(no attachment in message) Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa6.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 05 Jun 2023 05:54:38 -0700 Received: from chn-vm-ex04.mchp-main.com (10.10.85.152) by chn-vm-ex01.mchp-main.com (10.10.85.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Mon, 5 Jun 2023 05:54:37 -0700 Received: from [10.159.245.112] (10.10.115.15) by chn-vm-ex04.mchp-main.com (10.10.85.152) with Microsoft SMTP Server id 15.1.2507.21 via Frontend Transport; Mon, 5 Jun 2023 05:54:25 -0700 Message-ID: Date: Mon, 5 Jun 2023 14:54:18 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: [PATCH 03/21] dt-bindings: usb: generic-ehci: Document clock-names property Content-Language: en-US To: Conor Dooley , Varshini Rajendran CC: , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , References: <20230603200243.243878-1-varshini.rajendran@microchip.com> <20230603200243.243878-4-varshini.rajendran@microchip.com> <20230603-skincare-ideology-bfbc3fd384c5@spud> From: Nicolas Ferre Organization: microchip In-Reply-To: <20230603-skincare-ideology-bfbc3fd384c5@spud> Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On 03/06/2023 at 23:15, Conor Dooley wrote: > Hey Varshini, > > On Sun, Jun 04, 2023 at 01:32:25AM +0530, Varshini Rajendran wrote: >> Document the property clock-names in the schema. >> >> It fixes the dtbs_warning, > s/dtbs_warning/dtbs_check warning/? > >> 'clock-names' does not match any of the regexes: 'pinctrl-[0-9]+' > Does this fix a warning currently in the tree, or fix a warning > introduced by some patches in this series? (Or both?) Our USB DT pattern is the same on all our newer SoC, to it mustn't be introduced by the addition of this one. Best regards, Nicolas >> Signed-off-by: Varshini Rajendran >> --- >> Documentation/devicetree/bindings/usb/generic-ehci.yaml | 4 ++++ >> 1 file changed, 4 insertions(+) >> >> diff --git a/Documentation/devicetree/bindings/usb/generic-ehci.yaml b/Documentation/devicetree/bindings/usb/generic-ehci.yaml >> index 7e486cc6cfb8..542ac26960fc 100644 >> --- a/Documentation/devicetree/bindings/usb/generic-ehci.yaml >> +++ b/Documentation/devicetree/bindings/usb/generic-ehci.yaml >> @@ -102,6 +102,10 @@ properties: >> - if a USB DRD channel: first clock should be host and second >> one should be peripheral >> >> + clock-names: >> + minItems: 1 >> + maxItems: 4 >> + >> power-domains: >> maxItems: 1 >> >> -- >> 2.25.1 -- Nicolas Ferre