From: Devarsh Thakkar <devarsht@ti.com>
To: Maxime Ripard <mripard@kernel.org>
Cc: <jyri.sarha@iki.fi>, <tomi.valkeinen@ideasonboard.com>,
<airlied@gmail.com>, <daniel@ffwll.ch>,
<maarten.lankhorst@linux.intel.com>, <tzimmermann@suse.de>,
<dri-devel@lists.freedesktop.org>, <linux-kernel@vger.kernel.org>,
<praneeth@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<a-bhatia1@ti.com>, <j-luthra@ti.com>, <r-ravikumar@ti.com>,
<j-choudhary@ti.com>
Subject: Re: [PATCH] drm/tidss: Power up attached PM domains on probe
Date: Mon, 16 Oct 2023 13:07:21 +0530 [thread overview]
Message-ID: <04a6eefa-235c-c973-8c74-eb8a8982abf4@ti.com> (raw)
In-Reply-To: <libnfyaftywmfr2gmkdjsv6cptzjyrrx2tkxczusifnwthyh36@olzd2e5hagtr>
Hi Maxime,
On 12/10/23 18:10, Maxime Ripard wrote:
> Hi,
>
> On Thu, Oct 12, 2023 at 05:10:06PM +0530, Devarsh Thakkar wrote:
>> On 09/10/23 13:20, Devarsh Thakkar wrote:
>>> Some SoC's such as AM62P have dedicated power domains
>>> for OLDI which need to be powered on separetely 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.
>>>
>>
>> NAK, for this patch, as discussed with team there are already plans
>> to have separate OLDI bridge driver which should eventually handle
>> the additional power domains.
>
> Just for the record in case your current plan doesn't work out and we
> need to revisit this patch: my point was that it's something that
> deviates by a margin from what drivers are usually expected to do, so we
> should document why that deviation is there.
>
Sure, thanks for suggesting, I agree that if going with this logic, we should
definitely put a comment in driver regarding same.
> The patch itself looks reasonable to me otherwise.
Yes, it's just that we are planning a separate driver for OLDI. We will see if
we need similar logic in that driver too.
Regards
Devarsh
>
> Maxime
prev parent reply other threads:[~2023-10-16 7:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 7:50 Devarsh Thakkar
2023-10-09 9:23 ` Maxime Ripard
2023-10-09 11:10 ` Devarsh Thakkar
2023-10-12 8:45 ` Devarsh Thakkar
2023-10-12 11:40 ` Devarsh Thakkar
2023-10-12 12:40 ` Maxime Ripard
2023-10-16 7:37 ` Devarsh Thakkar [this message]
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=04a6eefa-235c-c973-8c74-eb8a8982abf4@ti.com \
--to=devarsht@ti.com \
--cc=a-bhatia1@ti.com \
--cc=airlied@gmail.com \
--cc=daniel@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=j-choudhary@ti.com \
--cc=j-luthra@ti.com \
--cc=jyri.sarha@iki.fi \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=mripard@kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=r-ravikumar@ti.com \
--cc=tomi.valkeinen@ideasonboard.com \
--cc=tzimmermann@suse.de \
--cc=vigneshr@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
all inboxes | Powered by JetHome®