Received: by 2002:ac0:a5a7:0:0:0:0:0 with SMTP id m36-v6csp34758imm; Tue, 17 Jul 2018 13:25:17 -0700 (PDT) X-Google-Smtp-Source: AAOMgpceW0D/qIUYS8UmxRbpRi6AMdFAew+Gn0TbUNcCsnUDGxrS5oAKTxRLatsUZE1wk2FM9bJa X-Received: by 2002:a17:902:599b:: with SMTP id p27-v6mr2961544pli.191.1531859117179; Tue, 17 Jul 2018 13:25:17 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1531859117; cv=none; d=google.com; s=arc-20160816; b=FK2LAXKZpHTmzmnAAVAYnaRMFOSfOHK4wdsenKo3D1KfVJ6ulGAj4YKhLFYK9/oXQU hWDB9xh74/l9iQL+DU7AGGajGEErSfubQU434htmEj4bNPGRGWliHxXdibx4GIBJn7/J sk4Yg08WW+7DcvNa1sPP6amWwN1XqTGL2rsloLNiJp/x16J7u9CTZp0x0m23Hhsun9aA MCTq0bq2G7PtW7mlFuvSFbdZ4x76sIhkYlc2za5af97njl7lAcL+o62gXidTHftP3uQI a8VKd+2D3BLfgSwf76stoatT0y0kZs2MU5ezHzhevRR81vae6z/qzpjgJdVJphcpVTwn wdcA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :references:in-reply-to:mime-version:dkim-signature :arc-authentication-results; bh=remtMM1dLeUZagBlL/2ql9wierFKRupmAW/ztpEL5wo=; b=mTyb7KtKQjpcV4HkOyD1RGSSHep9falP9KV4VjFR9hMYgznLIgYvV/kxnPdF2BbQAl Reihao44sx3g/8Mib+5NUq3zksjSHhAEtgdn9REzZpi6YxcJvvt+RpKgdRxg4pMBEO0o qEcP0Af63e7lUdHAeZ+1fXbrVl6FWAhW/NMFGkT2b60uSlzvRninu9JQqgWaW0JbRlqd mw/4rr6UXxWx3S7oU1Tpqt95uwsFDsKKpL6UyVZKyTSv/bnkW984xR3fEM2vOVAA+NlV kMLB5QFFzhCyNb0Hgp4yUVeP2xjKgRcmZAoIIEvHCuGN1KRQF75aC+yhPGnc7eos93it 99Ug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sHh9JM+C; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l7-v6si1686667pgc.650.2018.07.17.13.25.02; Tue, 17 Jul 2018 13:25:17 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=sHh9JM+C; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730480AbeGQU6j (ORCPT + 99 others); Tue, 17 Jul 2018 16:58:39 -0400 Received: from mail-oi0-f68.google.com ([209.85.218.68]:45932 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729741AbeGQU6i (ORCPT ); Tue, 17 Jul 2018 16:58:38 -0400 Received: by mail-oi0-f68.google.com with SMTP id q11-v6so4467835oic.12; Tue, 17 Jul 2018 13:24:20 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=remtMM1dLeUZagBlL/2ql9wierFKRupmAW/ztpEL5wo=; b=sHh9JM+C+FNAhYqDjxabChBh+zTaViIkcCRUaEUQJ7+JpJRygXkZ2BMXgFwZS+nIQl 7gog1Gm0fdIxPTrxQ+ksE2955g9uv06z899i7EsstqyWlBgXALuVhfnDkFmfDE3/E360 ByMyceHtcErniudtN5uWN5/R2h4bxZ/xBDhfrWSSByaEfoSuTjUyp1lEOd7hY/GSdNLJ hJ46fNyhjnU0t5iRBgGNwd259dsLzjKZKFqmRVvRu/qdS/T0Rg3nVp5nUNyj/Vtt1M0g AQcnCzAIueYWbCjKlXdehV2oFexyxXTA/5iJIB0bigKasDhPCs4wWXo8GLIIVEBppTbw bPDg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=remtMM1dLeUZagBlL/2ql9wierFKRupmAW/ztpEL5wo=; b=j9qYeXBMYIDNKaZfhSl4KrxS+e67TDooAMdSBaYTgUjRwRKkEoBNLIGW4ILFxdwQbe eFJfs3aO2TSpOGnSmHaZ3MQmBOclxVo/fNrJRXCQ7pJsRlTwsetBhelX+x90E7emLrjw Yfwb/OYu8UPNyzXXth1h2NdLimIRyft1nxdsLgNovihbDvHs/L7jDNxn366/hsSqsSrE 8/DOKVFo95yCenoR31jSmsbdEFMBcU6Hk76mB0aeF1sXHwMikPlSBqCTJQ9lo9ePFjJf YynqsIZYzhOkPIJtwbqjoaZRruRd4UsW9Caqj/5hxCU8qag5Uzte/5BLdil1AW0Ew1uf cAgw== X-Gm-Message-State: AOUpUlEobslobGqZitxt/dNhz0719aiNdYwmMM6/0ZZ1GtelmQsL/KSo LhQE5Ylpc92Z0zZRVMo4UKHUtysz8IvG/GbLLv4= X-Received: by 2002:aca:b48b:: with SMTP id d133-v6mr3034667oif.165.1531859060283; Tue, 17 Jul 2018 13:24:20 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a9d:5b33:0:0:0:0:0 with HTTP; Tue, 17 Jul 2018 13:23:59 -0700 (PDT) In-Reply-To: References: <1531822342-4293-1-git-send-email-linux.amoon@gmail.com> From: Anand Moon Date: Wed, 18 Jul 2018 01:53:59 +0530 Message-ID: Subject: Re: [PATCH 1/5] thermal: exynos: enable core tmu clk on exynos platform To: Krzysztof Kozlowski Cc: Bartlomiej Zolnierkiewicz , Zhang Rui , Eduardo Valentin , Kukjin Kim , Rob Herring , Mark Rutland , Linux PM list , "linux-samsung-soc@vger.kernel.org" , linux-arm-kernel , Linux Kernel , devicetree Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Krzysztof On 17 July 2018 at 17:50, Krzysztof Kozlowski wrote: > Hi Anand, > > Thanks for patch. > > On 17 July 2018 at 12:12, Anand Moon wrote: >> clk_summary do not show tmu_apbif clk enable, so replace >> the clk_prepare with clk_prepare_enables to enable tmu clk. > > This is not valid reason to do a change. What is clk_summary does not > really matter. Your change has negative impact on power consumption as > the clock stays enabled all the time. This is not what we want... so > please explain it more - why you need the clock to be enabled all the > time? What is broken (clk_summary is not broken in this case)? > Opps I could not explain some more in my commit message. Actually TMU sensor for Exynos process are controlled by so external clk Exynos4412 have VDD18_TS sensor which controls the CLK_SENSE tmu. Exynos5422 have VDD18_TS01 / VDD18_TS23 / VDD18_TS4 sensor which control the CLK_SENSE tmu. So as per my understanding tmu is clk driver which control the flow PMIC. clk_prepare_enable combine clk_prepare and clk_enable and clk_disable_unprepare combine clk_disable and clk_unprepare. most of the driver prefer clk_prepare_enable and clk_disable_unprepare. clk_summary is just a reference looking point where we could check the clk is enable/disable. what is broken ? I still few more parameter need to tuned to configure the tmu driver. >> simplify the enable of tmu_triminfo_apbif clk, also fixed >> the order of goto error for failed cases. > > This has to be split into separate change. > > Best regards, > Krzysztof Best Regards -Anand