From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755647AbeEHUPL (ORCPT ); Tue, 8 May 2018 16:15:11 -0400 Received: from mail.kernel.org ([198.145.29.99]:43888 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752259AbeEHUPI (ORCPT ); Tue, 8 May 2018 16:15:08 -0400 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 To: Amit Nischal , Rob Herring From: Stephen Boyd In-Reply-To: Cc: 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 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> Message-ID: <152581050735.138124.795656319855957213@swboyd.mtv.corp.google.com> User-Agent: alot/0.7 Subject: Re: [PATCH v1 0/2] Add QCOM video clock controller driver Date: Tue, 08 May 2018 13:15:07 -0700 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by mail.home.local id w48KFEea009867 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.