Received: by 2002:a25:7ec1:0:0:0:0:0 with SMTP id z184csp3480298ybc; Thu, 14 Nov 2019 09:42:24 -0800 (PST) X-Google-Smtp-Source: APXvYqxzluaLJHL0TZAgockgDUFFHPL/SjpYQBN56V3fxjQgGIAYXGgJnvesiwKCWt/rUv02WOb8 X-Received: by 2002:aa7:d391:: with SMTP id x17mr2650923edq.43.1573753344647; Thu, 14 Nov 2019 09:42:24 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1573753344; cv=none; d=google.com; s=arc-20160816; b=dVZthM9Uyb2VEYyWkPJ4OLsAS1fleqGon04I6xU2qxmIbHbBTfOnJpznw6RETH+Dcx 2l09Oe01l4Ic5ubF4BHwhPVuL9rB+o5pCKvDw1plPGjRxdGYhzpvxQiiIwyRaN6zMVw2 mR+k1IEog756R74pW19UP1HD/dLyQ885eHHI/hIP+D4esl5Yx+DkT8Hwk5cw8KwGMN0M n/p3oYZwCRx287l66y+DadsU5FyaIq6OsveVFU6eu4iCWxJgNMH1gx+bZ5HbZuaxj7Nt QHnLRjE33x76m9z1c4AI1tzKFufZQB6BMyQkCeQe2t3/TNRIvvpPryPdfnoRoTGr2x2H eBqw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=owpgnNukquuuIg9v9mi/2GWFAuq99bPG6NDaDjFe8g8=; b=p0WMEmp3zGOtRw5bAmEbvs1f7IvtTcOoR3OoD2X0sR8CzDDtUqTOosSYtZrIF0cA7e SDyDcOBJEPFFnYy8JdUtXr2XtyHEaKvdUuyw6aQX6A1K/CjlL6MDEMfTdFAiu05lVLon 0Jmd+OJ2OtuAGRdmrSg6S+JE6EoPpo8CsgN2ZbS+EUul4V3rowThkfpA6fXc2qXAJ0Hm HtUvmpiKGrJfs3GnAroe4cN2vo6x14NS5MFdQvZF+SL8MTfqgayg42pNUYWB1NyEoj9g MIgUWn1LlPMcw73yZ6uBcsGcLrGF0N0iGGqfKMxbm6H7kFbnItJML/5xgw3w2rBmh0us EGpQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=qN2v5wV0; 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=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id s6si4036799edr.37.2019.11.14.09.41.59; Thu, 14 Nov 2019 09:42:24 -0800 (PST) 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=@kernel.org header.s=default header.b=qN2v5wV0; 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=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726674AbfKNRjx (ORCPT + 99 others); Thu, 14 Nov 2019 12:39:53 -0500 Received: from mail.kernel.org ([198.145.29.99]:52764 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725976AbfKNRjx (ORCPT ); Thu, 14 Nov 2019 12:39:53 -0500 Received: from mail-qv1-f48.google.com (mail-qv1-f48.google.com [209.85.219.48]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 34B0120718; Thu, 14 Nov 2019 17:39:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1573753192; bh=VzKteWn1F/CosCCsd6C4IKUCGWE4H5oQV8jGARZ48tc=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=qN2v5wV095fAUbYtR5P6fE7B5vGnb+vx313xCT936CPIndi5UGPzUwBJ4RrLRuJ3x doWz3mevftGogNgXftWdpHE1RIm0Y5J6GvK5tLIDIKNpwQIF4FFify2At4paexUm3K 4SIxI+snb5+OFz1v88ytyKBaUGmq/kZP83rqrNBI= Received: by mail-qv1-f48.google.com with SMTP id s18so2698307qvr.4; Thu, 14 Nov 2019 09:39:52 -0800 (PST) X-Gm-Message-State: APjAAAWU3N45mXI3Ud44Pp4vYPoEZm/VZN9MOpL5LaaVCp0AL7a7LjP+ ZR2aMon3mU4pSQ46aeWgIpGYozdnZqVv/a9nCw== X-Received: by 2002:a0c:d2b4:: with SMTP id q49mr8873666qvh.135.1573753191385; Thu, 14 Nov 2019 09:39:51 -0800 (PST) MIME-Version: 1.0 References: <96537f8702501a45501d5a59ca029f92e36a9e4a.1573455324.git.rahul.tanwar@linux.intel.com> <1d3be294-5f12-462c-855c-e53ecb9190b7@linux.intel.com> In-Reply-To: <1d3be294-5f12-462c-855c-e53ecb9190b7@linux.intel.com> From: Rob Herring Date: Thu, 14 Nov 2019 11:39:40 -0600 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v6 2/2] dt-bindings: pinctrl: intel: Add for new SoC To: "Tanwar, Rahul" Cc: Linus Walleij , Mark Rutland , "open list:GPIO SUBSYSTEM" , "linux-kernel@vger.kernel.org" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Andriy Shevchenko , qi-ming.wu@intel.com, yixin zhu , cheol.yong.kim@intel.com Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Nov 13, 2019 at 9:27 PM Tanwar, Rahul wrote: > > > Hi Linus, > > On 13/11/2019 10:46 PM, Linus Walleij wrote: > > On Mon, Nov 11, 2019 at 11:11 AM Rahul Tanwar > > wrote: > > > >> Add dt bindings document for pinmux & GPIO controller driver of > >> Intel Lightning Mountain SoC. > >> > >> Signed-off-by: Rahul Tanwar > > (...) > > > >> +properties: > >> + compatible: > >> + const: intel,lgm-pinctrl > > Just noted from another review where Rob noted that this name should > > match the internal name in the datasheet for this hardware block. Is it > > really called "lgm-pinctrl" inside Intel? > > > > intel,lightning-mountain-io and similar are perfectly fine if that is the > > name it has in your documentation. > > Our documentation does not have any specific names for these hardware > blocks. It names it in a very generic/standard manner like GPIO, pinmux.. > > To make the name explicit & self explanatory, i should probably change > the name as you suggested i.e. intel,lightning-mountain-io. You should also be consistent with 'lgm' vs. 'lightning-mountain' use across bindings some of which I think have already been accepted. Rob