[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAOMZO5CE890CygcP=VNgiqw9yDCZmJC9b-=OzBDRQSe1GHg8HQ@mail.gmail.com>
Date: Sat, 20 Nov 2021 17:52:37 -0300
From: Fabio Estevam <festevam@...il.com>
To: Adam Ford <aford173@...il.com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@...ts.infradead.org>,
Tim Harvey <tharvey@...eworks.com>,
Adam Ford-BE <aford@...conembedded.com>,
Shawn Guo <shawnguo@...nel.org>,
Sascha Hauer <s.hauer@...gutronix.de>,
Pengutronix Kernel Team <kernel@...gutronix.de>,
NXP Linux Team <linux-imx@....com>,
Lucas Stach <l.stach@...gutronix.de>,
Peng Fan <peng.fan@....com>,
linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] soc: imx: gpcv2: keep i.MX8MM VPU-H1 bus clock active
Hi Adam,
On Sat, Nov 20, 2021 at 4:39 PM Adam Ford <aford173@...il.com> wrote:
>
> Enable the vpu-h1 clock when the domain is active because reading
> or writing to the VPU-H1 IP block cause the system to hang.
>
> Fixes: 656ade7aa42a ("soc: imx: gpcv2: keep i.MX8M* bus clocks enabled")
> Signed-off-by: Adam Ford <aford173@...il.com>
This makes sense:
Reviewed-by: Fabio Estevam <festevam@...il.com>
Powered by blists - more mailing lists