Received: by 2002:ac0:946b:0:0:0:0:0 with SMTP id j40csp2806863imj; Mon, 18 Feb 2019 12:38:36 -0800 (PST) X-Google-Smtp-Source: AHgI3IbDraQDe6W3jOgeiOzEvyVNZq3+QzHzOgIE9PcoKs/afVnRYCxDtEnUIm6VnD8tmiXmmptY X-Received: by 2002:a63:5b48:: with SMTP id l8mr20568912pgm.80.1550522316767; Mon, 18 Feb 2019 12:38:36 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1550522316; cv=none; d=google.com; s=arc-20160816; b=oCsmPIU/CGvbnMOBHtDFAbGRmjeOEpJcJHYnnh6i3hgN9ZML/t1x9MwZI+W87ZIjoJ b2U0Ee/OuKOu+OiTIYWcLCzPVeiqxMhDiw5kH/JdX9rIrD+WFZq8HHnp7y8EZPIdbx0Z 1Ob5UgtzUp3il/rGkvE1sY0/pNBiNr22/1HiZl1ki3cDnBu4LSC0+uH+7qrY6s4ytlxh VIAlSh8XVCcHP8nAJjCtmRgbD0uiDS7pGYTK5KREaN/yfFzmSK5s5oml5QBavzC4q1Tu KZ9XbUsRrWro6T+qUAOeOJ7prXyv/EusqGAQJSfXCir/r8o/RmkBPh+Z7T50cn1Nza2p UkGA== 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:from:date; bh=mxTMXYrQIwaNJervkd9UktCFa4U1xZCoJrS9clPs9rc=; b=AdL6Q534CatAIgirnCelNpv9/h6ZZ4gk8UQzq35v5OfdTomrepBkE4BBzurcQFN2di r4YNCOnmTJ+bhpAFF/uMBrbd0jy8nLv11c83b5J3zJoJbHhH8GtNer4ffynuatB37HOc BnmRzez1yILZSeH6X5LGum1r4dplsXY0DeglGsgVW52WeL8cjcGnA3EEDz3ZOmPoRkU4 X6F9FerlabbG3U5Ao6HGnNf+TdFfOWgCBke2o+3qgaLX3NutJdk+ITGsyERQ48oHNWAF l4yJDt1+Vud0ToaEHJ39+ipiHaB+LV6lZbuLMv1/ugxVY/5ygbg1ebIEugWz8/9IOhd9 csoQ== ARC-Authentication-Results: i=1; mx.google.com; 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=fail (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 k188si14595797pgc.246.2019.02.18.12.38.20; Mon, 18 Feb 2019 12:38:36 -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; 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=fail (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729686AbfBRUhB (ORCPT + 99 others); Mon, 18 Feb 2019 15:37:01 -0500 Received: from mail-ot1-f66.google.com ([209.85.210.66]:41383 "EHLO mail-ot1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727920AbfBRUhB (ORCPT ); Mon, 18 Feb 2019 15:37:01 -0500 Received: by mail-ot1-f66.google.com with SMTP id t7so14099658otk.8; Mon, 18 Feb 2019 12:37:00 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=mxTMXYrQIwaNJervkd9UktCFa4U1xZCoJrS9clPs9rc=; b=dy0LN+nhee3gKhbFJDUiEG70yydoDFo7Jcwv9Iqm0R02vDbdciF1LtXjZKUzgHopGZ ulZXlTK0DNKstFUCocLw+zKz2ui9HxDuCxqBcu3i2vJIcNlGQeWd47K++PaaMAgRYKyt OQco2vZzr3qiU2aPl7VH7l2lMuFU2PypFKVyX0jaMurCQl7URHmEEzVwvajYM2ufKJ51 bU+JovecQvc0ekQEqVtqjoLQ1dgZ7ZTevKU6J1gMrh8iG9VJVXiksEGcgNqxnmEBUqtZ u97SM9y79qrfq7lj0uFWelo+BZzlOu5lVvPqnYH9VQTHBpVDOqWwunvBth4OTyTl3W7Z H2Wg== X-Gm-Message-State: AHQUAuYa74uWasBGwNQtMqSQ4kgyZt+D0uLYsogjT1qHhwJzy7ms/Ad0 ys2JIcf9F64N863li1JhoA== X-Received: by 2002:a05:6830:1092:: with SMTP id y18mr15795045oto.125.1550522220168; Mon, 18 Feb 2019 12:37:00 -0800 (PST) Received: from localhost (24-155-109-49.dyn.grandenetworks.net. [24.155.109.49]) by smtp.gmail.com with ESMTPSA id r132sm3524453oie.20.2019.02.18.12.36.59 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Mon, 18 Feb 2019 12:36:59 -0800 (PST) Date: Mon, 18 Feb 2019 14:36:58 -0600 From: Rob Herring To: Matthias Brugger Cc: Ryder Lee , Thierry Reding , Sean Wang , Weijie Gao , linux-pwm@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org Subject: Re: [PATCH v1 2/5] dt-bindings: pwm: add a property "mediatek,num-pwms" Message-ID: <20190218203658.GA20434@bogus> References: <7e1de17a43f2cde73aecd2773e2b3a5fdfd294f3.1547781007.git.ryder.lee@mediatek.com> <7d387d2a-74f0-c6c7-aa2d-cf9b87579682@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7d387d2a-74f0-c6c7-aa2d-cf9b87579682@gmail.com> User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Jan 18, 2019 at 09:44:49AM +0100, Matthias Brugger wrote: > > > On 18/01/2019 04:24, Ryder Lee wrote: > > This adds a property "mediatek,num-pwms" in example so that we could > > set the number of PWM channels via device tree. > > > > Signed-off-by: Ryder Lee > > Reviewed-by: Matthias Brugger > > --- > > Changes since v1: add a Reviewed-by tag. > > --- > > Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 2 ++ > > 1 file changed, 2 insertions(+) > > > > diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt > > index 991728c..f9e2d1f 100644 > > --- a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt > > +++ b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt > > @@ -20,6 +20,7 @@ Required properties: > > - pinctrl-names: Must contain a "default" entry. > > - pinctrl-0: One property must exist for each entry in pinctrl-names. > > See pinctrl/pinctrl-bindings.txt for details of the property values. > > + - mediatek,num-pwms: the number of PWM channels. > > > > Example: > > pwm0: pwm@11006000 { > > @@ -37,4 +38,5 @@ Example: > > "pwm3", "pwm4", "pwm5"; > > pinctrl-names = "default"; > > pinctrl-0 = <&pwm0_pins>; > > + mediatek,num-pwms = <5>; > > }; > > > > Wasn't there a comment in the last version to use num-pwms instead of > mediatek,num-pwms? > > Uwe I think you requested that. Perhaps, but why is this needed? Typically, this would be implied by the compatible or the driver doesn't care and we assume 'pwms' properties are not out of range. Rob