From: kalyan_t@codeaurora.org
To: Matthias Kaehlcke <mka@chromium.org>
Cc: devicetree@vger.kernel.org, mkrishn@codeaurora.org,
linux-arm-msm@vger.kernel.org, travitej@codeaurora.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
dianders@chromium.org, seanpaul@chromium.org,
hoegsberg@chromium.org, freedreno@lists.freedesktop.org
Subject: Re: [v1] drm/msm/dpu: add support for clk and bw scaling for display
Date: Tue, 14 Jul 2020 16:39:47 +0530 [thread overview]
Message-ID: <38dc4bbfd754175e476252c4bc259d55@codeaurora.org> (raw)
In-Reply-To: <20200714011219.GQ3191083@google.com>
On 2020-07-14 06:42, Matthias Kaehlcke wrote:
> On Thu, Jun 18, 2020 at 07:38:41PM +0530, Kalyan Thota wrote:
>> This change adds support to scale src clk and bandwidth as
>> per composition requirements.
>>
>> Interconnect registration for bw has been moved to mdp
>> device node from mdss to facilitate the scaling.
>>
>> Changes in v1:
>> - Address armv7 compilation issues with the patch (Rob)
>>
>> Signed-off-by: Kalyan Thota <kalyan_t@codeaurora.org>
>
> It seems this is an evolution of this series:
> https://patchwork.kernel.org/project/linux-arm-msm/list/?series=265351
>
> Are the DT bits of the series still valid? If so please include them in
> the
> series, otherwise please add DT patches to allow folks to test and
> review,
> and get them landed in Bjorn's tree after the driver changes have
> landed.
Hi,
Yes the patch is dependent on the DT changes, should i add them with
depends tag in the commit text ?
https://patchwork.kernel.org/patch/11470785/
https://patchwork.kernel.org/patch/11470789/
- Kalyan
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-07-15 7:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-18 14:08 [v1] drm/msm/dpu: add support for clk and bw scaling for display Kalyan Thota
2020-07-10 17:08 ` Rob Clark
2020-07-13 15:59 ` [Freedreno] " kalyan_t
2020-07-13 17:20 ` Rob Clark
2020-07-14 11:20 ` kalyan_t
2020-07-14 15:57 ` Rob Clark
2020-07-14 1:12 ` Matthias Kaehlcke
2020-07-14 11:09 ` kalyan_t [this message]
2020-07-14 16:23 ` Matthias Kaehlcke
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=38dc4bbfd754175e476252c4bc259d55@codeaurora.org \
--to=kalyan_t@codeaurora.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=freedreno@lists.freedesktop.org \
--cc=hoegsberg@chromium.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mka@chromium.org \
--cc=mkrishn@codeaurora.org \
--cc=seanpaul@chromium.org \
--cc=travitej@codeaurora.org \
/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).