Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp6731498ybn; Mon, 30 Sep 2019 02:52:45 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJjixiUGQiz9u7HX3KWKFCY1KMdUaArXJbYoOoO9s6wsXc7DBovCXYUlI7uVyl/JhzR0Cq X-Received: by 2002:a50:eb44:: with SMTP id z4mr18073688edp.207.1569837165322; Mon, 30 Sep 2019 02:52:45 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569837165; cv=none; d=google.com; s=arc-20160816; b=BzWTSTGTg3MDUsN89PXC3ZptohcrHXgDzCUaakzDTtAYA3tTj/mGw7Gb+AdITR3MY8 V3JF31DAG4/u5TDlQ9juy4mZFvOMYnPz85t+HmMOH2X9gaXokFDZfaxxJbZROgdiW2iT Z1NdhkZiUZvvZqwSXuyHZsMsuZjMrlReDGrr7jQix/FoVv7pOY+BMbUTZ7IhSyNvu6S+ DuFVhCGBf0LCpnRk9agUMH+wl4YipGQKe3ks2OV+jmioKaSdpn+EMF5IG0Hhy+Yc5Xqo HFYetagOuTgqT8rvECbPaVtKPe1z4Y9UxXQ9Y2hqYhU7NS687xs3xWJRx3D1Zr/pq/iF vzvw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :references:in-reply-to:date:cc:to:from:subject:message-id; bh=in6dXa211yCrhRjVpxsOuWln+wTRt6zqrrZ93+N20CY=; b=EpFU7rHEkrCRu2Y7RxbFrSdcl+dTHCqL8y8pi5YtilFhJkz94rcvGyQuALLQTxb7OP wCQ+6ck3W5G6eGUKHJ0eFJeAkAvBla1U7rkVGGtuOuiGKgjq9DxYqOuXN5ghjwSTHXRo KgrHnHz0VhuGc8UasxiwCrD+EbVFP9mQHAQN+NyTAKLBEs/ScewDjzW31/ihJ6zpBlWS xDT3tjbgBiNACqxLNTDU6DSyvzldTNzMl+MrMPvnIaTXpnq1Kc4yhr/dw0x4/kDRRvNX 5/SrEHPrcfD3pOHLQw1MbPw13To/M1phD3f907ErWEgQDb9v9wPKlSweER3zaE9KTink aGww== 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=mediatek.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id d22si6677302ede.131.2019.09.30.02.52.20; Mon, 30 Sep 2019 02:52:45 -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; 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=mediatek.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730534AbfI3Jv2 (ORCPT + 99 others); Mon, 30 Sep 2019 05:51:28 -0400 Received: from mailgw01.mediatek.com ([210.61.82.183]:59170 "EHLO mailgw01.mediatek.com" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726504AbfI3Jv1 (ORCPT ); Mon, 30 Sep 2019 05:51:27 -0400 X-UUID: 6ae0d28dc9b24e3187041e13772beeaa-20190930 X-UUID: 6ae0d28dc9b24e3187041e13772beeaa-20190930 Received: from mtkmrs01.mediatek.inc [(172.21.131.159)] by mailgw01.mediatek.com (envelope-from ) (Cellopoint E-mail Firewall v4.1.10 Build 0809 with TLS) with ESMTP id 231710556; Mon, 30 Sep 2019 17:51:21 +0800 Received: from mtkcas08.mediatek.inc (172.21.101.126) by mtkmbs08n1.mediatek.inc (172.21.101.55) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Mon, 30 Sep 2019 17:51:18 +0800 Received: from [172.21.84.99] (172.21.84.99) by mtkcas08.mediatek.inc (172.21.101.73) with Microsoft SMTP Server id 15.0.1395.4 via Frontend Transport; Mon, 30 Sep 2019 17:51:17 +0800 Message-ID: <1569837079.32131.5.camel@mtksdccf07> Subject: Re: [PATCH v10 08/12] pwm: mediatek: Add MT7629 compatible string From: Sam Shih To: Thierry Reding CC: Rob Herring , Mark Rutland , Matthias Brugger , Ryder Lee , John Crispin , , , , Date: Mon, 30 Sep 2019 17:51:19 +0800 In-Reply-To: <20190930093629.GH1518582@ulmo> References: <1569421957-20765-1-git-send-email-sam.shih@mediatek.com> <1569421957-20765-9-git-send-email-sam.shih@mediatek.com> <20190927112831.GA1171568@ulmo> <1569833468.32131.4.camel@mtksdccf07> <20190930093629.GH1518582@ulmo> Content-Type: text/plain; charset="ISO-8859-15" X-Mailer: Evolution 3.2.3-0ubuntu6 Content-Transfer-Encoding: 7bit MIME-Version: 1.0 X-MTK: N Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, 2019-09-30 at 11:36 +0200, Thierry Reding wrote: > On Mon, Sep 30, 2019 at 04:51:08PM +0800, Sam Shih wrote: > > Hi, > > > > On Fri, 2019-09-27 at 13:28 +0200, Thierry Reding wrote: > > > On Wed, Sep 25, 2019 at 10:32:33PM +0800, Sam Shih wrote: > > > > This adds pwm support for MT7629, and separate mt7629 compatible string > > > > from mt7622 > > > > > > > > Signed-off-by: Sam Shih > > > > --- > > > > drivers/pwm/pwm-mediatek.c | 6 ++++++ > > > > 1 file changed, 6 insertions(+) > > > > > > I picked this patch up and made some minor adjustments to make it build > > > without the num_pwms patches. With that I don't think there's anything > > > left from this series that you need. > > > > Yes, I think the driver should work once dtsi updated. > > ("[v10,12/12] arm: dts: mediatek: add mt7629 pwm support") > > > > But, due to we use comaptible string separately for every SoC now, > > The comaptible string in dt-bindings should be "mediatek,mt7629-pwm". > > I think we should use "[v10,11/12] dt-bindings: pwm: update bindings > > for MT7629" to replace commit 1c00ad6ebf36aa3b0fa598a48b8ae59782be4121, > > Or maybe we need a little modification like this ? > > diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt ... > > - - "mediatek,mt7629-pwm", "mediatek,mt7622-pwm": found on mt7629 SoC. > > + - "mediatek,mt7629-pwm": found on mt7629 SoC. > > Good catch, I must've taken this from the wrong version of the patch. > > How about the attached patch? > > Thanks, > Thierry > --- >8 --- > From 641b0ee176b139f9edd137ba636ca0cb9c63289a Mon Sep 17 00:00:00 2001 > From: Thierry Reding > Date: Mon, 30 Sep 2019 11:33:31 +0200 > Subject: [PATCH] dt-bindings: pwm: mediatek: Remove gratuitous compatible > string for MT7629 > > The MT7629 is, in fact, not compatible with the MT7622 because the > former has a single PWM channel while the former has 6. Remove the > gratuitous compatible string for MT7629. > > Reported-by: Sam Shih > Signed-off-by: Thierry Reding > --- > Documentation/devicetree/bindings/pwm/pwm-mediatek.txt | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt > index c8501530173c..053e9b5880f1 100644 > --- a/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt > +++ b/Documentation/devicetree/bindings/pwm/pwm-mediatek.txt > @@ -6,7 +6,7 @@ Required properties: > - "mediatek,mt7622-pwm": found on mt7622 SoC. > - "mediatek,mt7623-pwm": found on mt7623 SoC. > - "mediatek,mt7628-pwm": found on mt7628 SoC. > - - "mediatek,mt7629-pwm", "mediatek,mt7622-pwm": found on mt7629 SoC. > + - "mediatek,mt7629-pwm": found on mt7629 SoC. > - "mediatek,mt8516-pwm": found on mt8516 SoC. > - reg: physical base address and length of the controller's registers. > - #pwm-cells: must be 2. See pwm.txt in this directory for a description of It seems good to me. Thanks, Regards, Sam