From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Estevam Subject: Re: [PATCH V2 4/4] thermal: qoriq: Add clock operations Date: Tue, 30 Jul 2019 00:56:33 -0300 Message-ID: References: <20190729083915.4855-1-Anson.Huang@nxp.com> <20190729083915.4855-4-Anson.Huang@nxp.com> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Anson Huang Cc: "rui.zhang" , Eduardo Valentin , Daniel Lezcano , Rob Herring , Mark Rutland , "linux-pm@vger.kernel.org" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , linux-kernel , dl-linux-imx List-Id: devicetree@vger.kernel.org Hi Anson, On Tue, Jul 30, 2019 at 12:00 AM Anson Huang wrote: > Shawn already applied the patch, and Abel has the AHB clock patch to fix that, > so just wait for the AHB clock patch in instead of revert the TMU clock patch? Sorry, I don't understand Abel's patch as there is not a proper description of what it tries to fix. If I understand correctly Abel's patch is not the proper fix and the real fix for the kernel TMU hang in linux-next is to manage the TMU clock inside the TMU driver, like you did in this patch. To avoid a revert one possible solution would be to send only this one as a fix for 5.3. You can point that it Fixes the commit that adds i.MX8M support for the TMU driver.