From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from perceval.ideasonboard.com (perceval.ideasonboard.com [213.167.242.64]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 997791FF7B0; Mon, 16 Dec 2024 08:33:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=213.167.242.64 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734337986; cv=none; b=BgOW6ImCLytCRGZMvD8MjteSw5DitDXn8b+h6/E34gEzEBhATPfpnuFOvFff7CkPnSYmUgSE34zSsy8f8c0pazdYevx4bbkuj26+mtY0ftPD5n4c9Z/x+2Kv5/xvEg9TjCqxJRVrnKI+NYfFCR44wB4oiGgvItux1qlXyVVbNZw= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1734337986; c=relaxed/simple; bh=6jLd1uN34169vrHjBxynJiQD7DGybjgKDzBNRxxHp6U=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=eH9TrD4ZgK45H4rlJ8FWByWc73/ACt9IpaukcE6cLy+VF2AnrTYYGs9+JJc7itQj0/tUY2PPTY9dUhGNG+hpQxL08hRCnCtRLeJO7zOjRWbLfrTRD6XTQ5TUtgeEC4lsVpnwUm28vLxe3iivogBKOzFlVqrG/awOyPy7UtFqX7U= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=ideasonboard.com; spf=pass smtp.mailfrom=ideasonboard.com; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b=pT5HXt8Q; arc=none smtp.client-ip=213.167.242.64 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=ideasonboard.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=ideasonboard.com header.i=@ideasonboard.com header.b="pT5HXt8Q" Received: from pendragon.ideasonboard.com (81-175-209-231.bb.dnainternet.fi [81.175.209.231]) by perceval.ideasonboard.com (Postfix) with ESMTPSA id 664BB13C; Mon, 16 Dec 2024 09:32:19 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ideasonboard.com; s=mail; t=1734337939; bh=6jLd1uN34169vrHjBxynJiQD7DGybjgKDzBNRxxHp6U=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=pT5HXt8Qdd6jf0+ZGRGtk1o4+1AH4aQzdWQwgML2CYEP/cuVeM56ZZ2d1YskSx/Xw HGsXaNRyzjIg5wQMdPKDmoAdOWBJK6RbEq+840ZJP3U6icjbw3MpwtPSwq9MEm78BE 6U/DGkmH3oYCgNBpcax0QcI4j08ONGFQG/yIgwvo= Date: Mon, 16 Dec 2024 10:32:39 +0200 From: Laurent Pinchart To: Krzysztof Kozlowski Cc: Tomi Valkeinen , Kieran Bingham , Andrzej Hajda , Neil Armstrong , Robert Foss , Jonas Karlman , Jernej Skrabec , David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Geert Uytterhoeven , Magnus Damm , Michael Turquette , Stephen Boyd , LUU HOAI , Jagan Teki , Sam Ravnborg , Biju Das , dri-devel@lists.freedesktop.org, linux-renesas-soc@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org, Tomi Valkeinen Subject: Re: [PATCH v4 3/7] dt-bindings: display: renesas,du: Add missing maxItems Message-ID: <20241216083239.GC32204@pendragon.ideasonboard.com> References: <20241213-rcar-gh-dsi-v4-0-f8e41425207b@ideasonboard.com> <20241213-rcar-gh-dsi-v4-3-f8e41425207b@ideasonboard.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: Hi Krzysztof, On Mon, Dec 16, 2024 at 08:58:49AM +0100, Krzysztof Kozlowski wrote: > On Fri, Dec 13, 2024 at 04:02:59PM +0200, Tomi Valkeinen wrote: > > From: Tomi Valkeinen > > > > The binding is missing maxItems for all renesas,cmms and renesas,vsps > > properties. As the amount of cmms or vsps is always a fixed amount, set > > the maxItems to match the minItems. > > > > Signed-off-by: Tomi Valkeinen > > --- > > Documentation/devicetree/bindings/display/renesas,du.yaml | 10 ++++++++++ > > 1 file changed, 10 insertions(+) > > The top level property should define widest constraints as well. I'm curious, why is that ? I understand why a top-level default would make sense when it's optionally overridden by model-specific values, but in this case there's no such default. Every SoC has its own fixed value. -- Regards, Laurent Pinchart