From: Leonard Crestez <leonard.crestez@nxp.com>
To: Georgi Djakov <georgi.djakov@linaro.org>,
Rob Herring <robh+dt@kernel.org>
Cc: "Chanwoo Choi" <cw00.choi@samsung.com>,
"Artur Świgoń" <a.swigon@partner.samsung.com>,
"Alexandre Bailon" <abailon@baylibre.com>,
"Rafael J. Wysocki" <rafael@kernel.org>,
"Jacky Bai" <ping.bai@nxp.com>,
"Anson Huang" <anson.huang@nxp.com>,
"Abel Vesa" <abel.vesa@nxp.com>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"Saravana Kannan" <saravanak@google.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Shawn Guo" <shawnguo@kernel.org>,
"Aisheng Dong" <aisheng.dong@nxp.com>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"Matthias Kaehlcke" <mka@chromium.org>,
"Angus Ainslie" <angus@akkea.ca>,
"Martin Kepplinger" <martink@posteo.de>,
"Silvano Di Ninno" <silvano.dininno@nxp.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
dl-linux-imx <linux-imx@nxp.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH RFC v6 0/9] interconnect: Add imx support via devfreq
Date: Wed, 11 Dec 2019 09:53:38 +0000 [thread overview]
Message-ID: <VI1PR04MB702367B475FB20214F27F1F5EE5A0@VI1PR04MB7023.eurprd04.prod.outlook.com> (raw)
In-Reply-To: cover.1573761527.git.leonard.crestez@nxp.com
On 14.11.2019 22:10, Leonard Crestez wrote:
> This series adds interconnect scaling support for imx8m series chips. It uses a
> per-SOC interconnect provider layered on top of multiple instances of devfreq
> for scalable nodes along the interconnect.
>
> Existing qcom interconnect providers mostly translate bandwidth requests into
> firmware calls but equivalent firmware on imx8m is much thinner. Scaling
> support for individual nodes is implemented as distinct devfreq drivers
> instead.
>
> The imx interconnect provider doesn't communicate with devfreq directly
> but rather computes "minimum frequencies" for nodes along the path and
> creates dev_pm_qos requests.
>
> Since there is no single devicetree node that can represent the
> "interconnect" the main NOC is picked as the "interconnect provider" and
> will probe the interconnect platform device if #interconnect-cells is
> present. This avoids introducing "virtual" devices but it means that DT
> bindings of main NOC includes properties for both devfreq and
> interconnect.
>
> This depends on other series for devfreq pm/qos and ddrc:
It took a while but all runtime dependencies are included in
next-20191210 and the compile-time dependency on
DEV_PM_QOS_MIN_FREQUENCY is also included in v5.5-rc1. This series is a
bit old but still applies usefully so I thought I'd ask for additional
comments instead of a blank resend.
Georgi: can you please take a look at this series and suggest what would
make it suitable for inclusion?
Some dubious aspects:
* Existing drivers have multiple providers per SOC (for each internal
NOC?) but this is a single driver for the entire SOC topology. Not clear
what would be gain from this.
* NOC DT node implements devfreq (because it can be scaled) and
interconnect (to avoid virtual DT nodes). Maybe the devfreq NOC scaling
implementation could be moved into drivers/interconnect/imx?
It is quite different from qcom providers but hardware/firmware is also
very different.
> Changes since RFCv5:
> * Replace scanning for interconnect-node-id with explicit
> scalable-nodes/scalable-node-ids property on NoC.
> * Now passes make `dtbs_check`
> * Remove struct imx_icc_provider
> * Switch to of_icc_xlate_onecell
> * Use of_find_device_by_node to fetch QoS target, this causes fewer probe
> deferrals, removes dependency on devfreq API and even allows reloading ddrc
> module at runtime
> * Add imx_icc_node_destroy helper
> * Remove 0/1 on DEFINE_BUS_SLAVE/MASTER which created spurious links
> Link: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fcover%2F11222015%2F&data=02%7C01%7Cleonard.crestez%40nxp.com%7Cff0127cbde3e4e6f6c8508d7693eb8d5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637093590418229667&sdata=0EN1w8RtXHgyvXpRnOovEkWILoVlQ%2FEXJ0zdOOHI%2FgM%3D&reserved=0
>
> Changes since RFCv4:
> * Drop icc proxy nonsense
> * Make devfreq driver for NOC probe the ICC driver if
> #interconnect-cells is present
> * Move NOC support to interconnect series and rename the node in DT
> * Add support for all chips at once, differences are not intereseting
> and there is more community interest for 8mq than 8mm.
> Link: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fcover%2F11111865%2F&data=02%7C01%7Cleonard.crestez%40nxp.com%7Cff0127cbde3e4e6f6c8508d7693eb8d5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637093590418229667&sdata=bsJqXPVJSszKJf%2BXdqFT2E8wriuKQU00sWwkRqZYmn0%3D&reserved=0
>
> Changes since RFCv3:
> * Remove the virtual "icc" node and add devfreq nodes as proxy providers
> * Fix build on 32-bit arm (reported by kbuilt test robot)
> * Remove ARCH_MXC_ARM64 (never existed in upstream)
> * Remove _numlinks, calculate instead
> * Replace __BUSFREQ_H header guard
> * Improve commit message and comment spelling
> * Fix checkpatch issues
> Link to RFCv3: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fcover%2F11078671%2F&data=02%7C01%7Cleonard.crestez%40nxp.com%7Cff0127cbde3e4e6f6c8508d7693eb8d5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637093590418229667&sdata=c9xKEw9Fjlv%2FqDiWKr7zOUY5zZMWXjNyApBd94Nidnc%3D&reserved=0
>
> Changes since RFCv2 and initial work by Alexandre Bailon:
> * Relying on devfreq and dev_pm_qos instead of CLK
> * No more "platform opp" stuff
> * No more special suspend handling: use suspend-opp on devfreq instead
> * Replace all mentions of "busfreq" with "interconnect"
> Link to v2: https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpatchwork.kernel.org%2Fcover%2F11021563%2F&data=02%7C01%7Cleonard.crestez%40nxp.com%7Cff0127cbde3e4e6f6c8508d7693eb8d5%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C0%7C637093590418229667&sdata=1tEQS9BaHRTjdUYvZJ9%2FJG2BQQGl6hkbPWxiIZ811FY%3D&reserved=0
>
> Leonard Crestez (9):
> dt-bindings: interconnect: Add bindings for imx8m noc
> PM / devfreq: Add generic imx bus scaling driver
> PM / devfreq: imx: Register interconnect device
> interconnect: Add imx core driver
> interconnect: imx: Add platform driver for imx8mm
> interconnect: imx: Add platform driver for imx8mq
> interconnect: imx: Add platform driver for imx8mn
> arm64: dts: imx8m: Add NOC nodes
> arm64: dts: imx8m: Add interconnect provider properties
>
> .../bindings/interconnect/fsl,imx8m-noc.yaml | 104 ++++++
> arch/arm64/boot/dts/freescale/imx8mm.dtsi | 28 ++
> arch/arm64/boot/dts/freescale/imx8mn.dtsi | 28 ++
> arch/arm64/boot/dts/freescale/imx8mq.dtsi | 28 ++
> drivers/devfreq/Kconfig | 9 +
> drivers/devfreq/Makefile | 1 +
> drivers/devfreq/imx-devfreq.c | 187 +++++++++++
> drivers/interconnect/Kconfig | 1 +
> drivers/interconnect/Makefile | 1 +
> drivers/interconnect/imx/Kconfig | 17 +
> drivers/interconnect/imx/Makefile | 4 +
> drivers/interconnect/imx/imx.c | 301 ++++++++++++++++++
> drivers/interconnect/imx/imx.h | 60 ++++
> drivers/interconnect/imx/imx8mm.c | 105 ++++++
> drivers/interconnect/imx/imx8mn.c | 94 ++++++
> drivers/interconnect/imx/imx8mq.c | 103 ++++++
> include/dt-bindings/interconnect/imx8mm.h | 49 +++
> include/dt-bindings/interconnect/imx8mn.h | 41 +++
> include/dt-bindings/interconnect/imx8mq.h | 48 +++
> 19 files changed, 1209 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/interconnect/fsl,imx8m-noc.yaml
> create mode 100644 drivers/devfreq/imx-devfreq.c
> create mode 100644 drivers/interconnect/imx/Kconfig
> create mode 100644 drivers/interconnect/imx/Makefile
> create mode 100644 drivers/interconnect/imx/imx.c
> create mode 100644 drivers/interconnect/imx/imx.h
> create mode 100644 drivers/interconnect/imx/imx8mm.c
> create mode 100644 drivers/interconnect/imx/imx8mn.c
> create mode 100644 drivers/interconnect/imx/imx8mq.c
> create mode 100644 include/dt-bindings/interconnect/imx8mm.h
> create mode 100644 include/dt-bindings/interconnect/imx8mn.h
> create mode 100644 include/dt-bindings/interconnect/imx8mq.h
>
prev parent reply other threads:[~2019-12-11 9:53 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-14 20:09 [PATCH RFC v6 0/9] interconnect: Add imx support via devfreq Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 1/9] dt-bindings: interconnect: Add bindings for imx8m noc Leonard Crestez
2019-12-16 1:12 ` Chanwoo Choi
2019-12-16 3:25 ` Chanwoo Choi
2019-12-16 15:09 ` Leonard Crestez
2019-12-17 0:15 ` Chanwoo Choi
2019-12-19 14:31 ` Leonard Crestez
2019-12-19 15:55 ` Chanwoo Choi
2019-12-19 19:11 ` Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 2/9] PM / devfreq: Add generic imx bus scaling driver Leonard Crestez
2019-11-20 14:08 ` Angus Ainslie
2019-11-20 15:04 ` Leonard Crestez
2019-11-20 15:29 ` Marco Felsch
2019-11-20 15:41 ` Angus Ainslie
2019-11-20 16:30 ` Leonard Crestez
2019-11-20 16:38 ` Angus Ainslie
2019-11-20 18:02 ` Leonard Crestez
2020-02-04 9:45 ` Martin Kepplinger
2020-02-13 10:53 ` Martin Kepplinger
2019-12-13 1:30 ` Chanwoo Choi
2019-12-13 1:51 ` Chanwoo Choi
2019-12-16 1:06 ` Chanwoo Choi
2019-12-16 14:57 ` Leonard Crestez
2019-12-17 0:41 ` Chanwoo Choi
2019-12-17 21:05 ` Leonard Crestez
2019-12-18 3:15 ` Chanwoo Choi
2019-12-18 10:10 ` Leonard Crestez
2019-12-18 10:46 ` Chanwoo Choi
2019-12-18 17:06 ` Chanwoo Choi
2019-11-14 20:09 ` [PATCH RFC v6 3/9] PM / devfreq: imx: Register interconnect device Leonard Crestez
2019-12-13 4:28 ` Chanwoo Choi
2019-12-16 15:00 ` Leonard Crestez
2019-12-17 1:02 ` Chanwoo Choi
2019-12-18 10:13 ` Leonard Crestez
2019-12-18 11:05 ` Chanwoo Choi
2019-12-18 17:13 ` Leonard Crestez
2019-12-19 7:07 ` Chanwoo Choi
2019-11-14 20:09 ` [PATCH RFC v6 4/9] interconnect: Add imx core driver Leonard Crestez
2019-12-12 7:29 ` Georgi Djakov
2019-12-19 0:18 ` Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 5/9] interconnect: imx: Add platform driver for imx8mm Leonard Crestez
2019-12-12 7:35 ` Georgi Djakov
2019-12-16 14:35 ` Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 6/9] interconnect: imx: Add platform driver for imx8mq Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 7/9] interconnect: imx: Add platform driver for imx8mn Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 8/9] arm64: dts: imx8m: Add NOC nodes Leonard Crestez
2019-11-14 20:09 ` [PATCH RFC v6 9/9] arm64: dts: imx8m: Add interconnect provider properties Leonard Crestez
2019-12-11 9:53 ` Leonard Crestez [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=VI1PR04MB702367B475FB20214F27F1F5EE5A0@VI1PR04MB7023.eurprd04.prod.outlook.com \
--to=leonard.crestez@nxp.com \
--cc=a.swigon@partner.samsung.com \
--cc=abailon@baylibre.com \
--cc=abel.vesa@nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=angus@akkea.ca \
--cc=anson.huang@nxp.com \
--cc=cw00.choi@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=georgi.djakov@linaro.org \
--cc=kernel@pengutronix.de \
--cc=krzk@kernel.org \
--cc=kyungmin.park@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-pm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=martink@posteo.de \
--cc=mka@chromium.org \
--cc=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=ping.bai@nxp.com \
--cc=rafael@kernel.org \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=silvano.dininno@nxp.com \
--cc=viresh.kumar@linaro.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).