From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6F82C76186 for ; Sat, 27 Jul 2019 20:17:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 71D0E208E4 for ; Sat, 27 Jul 2019 20:17:52 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="ru73Yj2p" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388324AbfG0URv (ORCPT ); Sat, 27 Jul 2019 16:17:51 -0400 Received: from mail-lf1-f67.google.com ([209.85.167.67]:44341 "EHLO mail-lf1-f67.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2387841AbfG0URv (ORCPT ); Sat, 27 Jul 2019 16:17:51 -0400 Received: by mail-lf1-f67.google.com with SMTP id r15so22373187lfm.11; Sat, 27 Jul 2019 13:17:49 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=TNmkt6r1wwZluVwfnTTUGV7AKJv+CJ4rclhv3bynhgE=; b=ru73Yj2pRqQDLD6iKXAYSgjhlhEIgBZZQT02f+jLPD8yVaXpKCY7K7LNKQSrKiJ2OL aAukl8H4Z7Jz0FXAa5MjGOVQsxNtA5b8RLTFH1vO/bVKf3EDt1e1XwTaNXhUU+dtrd5+ bMSbDJxIGosG9XvFJBPNJ5he9UGUME7Gglvl+Ow19zvHJ/Ov8tQ7sC08p1u69oc0a6mX kvE5Ktgn3O/zZpohQMzl/iuAiWrn5yjuqFPsgpQszQSv5p2/YjS5Gp8P1BJzb9zwjYsW aiLED55ID7afVvRriFX0FFfuucsVOdye1JARsOta/7Wuu7vr3+wnVc+wX/oAk2MZVk9n jRbg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=TNmkt6r1wwZluVwfnTTUGV7AKJv+CJ4rclhv3bynhgE=; b=XRg0IBOC66LaP1rPUcVGLFcpVc4cdzH8d0KLJXE1bz2ql62/Cjthv0m3rLG67m1YTe bbM8z7eUPUfEGOlJCfvvdgR87JxmgcKmNttUjRdMgN9bwZxRjKuK5gNYVMQ+iWTwobvp GVyMsc5jH/92clhxVLUHT/zQYEDN+19xp7sl5VHH/cNhNpN2Y7j2+xKf6BZDnfb50GNP Nemn7BVAzl9kI751KIb3aScDI56rli88vGlPSgDTkFNxNjovBJUrhxX6DWCWXXaW+a92 LNLeREJVkuYPDqwyBIbUHeKi7o4O53b3ICqprUjoC7B8ZS3El/66OmdwZU59WCwuxA9s R+IQ== X-Gm-Message-State: APjAAAUr1rppyjdslnfM6uOAYbT5nWUA+/NC0VLA+oWsxXWb46Uw7UY+ ukQR4MIXEGGhH4vC3ub0fjDxvYJU8RmLDBFxndI= X-Google-Smtp-Source: APXvYqxpSbR1Bjz4XI/bIwcJDaFltZanQO8EpuyDV/1mHmh80RcaDU5FYXYbDZXzcAhwMCy9dV3VjhYwFCUXJT14/aM= X-Received: by 2002:a05:6512:29a:: with SMTP id j26mr16237912lfp.44.1564258668333; Sat, 27 Jul 2019 13:17:48 -0700 (PDT) MIME-Version: 1.0 References: <20190705045612.27665-1-Anson.Huang@nxp.com> <20190705045612.27665-5-Anson.Huang@nxp.com> <20190727182636.GA7170@bogon.m.sigxcpu.org> In-Reply-To: <20190727182636.GA7170@bogon.m.sigxcpu.org> From: Fabio Estevam Date: Sat, 27 Jul 2019 17:17:50 -0300 Message-ID: Subject: Re: [PATCH 5/6] clk: imx8mq: Remove CLK_IS_CRITICAL flag for IMX8MQ_CLK_TMU_ROOT To: =?UTF-8?Q?Guido_G=C3=BCnther?= Cc: Daniel Baluta , Anson Huang , Mark Rutland , Carlo Caione , "Angus Ainslie (Purism)" , Leonard Crestez , linux-clk , Abel Vesa , Andrey Smirnov , Daniel Lezcano , dl-linux-imx , "rui.zhang" , Michael Turquette , Devicetree List , linux-pm@vger.kernel.org, Sascha Hauer , Eduardo Valentin , Rob Herring , linux-arm-kernel , Stephen Boyd , Linux Kernel Mailing List , Pengutronix Kernel Team , Shawn Guo , Lucas Stach Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Guido, On Sat, Jul 27, 2019 at 3:26 PM Guido G=C3=BCnther wrote: > I noticed a boot hang yesterday on next-20190726 when loading the > qoriq_thermal which I worked around by blacklisting it. The > fsl,imx8mq-tmu node specifies a clock (IMX8MQ_CLK_TMU_ROOT) but does not > seem to enable, shouldn't it do so? Yes, I think you are right. I don't have access to a imx8mq board at the moment, but something like below would probably help: http://code.bulix.org/pd88jp-812381 If it helps, I can send it as a formal patch. Regards, Fabio Estevam