Re: [PATCH 1/3] dt-bindings: display: msm: Allow two MDSS power domains
Yongxing Mou <[email protected]>
| Newsgroups | org.kernel.vger.linux-arm-msm,org.freedesktop.lists.dri-devel,org.kernel.vger.linux-devicetree,org.kernel.vger.linux-kernel |
|---|---|
| Message-ID | <[email protected]> |
On 7/22/2026 2:20 AM, Dmitry Baryshkov 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. > > Another question... If INT2_GDSC only powers up a subset of SSPPs, why > is it being declared as powering up the full MDSS? Can we move it to the > DPU device instead? > Hmm, yes, it only use for VIG2/VIG3/DMA5 here. we can move it to DPU. Since listing more than one power-domain disables auto-attach, a small driver change is needed to attach both domains explicitly — MMCX with PD_FLAG_REQUIRED_OPP to keep performance-state voting working, INT2_GDSC as a plain runtime-PM supplier. >> >> 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(-) >> >