From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-alma10-1.taild15c8.ts.net [100.103.45.18]) (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 C424A3D47C0; Mon, 27 Jul 2026 20:23:33 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=100.103.45.18 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785183814; cv=none; b=ppgmbi7688LrP676uwHq+0qHO4BqZ3UZ7OLJOMyqEwe8nL6V5Ir8Ycqn6ttgo3RqMpEkWUkNhx0rdK5v33dTyHD9AcRE113LlP2fpEJkWzNpyCL9MtCBsUE6+BNa3sEegP5clMXXg0OEODrC5PjR5rrZ7CcfIF+g0ZOqZzMfCSM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1785183814; c=relaxed/simple; bh=dLRDBawlfPihNhf+2UuXBbiWYATERzDVJKZ3oMc8mqE=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=YT8jh1gthRuWVuKSqo4tWZEyxnedF87aVyPf7pdmoN8VsCasl0wXCoCcJjd2cGOs9+GkyWgtBPMYWzlmzxjyyuI9pYDL0Jt58AYkpyxFiA+P83cBVn1oICQ6B86w7qymZk9pwN313nyEAiJo7f+MoA8adQjWh3C/Mnn5XJ20gy4= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=CDRs+v50; arc=none smtp.client-ip=100.103.45.18 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="CDRs+v50" Received: by smtp.kernel.org (Postfix) with ESMTPSA id ABC071F00A3A; Mon, 27 Jul 2026 20:23:32 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=kernel.org; s=k20260515; t=1785183813; bh=roIbNH/RduX4j/JAGLRnJpvgmdn9O369ogKB6aRiAbA=; h=Date:From:To:Cc:Subject:References:In-Reply-To; b=CDRs+v50gJiFQDn8BW+YbATTt/AIpD63bauQmAStdsrLfy2QIN6fnywlDzmam58Wn YM4ljdK273tUDAPX1zMrlnJiH+YQ0jYBv7tSF0PYQuG4PdbL7iSLHoo8S0JK3QCY0e iVmap1Sy838Bi8RvrOD4VBTWphxjEdI98NWdHNkEgDI1tlUEkWExtk3HsSghvMd91i 094q6zBGZzI9lIcwSIBJkAW0wwOccoxKMuGxcnWvjJiNKBVjrO2kEFiOXgAQbKej/D jNq08qw+nsiCMUFPAKnHES79aLYrms671mig3AZT8xKn5iFJPpPlbShlcE3HeUOH2b LtAw3rP/OagAg== Date: Mon, 27 Jul 2026 22:23:29 +0200 From: Krzysztof Kozlowski To: Jun Nie Cc: Rob Clark , Dmitry Baryshkov , Dmitry Baryshkov , Abhinav Kumar , Jessica Zhang , Sean Paul , Marijn Suijten , David Airlie , Simona Vetter , Maarten Lankhorst , Maxime Ripard , Thomas Zimmermann , Neil Armstrong , Rob Herring , Krzysztof Kozlowski , Conor Dooley , linux-arm-msm@vger.kernel.org, dri-devel@lists.freedesktop.org, freedreno@lists.freedesktop.org, linux-kernel@vger.kernel.org, devicetree@vger.kernel.org Subject: Re: [PATCH v5 1/6] dt-bindings: display: panel: Modify reset gpio number constrain Message-ID: <20260727-stirring-miraculous-nautilus-e22bda@quoll> References: <20260727-sm8650-7-1-bonded-dsi-v5-0-c042266b9eeb@linaro.org> <20260727-sm8650-7-1-bonded-dsi-v5-1-c042266b9eeb@linaro.org> Precedence: bulk X-Mailing-List: devicetree@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: <20260727-sm8650-7-1-bonded-dsi-v5-1-c042266b9eeb@linaro.org> On Mon, Jul 27, 2026 at 04:08:40PM +0800, Jun Nie wrote: > Some panel support 2 reset gpio, such as Synaptics R63455. So modify the There is no such binding for R63455. > number constrain of gpio to 1 to avoid check failure. What check failure? Please paste actual warnings (but not fake ones). > > Signed-off-by: Jun Nie > --- > Documentation/devicetree/bindings/display/panel/panel-common.yaml | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/display/panel/panel-common.yaml b/Documentation/devicetree/bindings/display/panel/panel-common.yaml > index 087415753d606..7c450d2799808 100644 > --- a/Documentation/devicetree/bindings/display/panel/panel-common.yaml > +++ b/Documentation/devicetree/bindings/display/panel/panel-common.yaml > @@ -119,7 +119,7 @@ properties: > confused with a backlight enable signal. > > reset-gpios: > - maxItems: 1 > + minItems: 1 I do not get why all bindings now get completely flexible number of resets. I am pretty sure not all of them constrain that. It's rather your task to check it and explain in commit msg. For example the second random I took to check (ILI7807S) does not restrict, so you just made that binding accepting 1000 reset lines. Why? Best regards, Krzysztof