Re: [PATCH 1/3] dt-bindings: display: msm: Allow two MDSS power domains

Dmitry Baryshkov <[email protected]>
Newsgroups org.freedesktop.lists.dri-devel,org.kernel.vger.linux-arm-msm,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel
Message-ID <44exzg6xzsxsgfspasbfwdi6mkovpoon6rsz4ahsomcveuvmkg@jau2b6lutygo>
On Thu, Aug 13, 2026 at 03:45:18PM +0800, Yongxing Mou wrote:
> 
> 
> On 7/24/2026 5:36 PM, Krzysztof Kozlowski wrote:
> > On Mon, Jul 20, 2026 at 04:43:53PM +0800, Yongxing Mou wrote:
> > > Kaanapali (SM8750) and Glymur use two display power domains.
> > > CORE_GDSC powers the main display hardware while INT2_GDSC
> > > powers a subset of SSPP blocks.
> > > 
> > > Allow the MDSS bindings to describe both power domains and
> > > their corresponding power-domain-names values.
> > > 
> > > Signed-off-by: Yongxing Mou <[email protected]>
> > > ---
> > >   .../devicetree/bindings/display/msm/mdss-common.yaml        |  3 ++-
> > >   .../devicetree/bindings/display/msm/qcom,glymur-mdss.yaml   | 13 ++++++++++++-
> > >   .../bindings/display/msm/qcom,kaanapali-mdss.yaml           | 13 ++++++++++++-
> > >   3 files changed, 26 insertions(+), 3 deletions(-)
> > > 
> > > diff --git a/Documentation/devicetree/bindings/display/msm/mdss-common.yaml b/Documentation/devicetree/bindings/display/msm/mdss-common.yaml
> > > index c6305a6e0334..c0b650ffd9ef 100644
> > > --- a/Documentation/devicetree/bindings/display/msm/mdss-common.yaml
> > > +++ b/Documentation/devicetree/bindings/display/msm/mdss-common.yaml
> > > @@ -31,7 +31,8 @@ properties:
> > >       const: mdss
> > >     power-domains:
> > > -    maxItems: 1
> > > +    minItems: 1
> > > +    maxItems: 2
> > 
> > So all deviecs now get 2 domains and this is completely ignored in the
> > commit msg.
> > 
> > Best regards,
> > Krzysztof
> > 
> Thanks, will modify a proper commit message next version.


And add if, enforcing either minItems:2 or maxItems:1 depending on the
compat.

-- 
With best wishes
Dmitry
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.