From: Marek Vasut <marex@denx.de>
To: Abel Vesa <abel.vesa@nxp.com>, Adam Ford <aford173@gmail.com>
Cc: linux-clk <linux-clk@vger.kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
NXP Linux Team <linux-imx@nxp.com>,
Rob Herring <robh+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
arm-soc <linux-arm-kernel@lists.infradead.org>,
devicetree <devicetree@vger.kernel.org>
Subject: Re: [RFC 0/3] clk: imx: Implement blk-ctl driver for i.MX8MN
Date: Sun, 25 Oct 2020 13:18:48 +0100 [thread overview]
Message-ID: <3dadade8-6e77-e27f-d5a6-307de17a4dd0@denx.de> (raw)
In-Reply-To: <20201025120509.r5kl76wo5mdmapo5@fsr-ub1664-175>
On 10/25/20 1:05 PM, Abel Vesa wrote:
[...]
>> Together, both the GPC and the clk-blk driver should be able to pull
>> the multimedia block out of reset. Currently, the GPC can handle the
>> USB OTG and the GPU, but the LCDIF and MIPI DSI appear to be gated by
>> the clock block
>>
>> My original patch RFC didn't include the imx8mn node, because it
>> hangs, but the node I added looks like:
>>
>> media_blk_ctl: clock-controller@32e28000 {
>> compatible = "fsl,imx8mn-media-blk-ctl", "syscon";
>> reg = <0x32e28000 0x1000>;
>> #clock-cells = <1>;
>> #reset-cells = <1>;
>> };
>>
>> I was hoping you might have some feedback on the 8mn clk-blk driver
>> since you did the 8mp clk-blk drive and they appear to be very
>> similar.
>>
>
> I'll do you one better still. I'll apply the patch in my tree and give it
> a test tomorrow morning.
You can also apply the one for 8MM:
https://lore.kernel.org/linux-arm-kernel/20201003224555.163780-5-marex@denx.de/
next prev parent reply other threads:[~2020-10-25 12:19 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-24 16:20 [RFC 0/3] clk: imx: Implement blk-ctl driver for i.MX8MN Adam Ford
2020-10-24 16:20 ` [RFC 1/3] dt-bindings: clock: imx8mn: Add media blk_ctl clock IDs Adam Ford
2020-10-30 18:30 ` Rob Herring
2020-10-24 16:20 ` [RFC 2/3] dt-bindings: reset: imx8mn: Add media blk_ctl reset IDs Adam Ford
2020-10-30 18:30 ` Rob Herring
2020-10-24 16:20 ` [RFC 3/3] clk: imx: Add blk-ctl driver for i.MX8MN Adam Ford
2021-01-27 14:56 ` Marek Vasut
2020-10-24 20:23 ` [RFC 0/3] clk: imx: Implement " Abel Vesa
2020-10-24 21:03 ` Adam Ford
2020-10-25 12:05 ` Abel Vesa
2020-10-25 12:18 ` Marek Vasut [this message]
2020-10-25 16:05 ` Adam Ford
2020-10-26 14:55 ` Abel Vesa
2020-10-26 15:12 ` Adam Ford
2020-10-26 15:44 ` Lucas Stach
2020-10-26 16:23 ` Adam Ford
2020-10-29 11:54 ` Lucas Stach
2020-10-29 12:18 ` Abel Vesa
2020-10-29 12:18 ` Adam Ford
2020-10-29 13:03 ` Lucas Stach
2020-10-27 9:38 ` Abel Vesa
2020-10-26 15:37 ` Lucas Stach
2020-10-27 9:31 ` Abel Vesa
2020-10-27 11:55 ` Abel Vesa
2020-10-28 1:28 ` Jacky Bai
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=3dadade8-6e77-e27f-d5a6-307de17a4dd0@denx.de \
--to=marex@denx.de \
--cc=abel.vesa@nxp.com \
--cc=aford173@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@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;
as well as URLs for NNTP newsgroup(s).