Received: by 2002:a05:6a10:6744:0:0:0:0 with SMTP id w4csp651880pxu; Fri, 23 Oct 2020 09:52:29 -0700 (PDT) X-Google-Smtp-Source: ABdhPJwdRdp/WRNxe6BAtCA4tg4dLAKB2IjkMulmQj42MdEUKeFg9Wgfg6wSIFvWOq78aZmvPX5o X-Received: by 2002:a17:906:d292:: with SMTP id ay18mr2986888ejb.244.1603471949338; Fri, 23 Oct 2020 09:52:29 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1603471949; cv=none; d=google.com; s=arc-20160816; b=XcYpj2VC8ETw+TLoOEOAXx/PSDuYSCndkRqM7x0qkfl8BCDXZfa7Znp8e0lH5jIZey 3VvRvqaCMQTIqMLmYzkTYSGzXI/4GGQ/ZsuW7qsXXUHD7jQ11n84DY2DFt+xPQoUb0An +ZoiUi0yHuP2BwX2irY+r79bliwhH+Lhj59GhrMqkhllppOM5kgtkDB8IMqPMbixWd9K OhNSY2gKxrrvaSvol13ah6lsoV6P8o5OkXVIaV8dmxPk9BchFIbcy5kLbPoSnkAxuETK Wr+P0CzitVCrTcKdNuA35wdrrB/IaYUpabQeDLUmSnI8U2upEiekNKBd28Yy5ubUwKgg DaXg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:user-agent:in-reply-to:content-disposition :mime-version:references:message-id:subject:cc:to:from:date :dkim-signature; bh=ucv5oR6DPdGRMnKY0683TdGM4cbhJcd2cZfvbWq/+PU=; b=pRSW7/v0EHPlsSAhbEmMkCIhLhj3klYbyKG+fU1LnN1re7D7N0M0Bu8jeLffSG8XJ3 9JgVTaLMTw+rJ+JJWqPwJtZLlEnFoKK2qLkqMOC4X0BBtb+MeWKPqqt78m8bYQtZMAvd WnfmNOnjzZUCWxPQprfWUaIhYnLzqELQsZ+B3LIMclnKu8CzuxIOR9wy+mmdY2hoPVQV NNjbWXt5v2s8od0HJPRPIyrt5Gz6i1h9QljMHrWsIH/Fn/rJ0S5fqCTP/HoYGpubbon3 txCfahN8XgcOuW2Ol6OEA9gEuD2ApsgAMTJoTJcDRCxSetE9kDyEQ4uyx9kNED22lbxW NMxg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=f07s3VLB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w23si1161960edu.226.2020.10.23.09.52.07; Fri, 23 Oct 2020 09:52:29 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@linaro.org header.s=google header.b=f07s3VLB; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linaro.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S461454AbgJWJ1Y (ORCPT + 99 others); Fri, 23 Oct 2020 05:27:24 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39072 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S461439AbgJWJ1X (ORCPT ); Fri, 23 Oct 2020 05:27:23 -0400 Received: from mail-pf1-x441.google.com (mail-pf1-x441.google.com [IPv6:2607:f8b0:4864:20::441]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6F9A4C0613D4 for ; Fri, 23 Oct 2020 02:27:23 -0700 (PDT) Received: by mail-pf1-x441.google.com with SMTP id b26so721993pff.3 for ; Fri, 23 Oct 2020 02:27:23 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ucv5oR6DPdGRMnKY0683TdGM4cbhJcd2cZfvbWq/+PU=; b=f07s3VLB2MfVm1O3IHZ0eF7bXrbz5q+OMq7d217XRq9up5bkItIWfl7qKlNY+ATmJV 4DovSd07C399R6SJrO1As9FKrmDERtWx5kJxc8DRoMJ+mxRaMkW0AoM45IF+41hG3rZP dKa0tPDvPO/MDNOsapAIMlYh40B5L1H/RKp5Om7zDiBn5DSZptfMyMgU+QpFQlJQWdcI Ed+VZC14LdegGJtYX7zFcRF7qKq62X4xqR4cjPePX5kPPD2cbCZWFP3wspS1A/+71EnK HG8VbMzQxU33SMfkk4pL55/YNMbLTdglZWjpTUOU1ZN/ohpfdr4UeO2OzSJKxvXWhepm Dm5w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ucv5oR6DPdGRMnKY0683TdGM4cbhJcd2cZfvbWq/+PU=; b=iO0ABy7SFBTDCV0QgNEcjwKW3lhfpgirpxADBDrpY6BZNOGZ3mLNPcz58vNDr3CGpq OXSf2pX7xQI8/vnZcEhqTNOywRSQKBDkuaVctusqEhQ5+opirlfAL0KejT4I8jfvVWBK +tkZtRnX05m182fWEf4h64Aa6og2XiCj8v3KS8Sezn2xfiQ8N+MjINoQ776XXosL94VQ LxCYODcmsQSmtSmy1FDlTUPb+uTFe3vn3fXtAiEhCJA1/CWtSnSyuSb/NMz3AeGyWLZy C9YU5pwFBIK9gKHlyjyoM9OWsS2c/8AVCXGGt1RdXUjilO3HAyN8yXmiiYrglFYIuoDM dHWw== X-Gm-Message-State: AOAM532rbc2xxnB+gs1XPKQAoy9YaAkaKrG9/QL1nixkPtWhuOUgl5Pa f3aXJn61HZYtoVUc+AmhMqy23g== X-Received: by 2002:a17:90a:f187:: with SMTP id bv7mr1555398pjb.198.1603445242886; Fri, 23 Oct 2020 02:27:22 -0700 (PDT) Received: from localhost ([122.181.54.133]) by smtp.gmail.com with ESMTPSA id gx20sm1545390pjb.1.2020.10.23.02.27.21 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Fri, 23 Oct 2020 02:27:22 -0700 (PDT) Date: Fri, 23 Oct 2020 14:57:20 +0530 From: Viresh Kumar To: Hector Yuan Cc: linux-mediatek@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-pm@vger.kernel.org, Rob Herring , "Rafael J. Wysocki" , Maxime Ripard , Santosh Shilimkar , Amit Kucheria , Stephen Boyd , Ulf Hansson , Dave Gerlach , Florian Fainelli , Robin Murphy , Lorenzo Pieralisi , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, wsd_upstream@mediatek.com Subject: Re: [PATCH v1] cpufreq: mediatek-hw: Add support for Mediatek cpufreq HW driver Message-ID: <20201023092720.qpws5wivqb4u6fwl@vireshk-i7> References: <1603441493-18554-1-git-send-email-hector.yuan@mediatek.com> <20201023082817.5vp4cvi2lmpaozcn@vireshk-i7> <1603444138.20224.19.camel@mtkswgap22> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1603444138.20224.19.camel@mtkswgap22> User-Agent: NeoMutt/20180716-391-311a52 Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 23-10-20, 17:08, Hector Yuan wrote: > On Fri, 2020-10-23 at 13:58 +0530, Viresh Kumar wrote: > > On 23-10-20, 16:24, Hector Yuan wrote: > > > This patchset includes 6 patches and depends on the MT6779 DTS patch[1] submitted by Hanks Chen. > > > The first 3 patches are for CPUFREQ HW driver and device tree binding, which are already sent before separately [2][3]. For binding part, I add a new patch to add property in cpu schema. > > > Besides, we add three more patches including EM power table, SVS CPU initialize, and cooling device. > > > > And even after so many versions of these you chose to name this V1. It > > is very difficult for reviewers to find time to review your stuff, and > > they expect some sort of summary from you on what exactly changed from > > last version and you also need to name the current version currently. > > > > This should have been V8 and you should have added a "V7->V8 diff:" > > section here, naming all the changes you did. Please send that as > > reply to this email, so I can see what really changed. > > > Hi, Viresh > > Sorry for your inconvenience. > #1~#3 is for cpufreq driver we have reviewed and the bindings which > separate freq domain to CPU schema.There is no change for the driver > itself. > 1. cpufreq: mediatek-hw: Add support for CPUFREQ HW > 2. dt-bindings: arm: cpus: Document 'mtk,freq-domain' property > 3. dt-bindings: cpufreq: add bindings for MediaTek cpufreq HW > > #4~#6 is for other CPU features, i.e. SVS [1] > 4. cpufreq: mediatek-hw: register EM power table > 5. cpufreq: mediatek-hw: Add SVS CPU initialization > 6. cpufreq: mediatek-hw: Add cooling dev flag > > I supposed that it could be more clean to separate #4~#6 in another > patchset.May I know is it okay to you? Or I should merge all of changes > into v8 like you mentioned? Thank you. Merge them all together and explain any special features (like SVS) in the commit log. It will also help in future when people want to understand your driver. Explain whatever is worth explaining there and is not straight forward. Thanks for the details. -- viresh