Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp378673imm; Tue, 5 Jun 2018 22:11:32 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJjQ7AWW5q/anD3ilipsRBlT0IZVSZa7D8TRaNaYIGJsjZSjtG+321h15yOm2182C/+58O3 X-Received: by 2002:a63:735e:: with SMTP id d30-v6mr1402322pgn.257.1528261892288; Tue, 05 Jun 2018 22:11:32 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528261892; cv=none; d=google.com; s=arc-20160816; b=yw7L0FBN1tK1QoGIE1BFfUC0vZy66HbLyJAKPcXw0IJB8RBYiYpTpJ3uSGsMGrhO3b 6UhNaM4oh7VvkiSZGnyFQKD5Z8dKvH8fTJak9on/dMW8epIeik4arhRaSGZy6641S1ey +jnoO85YR2ECJwuTalCpWf2VG4evQCh9Fu/TH/iszsPWYLHPItTA+OzES36GrX7uDW6E EMsa9Smtsr8Y8bCAvorMTFmiadHJewmhQUPsTIJR876f1sVqQHwy642S0um+sc6lcDA6 FuUBHmDy+BtZuYAT5wkYQpSLXqUTq52SgPkOQuq/j15aiG0hFQBd8b9l+JhxZ8ciMi1v dn9A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:date:from:dkim-signature:arc-authentication-results; bh=ceqvcqeS9cI6k7FcZLHfpcJncAWvZxTWYkUSH+n2HJ0=; b=DXyb9Uz3mpesAPYOGpXXT69kwJGwzw9T8nu/08Ni/xomAD6S0ZKct5FHsHX9XCUIwu NL9/ktwlIozBNEnEPwGXGhAK7LuLORJA+RQIbhL08IG4G2ZVzWthQ7/y5KoZtrnf6OhW aMxovFQhoNLAM+JYVeOQgeZr5Q/7a2Ljyjbxgi0NLsWvQ6FUWBVIPpipfVMKdV/p98dK hgJKRNrRQH/k4ve+Q4nh/TnaMJGUTVSi4u/knqS5k2dQZt8TjSp56ysjl8MfB9P3nUO5 uilMf9/QR7jQCrBbxvdo5Rt5di8ieNfV9uw+ttyf52u202YeHoUOVKhOPyRRtfx5yiNa lLbw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=PvcdUUvo; 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 r21-v6si12058650pfh.333.2018.06.05.22.11.17; Tue, 05 Jun 2018 22:11: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=@gmail.com header.s=20161025 header.b=PvcdUUvo; 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 S1752160AbeFFFKY (ORCPT + 99 others); Wed, 6 Jun 2018 01:10:24 -0400 Received: from mail-lf0-f68.google.com ([209.85.215.68]:45495 "EHLO mail-lf0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750817AbeFFFKW (ORCPT ); Wed, 6 Jun 2018 01:10:22 -0400 Received: by mail-lf0-f68.google.com with SMTP id n3-v6so7024216lfe.12; Tue, 05 Jun 2018 22:10:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:date:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=ceqvcqeS9cI6k7FcZLHfpcJncAWvZxTWYkUSH+n2HJ0=; b=PvcdUUvoyK9+tgTy9zllUTFTp1Pk2OPVx5j4PgBWO3Cd7y6m3XNxdT2szjBdWjacwQ yDpDXwtkPs95EjRxnfgXTKEeBBRSj+TENr09w1JxGd3TkgQ2tITsqIP8FJlEOB/tQxFv rEb348rjaHlME3S8rEeOG+dSRCr74WJBwoPXb3RwGHOZCTa82iQnTtuTVgmpH23zbM9j QIPEclOlvoTxLAVFQMi7YtATzwfP6KAoLWwgNMEpxXrSP1L5OOkZlcHXFcoQi1m2vrTG UE0AQJN8AaG7BwDBKlzltsGWAa5b2+Lhx6bpsybbwDKjgAR3muyddOoU2DNMR3SFaFza FTuA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:date:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=ceqvcqeS9cI6k7FcZLHfpcJncAWvZxTWYkUSH+n2HJ0=; b=rNgunb6I/AENJ/JMmzOOoeesp3Y72UwbnnN1zHDXQIdDzP0QE7xLU3WqJGz4kXPhv/ 3VBihE8Yal/3nFBkM1/R1zatYNojJI8qIACleMWYZ+E3mo3WtqlOp3VDKQmQVkGTn418 QI+3uycqod0YIF67ZkEYYHVKk/fC2kWMAKE3q69ujuZRkf+h5OUvXfZOcVHi2xud7SDK 1H4yeUpwWXAHNEKieX+C1+03tza4HcC+ksD/U6FSBRao/zGVCktq80SbvueFvXZ7DcXk wYcRMIQvabSR8N8SwldTga9YZE40OQNUhhtvqZYSZkDN2NXt/VjFrTIXlB1PXVQKF6Hj u9Tw== X-Gm-Message-State: APt69E2CY02Y0xQNdGnTmLDPmLJic4RFkopLYC4BXELM5cvR3+PsrKAT LeLwJ2NcmE7CXU9bYOSkvnvpNBwt X-Received: by 2002:a19:e450:: with SMTP id b77-v6mr848232lfh.76.1528261820875; Tue, 05 Jun 2018 22:10:20 -0700 (PDT) Received: from localhost.localdomain ([213.255.186.34]) by smtp.gmail.com with ESMTPSA id w62-v6sm4673193lff.57.2018.06.05.22.10.19 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 05 Jun 2018 22:10:20 -0700 (PDT) From: Matti Vaittinen X-Google-Original-From: Matti Vaittinen Date: Wed, 6 Jun 2018 08:10:17 +0300 To: Rob Herring Cc: Matti Vaittinen , mturquette@baylibre.com, sboyd@kernel.org, mark.rutland@arm.com, lee.jones@linaro.org, lgirdwood@gmail.com, broonie@kernel.org, mazziesaccount@gmail.com, linux-clk@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, mikko.mutanen@fi.rohmeurope.com, heikki.haikola@fi.rohmeurope.com Subject: Re: [PATCH v5 3/4] clk: bd71837: Devicetree bindings for ROHM BD71837 PMIC Message-ID: <20180606051017.GB20078@localhost.localdomain> References: <20180605154932.GA20204@rob-hp-laptop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180605154932.GA20204@rob-hp-laptop> User-Agent: Mutt/1.9.2 (2017-12-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Jun 05, 2018 at 09:49:32AM -0600, Rob Herring wrote: > On Mon, Jun 04, 2018 at 04:18:53PM +0300, Matti Vaittinen wrote: > > Document devicetree bindings for ROHM BD71837 PMIC clock output. > > > > Signed-off-by: Matti Vaittinen > > --- > > .../bindings/clock/rohm,bd71837-clock.txt | 38 ++++++++++++++++++++++ > > 1 file changed, 38 insertions(+) > > create mode 100644 Documentation/devicetree/bindings/clock/rohm,bd71837-clock.txt > > > > diff --git a/Documentation/devicetree/bindings/clock/rohm,bd71837-clock.txt b/Documentation/devicetree/bindings/clock/rohm,bd71837-clock.txt > > new file mode 100644 > > index 000000000000..771acfe34114 > > --- /dev/null > > +++ b/Documentation/devicetree/bindings/clock/rohm,bd71837-clock.txt > > @@ -0,0 +1,38 @@ > > +ROHM BD71837 Power Management Integrated Circuit clock bindings > > This needs to be added to the MFD doc. One node should be covered by at > most 1 document. I was thinking of that too. But then I asked why? I also thought that if one knows there is clock block in the chip - where does he look for binding document? From clock folder. Then I saw how bindings for MAX77686 chip were written and thought that this is beneficial for all. MFD document directs to clock and regulator docs and on othe other hand, clock document clearly states that properties it describes must be present "in main device node of the MFD chip". Don't you think on searching for clock bindings should find something from clock folder? I can follow your instruction here but I think the user might be happy if he found something under bindings/clock for clock related properties. Br, Matti Vaittinen