From: Taniya Das <tdas@codeaurora.org>
To: Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>
Cc: Andy Gross <andy.gross@linaro.org>,
David Brown <david.brown@linaro.org>,
Rajendra Nayak <rnayak@codeaurora.org>,
Amit Nischal <anischal@codeaurora.org>,
linux-arm-msm@vger.kernel.org, linux-soc@vger.kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add display clock controller driver for SDM845
Date: Sat, 23 Jun 2018 19:54:03 +0530 [thread overview]
Message-ID: <88b6cfa5-27fd-7fd0-e306-ae9580a39775@codeaurora.org> (raw)
In-Reply-To: <152942182329.16708.17615552184746348831@swboyd.mtv.corp.google.com>
Hello Stephen,
Thanks for the comments.
On 6/19/2018 8:53 PM, Stephen Boyd wrote:
> Quoting Taniya Das (2018-06-13 03:33:15)
>> [v2]
>> * Removed unused header file includes.
>> * Moved the frequency table macro to a common file [1].
>> * Move to pll config to probe.
>> * Update SoC name in device tree binding and
>> also update the Kconfig.
>>
>> Add support for the display clock controller found on SDM845
>> based devices. This would allow display drivers to probe and
>> control their clocks.
>>
>> The Display clock driver depends on the frequency table macro
>> movement to a common file [1].
>
> Please send that patch along with these patches so the dependency is
> clear.
>
Please check the latest patch series :
https://lkml.org/lkml/2018/6/23/109
>>
>> [1]: https://lkml.org/lkml/2018/6/13/216
>>
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation.
--
prev parent reply other threads:[~2018-06-23 14:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 10:33 [PATCH v2 0/2] Add display clock controller driver for SDM845 Taniya Das
2018-06-13 10:33 ` [PATCH v2 1/2] dt-bindings: clock: Introduce QCOM Display clock bindings Taniya Das
2018-06-13 10:33 ` [PATCH v2 2/2] clk: qcom: Add display clock controller driver for SDM845 Taniya Das
2018-06-13 12:56 ` kbuild test robot
2018-06-13 12:58 ` kbuild test robot
2018-06-19 15:23 ` [PATCH v2 0/2] " Stephen Boyd
2018-06-23 14:24 ` Taniya Das [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=88b6cfa5-27fd-7fd0-e306-ae9580a39775@codeaurora.org \
--to=tdas@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=anischal@codeaurora.org \
--cc=david.brown@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-soc@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=rnayak@codeaurora.org \
--cc=sboyd@kernel.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