From: Alexandre Bailon <abailon@baylibre.com>
To: Aisheng Dong <aisheng.dong@nxp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"georgi.djakov@linaro.org" <georgi.djakov@linaro.org>
Cc: "mturquette@baylibre.com" <mturquette@baylibre.com>,
"ptitiano@baylibre.com" <ptitiano@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Zening Wang <zening.wang@nxp.com>,
"khilman@baylibre.com" <khilman@baylibre.com>,
"ccaione@baylibre.com" <ccaione@baylibre.com>,
Jacky Bai <ping.bai@nxp.com>,
Leonard Crestez <leonard.crestez@nxp.com>,
dl-linux-imx <linux-imx@nxp.com>,
Ranjani Vaidyanathan <ranjani.vaidyanathan@nxp.com>
Subject: Re: [RFC PATCH 0/3] Add support of busfreq
Date: Fri, 15 Mar 2019 10:31:40 +0100 [thread overview]
Message-ID: <56e96a3a-4901-c79c-e91d-6b6a0690e5b7@baylibre.com> (raw)
In-Reply-To: <AM0PR04MB421150DF12C869161E7ED4C180440@AM0PR04MB4211.eurprd04.prod.outlook.com>
Hi Aisheng
On 3/15/19 3:39 AM, Aisheng Dong wrote:
> +Jacky and Leonard, Ranjani
>
> Hi Alexandre,
>
>> From: Alexandre Bailon [mailto:abailon@baylibre.com]
>>
>> This series implements busfreq, a framework used in MXP's tree to scale the
>> interconnect and dram frequencies.
>> In the vendor tree, device's driver request for a performance level, which is
>> used to scale the frequencies.
>> This series implements it using the interconnect framework.
>> Devices' driver request for bandwidth which is use by busfreq to determine a
>> performance level, and then scale the frequency.
>>
>> Busfreq is quite generic. It could be used for any i.MX SoC.
>> A busfreq platform driver just have to define a list of interconnect nodes, and
>> some OPPs.
>>
>
> It's really great to see this patch series.
> And it should be the correct direction we're heading to upstream busfreq support.
>
>> This series is sent as RFC mostly because the current support of i.MX SoC won't
>> benefit of busfreq framework, because the clocks' driver don't support
>> interconnect / dram frequency scaling.
>> As exemple, this series implements busfreq for i.MX8MM whose upstreaming
>> is in progress. Because this relies on ATF to do the frequency scaling, it won't
>> be hard make it work.
>>
>
> How can I test this patch series?
> Any additional patches you can share with us?
> Or what else we need to do to test it? We can help with it.
Many other patches will be required to test the series.
There are a couple of patches that updates i.MX device drivers to
request for bandwidth (does similar thing as bus_freq_request and
bus_freq_release).
In addition, a patch to that allow to scale the DRAM
frequency using CCF is required. I'm still working on this patch. It
works correctly on 4.14, but since I rebased it on linux-next/master, it
stopped to work. I'm trying to fix it now.
I will share all this patches ASAP.
Best Regards,
Alexandre
>
> Regards
> Dong Aisheng
>
>> As exemple, this series implements busfreq for Alexandre Bailon (3):
>> drivers: interconnect: Add a driver for i.MX SoC
>> drivers: interconnect: imx: Add support of i.MX8MM
>> dt-bindings: interconnect: Document fsl,busfreq-imx8mm bindings
>>
>> .../bindings/interconnect/imx8mm.txt | 24 +
>> drivers/interconnect/Kconfig | 1 +
>> drivers/interconnect/Makefile | 1 +
>> drivers/interconnect/imx/Kconfig | 17 +
>> drivers/interconnect/imx/Makefile | 2 +
>> drivers/interconnect/imx/busfreq-imx8mm.c | 132 ++++
>> drivers/interconnect/imx/busfreq.c | 570
>> ++++++++++++++++++
>> drivers/interconnect/imx/busfreq.h | 123 ++++
>> include/dt-bindings/interconnect/imx8mm.h | 37 ++
>> 9 files changed, 907 insertions(+)
>> create mode 100644
>> Documentation/devicetree/bindings/interconnect/imx8mm.txt
>> create mode 100644 drivers/interconnect/imx/Kconfig create mode
>> 100644 drivers/interconnect/imx/Makefile create mode 100644
>> drivers/interconnect/imx/busfreq-imx8mm.c
>> create mode 100644 drivers/interconnect/imx/busfreq.c
>> create mode 100644 drivers/interconnect/imx/busfreq.h
>> create mode 100644 include/dt-bindings/interconnect/imx8mm.h
>>
>> --
>> 2.19.2
next prev parent reply other threads:[~2019-03-15 9:31 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-13 19:34 [RFC PATCH 0/3] Add support of busfreq Alexandre Bailon
2019-03-13 19:34 ` [RFC PATCH 1/3] drivers: interconnect: Add a driver for i.MX SoC Alexandre Bailon
2019-06-10 22:10 ` Leonard Crestez
2019-03-13 19:34 ` [RFC PATCH 2/3] drivers: interconnect: imx: Add support of i.MX8MM Alexandre Bailon
2019-03-13 19:34 ` [RFC PATCH 3/3] dt-bindings: interconnect: Document fsl,busfreq-imx8mm bindings Alexandre Bailon
2019-03-15 2:39 ` [RFC PATCH 0/3] Add support of busfreq Aisheng Dong
2019-03-15 9:31 ` Alexandre Bailon [this message]
2019-03-15 17:17 ` Leonard Crestez
2019-04-10 5:29 ` Viresh Kumar
2019-04-10 5:29 ` Viresh Kumar
2019-03-15 16:17 ` Michael Turquette
2019-03-15 16:55 ` Alexandre Bailon
2019-05-14 19:34 ` Leonard Crestez
2019-05-14 19:34 ` Leonard Crestez
2019-06-04 8:44 ` Anson Huang
2019-06-04 20:13 ` Leonard Crestez
2019-05-03 11:19 ` Krzysztof Kozlowski
2019-05-03 11:19 ` Krzysztof Kozlowski
2019-05-14 6:33 ` Georgi Djakov
2019-05-14 6:33 ` Georgi Djakov
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=56e96a3a-4901-c79c-e91d-6b6a0690e5b7@baylibre.com \
--to=abailon@baylibre.com \
--cc=aisheng.dong@nxp.com \
--cc=ccaione@baylibre.com \
--cc=georgi.djakov@linaro.org \
--cc=khilman@baylibre.com \
--cc=leonard.crestez@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=ping.bai@nxp.com \
--cc=ptitiano@baylibre.com \
--cc=ranjani.vaidyanathan@nxp.com \
--cc=zening.wang@nxp.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).