Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4495246pxj; Tue, 22 Jun 2021 01:18:16 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwMfY6yXbabLwThemmIUbO/RcUj1sa06wBWeNfIq7HEwCxS9bjMKXEuPnBdemaZ5natgSN2 X-Received: by 2002:a02:2547:: with SMTP id g68mr2755997jag.24.1624349896161; Tue, 22 Jun 2021 01:18:16 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1624349896; cv=none; d=google.com; s=arc-20160816; b=WrOu9icbkk3tH6UBvX9DiIeTzpwMWWr4rB2OtZl8d70A07UrdImg0HPLNp3nYaLav0 6BobrY5IVNteEUR5YjZEEnHQtVHwAbrk4rSn3d9VeqIt+BahgMv8vFfZGK2o2LY+Jyfp iHoSGYSawp57cUE7p4PMOr9275vG49ybZ/DCMXMZoSps8WfexW05n6A3ILXwhNGMzl/C CivHiDAhXjIUSQyp3bM2HXhDXDwl4VrenHBocqTVs+oaMPnTeJHItwELj94cM77R7L6M cBPrQU2Q8G5b6HcSGh0UejOlrvV+rv7iIivgU4fHSwqNaZ8LKJ9SNiUoc1S9KqnTipcw 8ofQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:cc:to:subject:message-id:date:from:in-reply-to :references:mime-version; bh=s0hVMlLFV5eIwzuXXBEJWEV7FxMfuDBGtQwv1PuAfDc=; b=LAQG0Ua4Vx6N62q4i4eVHjvb/yJyLaRhYn28g2liaubznXRQ6PUiK6KZs7Evff2D+E gcpFsKFE0/6UfEdhl0HSaDzNpy8qHQSXgPzry2qUIS+oHH+owpUU9B4KEbmLZ/V4XEIZ qCCcKi97MPYe4SIM9fRFbN6CYiTfBHJhOPQV0FBRapiRiJp+dibnKXU+AxW+dfQQXguu Emvxxx+1n35xrdnCxFzi8vpaLIUhujZ6rqfTLJiQv66THYQYQ4iO5dwV+hYspJ5vEK3/ +Y/Cj50zKefKGoHjJXbKtddRSB7fgVBcZagmSXnB2FXDtzo7T4bYPEgzMFJjDQqRk6ey B6Ww== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id y7si22405857jae.125.2021.06.22.01.17.56; Tue, 22 Jun 2021 01:18:16 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-crypto-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-crypto-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229954AbhFVIT7 (ORCPT + 99 others); Tue, 22 Jun 2021 04:19:59 -0400 Received: from mail-vs1-f54.google.com ([209.85.217.54]:46782 "EHLO mail-vs1-f54.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229844AbhFVIT7 (ORCPT ); Tue, 22 Jun 2021 04:19:59 -0400 Received: by mail-vs1-f54.google.com with SMTP id z15so10758892vsn.13; Tue, 22 Jun 2021 01:17:41 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=s0hVMlLFV5eIwzuXXBEJWEV7FxMfuDBGtQwv1PuAfDc=; b=Yc8JShUBMH1dnjUYyQ4i3CS2+y2GF6q1YtRwv/bRUTq4JGwOzFH8jz0/QYnr8ZuDpr HcEesiBUGFsp/umSzAQ1ucxKn54tANWqVfYyhNDVX62VWxoC03W6vKFzSWDS1INIUujo EfpD0ZvANCW00iJ41ZnsyYqUYQ7WKnBJFLN0taGCgErNoNfbEbrJRexR6AwIwIKT2Knb /0emor8cfQJbNOnIXhfpVS1iQMsX9FEwTZTkt2w2NsDGz2POO5RqhJxIgP7TG7ACSbj/ GkkcJgg3HdSB+eNLe7DKVV3GNyEiHob+PVe9RVIKAdqt1PMr45YhOFebl4O9XRmtiOlY SQDQ== X-Gm-Message-State: AOAM530BLNzCLpsQ3ZsdxG/iSlElsnvEgk5f19JQOeLC0TziQs7pI7vp kFMx7YZsKONrP5YDTSXRni3TndxcwI12ri99DDk= X-Received: by 2002:a05:6102:2011:: with SMTP id p17mr21421376vsr.40.1624349860512; Tue, 22 Jun 2021 01:17:40 -0700 (PDT) MIME-Version: 1.0 References: <20210615191543.1043414-1-robh@kernel.org> In-Reply-To: <20210615191543.1043414-1-robh@kernel.org> From: Geert Uytterhoeven Date: Tue, 22 Jun 2021 10:17:28 +0200 Message-ID: Subject: Re: [PATCH] dt-bindings: Drop redundant minItems/maxItems To: Rob Herring Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Linux Kernel Mailing List , linux-ide@vger.kernel.org, linux-clk , Linux ARM , Linux Crypto Mailing List , DRI Development , dmaengine , Linux I2C , linux-iio@vger.kernel.org, ALSA Development Mailing List , Linux IOMMU , Linux Media Mailing List , Linux MMC List , netdev , linux-can@vger.kernel.org, linux-pci , linux-phy@lists.infradead.org, "open list:GPIO SUBSYSTEM" , Linux PWM List , "open list:REMOTE PROCESSOR (REMOTEPROC) SUBSYSTEM" , linux-riscv , linux-rtc@vger.kernel.org, "open list:SERIAL DRIVERS" , linux-spi , Linux PM list , USB list , Linux Watchdog Mailing List , Jens Axboe , Stephen Boyd , Herbert Xu , "David S. Miller" , David Airlie , Daniel Vetter , Vinod Koul , Bartosz Golaszewski , Kamal Dasu , Jonathan Cameron , Lars-Peter Clausen , Thomas Gleixner , Marc Zyngier , Joerg Roedel , Jassi Brar , Mauro Carvalho Chehab , Krzysztof Kozlowski , Ulf Hansson , Jakub Kicinski , Wolfgang Grandegger , Marc Kleine-Budde , Andrew Lunn , Vivien Didelot , Vladimir Oltean , Bjorn Helgaas , Kishon Vijay Abraham I , Linus Walleij , =?UTF-8?Q?Uwe_Kleine=2DK=C3=B6nig?= , Lee Jones , Ohad Ben-Cohen , Mathieu Poirier , Philipp Zabel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Alessandro Zummo , Alexandre Belloni , Greg Kroah-Hartman , Mark Brown , Zhang Rui , Daniel Lezcano , Wim Van Sebroeck , Guenter Roeck Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-crypto@vger.kernel.org Hi Rob, On Tue, Jun 15, 2021 at 9:16 PM Rob Herring wrote: > If a property has an 'items' list, then a 'minItems' or 'maxItems' with the > same size as the list is redundant and can be dropped. Note that is DT > schema specific behavior and not standard json-schema behavior. The tooling > will fixup the final schema adding any unspecified minItems/maxItems. > > This condition is partially checked with the meta-schema already, but > only if both 'minItems' and 'maxItems' are equal to the 'items' length. > An improved meta-schema is pending. > Signed-off-by: Rob Herring > --- a/Documentation/devicetree/bindings/net/stm32-dwmac.yaml > +++ b/Documentation/devicetree/bindings/net/stm32-dwmac.yaml > @@ -46,7 +46,6 @@ properties: > > clocks: > minItems: 3 > - maxItems: 5 > items: > - description: GMAC main clock > - description: MAC TX clock While resolving the conflict with commit fea99822914039c6 ("dt-bindings: net: document ptp_ref clk in dwmac") in soc/for-next, I noticed the following construct for clock-names: clock-names: minItems: 3 maxItems: 6 contains: enum: - stmmaceth - mac-clk-tx - mac-clk-rx - ethstp - eth-ck - ptp_ref Should this use items instead of enum, and drop maxItems, or is this a valid construct to support specifying the clocks in random order? If the latter, it does mean that the order of clock-names may not match the order of the clock descriptions. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds