Received: by 10.192.165.148 with SMTP id m20csp5406794imm; Wed, 9 May 2018 04:41:32 -0700 (PDT) X-Google-Smtp-Source: AB8JxZp1psCCmQ1MOOuZXigXxscDN3AvbZZ0yFbRW4EEa8euEHaKOi/h4VYCcWptSGqXehd1k/ay X-Received: by 2002:a17:902:8ec4:: with SMTP id x4-v6mr44688500plo.370.1525866092693; Wed, 09 May 2018 04:41:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1525866092; cv=none; d=google.com; s=arc-20160816; b=t2FtqG6R+6O/teV6apV4CrD1FA1PuAb4A26Gm656rF3W9PM2Q5W6ZeOIR0DH798dIz rFyn+31cG9k3BTGEbNqnxpM2uyONhVlSt4qZ+iTGDx9AbrJsgwNtJoSDRKYmyl+5WzB7 FFP38SePjEA2BSj61g9DrUwMjQuomdrNAbYw5ktIZ4xfV27wFU1FbZSeZrYrKoCx/oG1 rAMOm7OgzcpZZ+nrX/jdzEE38IZXoNXJEwO3cmsnwEo7BQ6B7XzFxBvKUxicmkEUIJxP gNVAWw/SNMnDrviYdaMTz6HiuV5iPTphetOIJlDOVmiWltp3sfYiOAl7EV+pXZ8bXdD1 SPdQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:message-id:references :in-reply-to:subject:cc:to:from:date:content-transfer-encoding :mime-version:dkim-signature:dkim-signature :arc-authentication-results; bh=93TeyR+8V08vrIDY/SBdqCpCI2f20FT4WeHbJ4iODxk=; b=kG0eIdlTRV8yy0aO6/i612wiVuehUkdVeTyTJM/x6dXBWroWjW0KPFwYBKHyoOcEKV jWefL0zbrXWjBO6X5mZTEZSR7lMdCVX4sBrjFCrst6fthYhSrw1HK6DmQ1o3FHb4xDzG ZhIgfAmy3Ku9idAqIFVjGyIFd9UCFUjdjo9+4Bgg9ZUzRoIjkliFTjaHDuRmjawbhsOp BWTjAIaIwkBAyXqgMIy7ImSjq1SWCuNMC88pyGEmTNC/TQVaYr+ZS8PHe4H2SpX1spHY LVVqndOQt3z7zDvCxxLktcFoEgOKJ7QusjEEoKJ2lCjSLsL7IPO3xAjYslQ+irXnQb73 Nqog== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@codeaurora.org header.s=default header.b=RMcMancP; dkim=pass header.i=@codeaurora.org header.s=default header.b=gxzI7kvz; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id g34-v6si26484126pld.411.2018.05.09.04.41.18; Wed, 09 May 2018 04:41:32 -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=@codeaurora.org header.s=default header.b=RMcMancP; dkim=pass header.i=@codeaurora.org header.s=default header.b=gxzI7kvz; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934383AbeEILj6 (ORCPT + 99 others); Wed, 9 May 2018 07:39:58 -0400 Received: from smtp.codeaurora.org ([198.145.29.96]:60368 "EHLO smtp.codeaurora.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933832AbeEILj4 (ORCPT ); Wed, 9 May 2018 07:39:56 -0400 Received: by smtp.codeaurora.org (Postfix, from userid 1000) id D09CC60FAA; Wed, 9 May 2018 11:39:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525865995; bh=9fDApyGquPlP6kQ3/RnVY9XLlbHP5hoGCwxgLye5LxU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=RMcMancPtjsd4GRx3AT1PkiI1ckPTdRX3fs0M+26eK4cJZfYraWRoTA+9Z6gqQh2f FqY1wtI4E+o34BLolbGcjN24qTtkaPHMJhPCumBMcUbqWtB08k0FLYCuRi1+YsJnYN eMFE6mLHqKC97Z5p063fJjzaBveJskiSPb4KX9sU= X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on pdx-caf-mail.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.8 required=2.0 tests=ALL_TRUSTED,BAYES_00, DKIM_SIGNED,T_DKIM_INVALID autolearn=no autolearn_force=no version=3.4.0 Received: from mail.codeaurora.org (localhost.localdomain [127.0.0.1]) by smtp.codeaurora.org (Postfix) with ESMTP id 546BF60F8F; Wed, 9 May 2018 11:39:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=codeaurora.org; s=default; t=1525865994; bh=9fDApyGquPlP6kQ3/RnVY9XLlbHP5hoGCwxgLye5LxU=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=gxzI7kvzzK8JbV32h5rjuli4R+yqb8A5Jc5ux1QGzH5uFZBtwT7bODctoTRaIT0SQ +Mi55j3kgXlwXRKwxkTsza0CWsAFv8rlI17Ol3FGgGrOlmsjZ84MIBUwvBACuumogT 4oo/p8aheqvHn+IBibV9OtqL8eHJzaJ5PkL5bcA0= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Wed, 09 May 2018 17:09:54 +0530 From: Amit Nischal To: Stephen Boyd Cc: Rob Herring , Michael Turquette , Stephen Boyd , Andy Gross , David Brown , Rajendra Nayak , Odelu Kukatla , Taniya Das , linux-arm-msm , "open list:ARM/QUALCOMM SUPPORT" , linux-clk , linux-kernel@vger.kernel.org, devicetree@vger.kernel.org, linux-clk-owner@vger.kernel.org Subject: Re: [PATCH v1 0/2] Add QCOM video clock controller driver In-Reply-To: <152581050735.138124.795656319855957213@swboyd.mtv.corp.google.com> References: <1525350925-16006-1-git-send-email-anischal@codeaurora.org> <152545146453.138124.2471609033510400995@swboyd.mtv.corp.google.com> <09ac2bd5eab25cfc70a1c5dc7b0f90ed@codeaurora.org> <20180507171121.GA22656@rob-hp-laptop> <8ac8a361a7dc69cce1e7498f1473bad8@codeaurora.org> <152581050735.138124.795656319855957213@swboyd.mtv.corp.google.com> Message-ID: X-Sender: anischal@codeaurora.org User-Agent: Roundcube Webmail/1.2.5 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2018-05-09 01:45, Stephen Boyd wrote: > Quoting Rob Herring (2018-05-08 05:48:07) >> On Mon, May 7, 2018 at 11:53 PM, Amit Nischal >> wrote: >> > On 2018-05-07 22:41, Rob Herring wrote: >> >> >> >> On Mon, May 07, 2018 at 04:16:53PM +0530, Amit Nischal wrote: >> >>> >> >>> On 2018-05-04 22:01, Stephen Boyd wrote: >> >>> > Quoting Amit Nischal (2018-05-03 05:35:23) >> >>> > > Changes in v1: >> >>> > > https://lkml.org/lkml/2018/4/24/545 >> >>> > > Addressed below review comments given by Rob >> >>> > > - Change the compatible property as per ',-' >> >>> > > format. >> >>> > > - Add header definitions for resets and power-domain cells. >> >>> > >> >>> > You didn't add any reset definitions though? >> >>> >> >>> We haven't added the reset definitions for videocc as there is no >> >>> video reset client. >> >> >> >> >> >> So? You don't know what resets there are? >> >> >> > >> > We know the resets, but video driver doesn't do any block resets >> > prior to accessing the video subsystem so that's the reason we do >> > not want to expose the resets in videocc driver. >> >> Bindings don't have to match what drivers currently use but should be >> complete as possible. > > Right. Please add the #defines in the header file for the resets. You > can leave them out of the driver if you really want to, but typically > we > still add them and then rely on not touching them if they shouldn't be > used. Thanks for the suggestion. I will add the videocc resets in the header file.