From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S933597AbcHJUtz (ORCPT ); Wed, 10 Aug 2016 16:49:55 -0400 Received: from hqemgate15.nvidia.com ([216.228.121.64]:11832 "EHLO hqemgate15.nvidia.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S933093AbcHJSLm (ORCPT ); Wed, 10 Aug 2016 14:11:42 -0400 X-PGP-Universal: processed; by hqnvupgp07.nvidia.com on Wed, 10 Aug 2016 02:52:59 -0700 Message-ID: <57AAF68D.7090707@nvidia.com> Date: Wed, 10 Aug 2016 15:10:29 +0530 From: Laxman Dewangan User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:24.0) Gecko/20100101 Thunderbird/24.4.0 MIME-Version: 1.0 To: Rob Herring , , CC: , , , Krzysztof Kozlowski , Javier Martinez Canillas Subject: Re: [PATCH V3 2/4] clk: Combine DT binding doc for max77686 and max77802 References: <1466160667-28451-1-git-send-email-ldewangan@nvidia.com> <1466160667-28451-3-git-send-email-ldewangan@nvidia.com> <20160620163947.GA27492@rob-hp-laptop> <5768E2AD.8070004@nvidia.com> <57725F64.4030903@nvidia.com> In-Reply-To: <57725F64.4030903@nvidia.com> X-Originating-IP: [10.19.65.30] X-ClientProxiedBy: DRUKMAIL101.nvidia.com (10.25.59.19) To bgmail102.nvidia.com (10.25.59.11) Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Tuesday 28 June 2016 04:58 PM, Laxman Dewangan wrote: > Hi Rob, > > On Tuesday 21 June 2016 12:16 PM, Laxman Dewangan wrote: >> >> On Monday 20 June 2016 10:09 PM, Rob Herring wrote: >>> On Fri, Jun 17, 2016 at 04:21:05PM +0530, Laxman Dewangan wrote: >>>> >>>> >>>> + >>>> Following properties should be presend in main device node of the >>>> MFD chip. >>>> Required properties: >>> I'd expect to see compatible strings updated... >>> >> >> There is no separate compatible string for clock. The clock nodes is >> the parent node only and the compatible described in the parent DT >> binding doc. >> >> >> Do we also need to add same thing here? > > Are you fine with the above? As there is no compatible string for > clock (clock does not have separate node), do I still need to add > explicitly here? > Can you please help here to review? If required, I can rebase and re-send the patches. Thanks, Laxman