MIME-Version: 1.0
References: <20211120193916.1309236-1-aford173@gmail.com>
In-Reply-To: <20211120193916.1309236-1-aford173@gmail.com>
From:   Fabio Estevam <festevam@gmail.com>
Date:   Sat, 20 Nov 2021 17:52:37 -0300
Message-ID: <CAOMZO5CE890CygcP=VNgiqw9yDCZmJC9b-=OzBDRQSe1GHg8HQ@mail.gmail.com>
Subject: Re: [PATCH] soc: imx: gpcv2: keep i.MX8MM VPU-H1 bus clock active
To:     Adam Ford <aford173@gmail.com>
Cc:     "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" 
        <linux-arm-kernel@lists.infradead.org>,
        Tim Harvey <tharvey@gateworks.com>,
        Adam Ford-BE <aford@beaconembedded.com>,
        Shawn Guo <shawnguo@kernel.org>,
        Sascha Hauer <s.hauer@pengutronix.de>,
        Pengutronix Kernel Team <kernel@pengutronix.de>,
        NXP Linux Team <linux-imx@nxp.com>,
        Lucas Stach <l.stach@pengutronix.de>,
        Peng Fan <peng.fan@nxp.com>,
        linux-kernel <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

Hi Adam,

On Sat, Nov 20, 2021 at 4:39 PM Adam Ford <aford173@gmail.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@gmail.com>

This makes sense:

Reviewed-by: Fabio Estevam <festevam@gmail.com>