From: Francesco Dolcini <francesco@dolcini.it>
To: Swamil Jain <s-jain1@ti.com>
Cc: jyri.sarha@iki.fi, tomi.valkeinen@ideasonboard.com,
airlied@gmail.com, simona@ffwll.ch,
maarten.lankhorst@linux.intel.com, mripard@kernel.org,
tzimmermann@suse.de, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, aradhya.bhatia@linux.dev,
dri-devel@lists.freedesktop.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, devarsht@ti.com, praneeth@ti.com,
h-shenoy@ti.com, u-kumar1@ti.com
Subject: Re: [PATCH 2/3] drm/tidss: Power up attached PM domains on probe
Date: Fri, 14 Nov 2025 16:39:25 +0100 [thread overview]
Message-ID: <20251114153925.GA62911@francesco-nb> (raw)
In-Reply-To: <20251114064336.3683731-3-s-jain1@ti.com>
Hello Swamil,
thanks for the patch.
On Fri, Nov 14, 2025 at 12:13:35PM +0530, Swamil Jain wrote:
> From: Devarsh Thakkar <devarsht@ti.com>
>
> Some SoC's such as AM62P have dedicated power domains
> for OLDI which need to be powered on separately along
> with display controller.
>
> So during driver probe, power up all attached PM domains
> enumerated in devicetree node for DSS.
>
> This also prepares base to add display support for AM62P.
>
> Signed-off-by: Devarsh Thakkar <devarsht@ti.com>
> [j-choudhary@ti.com: fix PM call sequence causing kernel crash in OLDI]
> Signed-off-by: Jayesh Choudhary <j-choudhary@ti.com>
you need to add your signed-off-by at the end
Francesco
next prev parent reply other threads:[~2025-11-14 15:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 6:43 [PATCH 0/3] Add Display support for AM62P SoC Swamil Jain
2025-11-14 6:43 ` [PATCH 1/3] dt-bindings: display: ti,am65x-dss: Add am62p dss compatible Swamil Jain
2025-11-14 17:58 ` Conor Dooley
2025-11-17 5:10 ` Swamil Jain
2025-11-14 6:43 ` [PATCH 2/3] drm/tidss: Power up attached PM domains on probe Swamil Jain
2025-11-14 15:39 ` Francesco Dolcini [this message]
2025-11-17 5:12 ` Swamil Jain
2025-11-14 6:43 ` [PATCH 3/3] drm: tidss: tidss_drv: Add support for AM62P display subsystem Swamil Jain
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251114153925.GA62911@francesco-nb \
--to=francesco@dolcini.it \
--cc=airlied@gmail.com \
--cc=aradhya.bhatia@linux.dev \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=h-shenoy@ti.com \
--cc=jyri.sarha@iki.fi \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=praneeth@ti.com \
--cc=robh@kernel.org \
--cc=s-jain1@ti.com \
--cc=simona@ffwll.ch \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=u-kumar1@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).