From: Martin Kepplinger <martink@posteo.de>
To: Leonard Crestez <leonard.crestez@nxp.com>
Cc: "Georgi Djakov" <georgi.djakov@linaro.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Artur Świgoń" <a.swigon@partner.samsung.com>,
"Alexandre Bailon" <abailon@baylibre.com>,
"Viresh Kumar" <viresh.kumar@linaro.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Aisheng Dong" <aisheng.dong@nxp.com>,
"Jacky Bai" <ping.bai@nxp.com>,
"Saravana Kannan" <saravanak@google.com>,
"Anson Huang" <anson.huang@nxp.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Michael Turquette" <mturquette@baylibre.com>,
"linux-pm@vger.kernel.org" <linux-pm@vger.kernel.org>,
"Krzysztof Kozlowski" <krzk@kernel.org>,
"Chanwoo Choi" <cw00.choi@samsung.com>,
"Kyungmin Park" <kyungmin.park@samsung.com>,
"MyungJoo Ham" <myungjoo.ham@samsung.com>,
dl-linux-imx <linux-imx@nxp.com>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFCv3 3/3] interconnect: imx: Add platform driver for imx8mm
Date: Wed, 21 Aug 2019 16:26:38 +0200 [thread overview]
Message-ID: <be41481b-5184-7878-b25e-41b7a1e1b2d5@posteo.de> (raw)
In-Reply-To: <VI1PR04MB7023E441FEE0D9288CAC0F44EEAA0@VI1PR04MB7023.eurprd04.prod.outlook.com>
On 21.08.19 16:21, Leonard Crestez wrote:
> On 21.08.2019 17:03, Martin Kepplinger wrote:
>> On 06.08.19 12:55, Leonard Crestez wrote:
>>> This adds a platform driver for the i.MX8MM SoC.
>>>
>>> Signed-off-by: Leonard Crestez <leonard.crestez@nxp.com>
>>> Signed-off-by: Alexandre Bailon <abailon@baylibre.com>
>>> ---
>>> drivers/interconnect/imx/Kconfig | 4 +
>>> drivers/interconnect/imx/Makefile | 1 +
>>> drivers/interconnect/imx/imx8mm.c | 114 ++++++++++++++++++++++
>>> include/dt-bindings/interconnect/imx8mm.h | 49 ++++++++++
>>> 4 files changed, 168 insertions(+)
>>> create mode 100644 drivers/interconnect/imx/imx8mm.c
>>> create mode 100644 include/dt-bindings/interconnect/imx8mm.h
>>
>> Do you plan to add such a driver for imx8mq too?
>
> Yes! The topology is different (serving different IP blocks) but no
> functional code changes are required between 8mm 8mn 8mq.
>
> I already wrote the code and tested it but didn't post because I want to
> get the core parts in first. I periodically push my "full"
> work-in-progress to github:
>
> https://github.com/cdleonard/linux/commits/next_imx8mm_busfreq
>
> You need out-of-tree ATF changes or devfreq probe will fail:
>
> https://github.com/cdleonard/arm-trusted-firmware/commits/imx_2.0.y_busfreq
>
Thanks for the update, that's good to hear. I'll get back to you when I
come around to test this and wish you good progress until then :)
martin
next prev parent reply other threads:[~2019-08-21 14:26 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-06 10:55 [RFCv3 0/3] interconnect: Add imx support via devfreq Leonard Crestez
2019-08-06 10:55 ` [RFCv3 1/3] dt-bindings: interconnect: Add bindings for imx Leonard Crestez
2019-08-07 15:16 ` Georgi Djakov
2019-08-07 22:35 ` Leonard Crestez
2019-08-06 10:55 ` [RFCv3 2/3] interconnect: Add imx core driver Leonard Crestez
2019-08-07 15:16 ` Georgi Djakov
2019-08-06 10:55 ` [RFCv3 3/3] interconnect: imx: Add platform driver for imx8mm Leonard Crestez
2019-08-21 14:02 ` Martin Kepplinger
2019-08-21 14:21 ` Leonard Crestez
2019-08-21 14:26 ` Martin Kepplinger [this message]
2019-10-10 14:43 ` Angus Ainslie
2019-10-15 14:05 ` Leonard Crestez
2019-10-16 14:09 ` Angus Ainslie
2019-10-16 14:54 ` Leonard Crestez
2019-10-17 13:25 ` Angus Ainslie
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=be41481b-5184-7878-b25e-41b7a1e1b2d5@posteo.de \
--to=martink@posteo.de \
--cc=a.swigon@partner.samsung.com \
--cc=abailon@baylibre.com \
--cc=aisheng.dong@nxp.com \
--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=leonard.crestez@nxp.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=mturquette@baylibre.com \
--cc=myungjoo.ham@samsung.com \
--cc=ping.bai@nxp.com \
--cc=robh+dt@kernel.org \
--cc=saravanak@google.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--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).