Received: by 2002:a25:4158:0:0:0:0:0 with SMTP id o85csp3323387yba; Mon, 6 May 2019 22:26:08 -0700 (PDT) X-Google-Smtp-Source: APXvYqyKAXJ8VQwdMP90LMfZJKvt6KD/j9O5brtOqimbzYVgggzALQ35KKE2zTk2YdB82Q0OQ3ov X-Received: by 2002:a65:6091:: with SMTP id t17mr37139394pgu.328.1557206768771; Mon, 06 May 2019 22:26:08 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1557206768; cv=none; d=google.com; s=arc-20160816; b=niA+Hrj9YogrUH3/9vtpI332kbKplhcJDAX7w1nvl7C6IP38zJjHWFyNNwzlrdRH9P IkQfiadgsr46ATz6mSWlbEzDGfeX3t8t7ervEJ6tNar9dyIK6QnMg3nP44ufgPIGTkvk WAg6cMDhyCdlicjkuUjt5u4XaGACbFA3iaIYpJQRWFr1mVdhjuOD4U5m2TLvnpVA7M7Q j+xv0IJ4uQ431SalbghaDf+2LsMWjmJyrdqI+h7FEUWe4zDlAuziAcROrmuvcbwjgvG6 N47rWoflasJiKhdTiuzdF71Z7XKqjBvltSdjUETIlsvCWe9LAFMIALReTbzCaO7A1ShK 4XcA== 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=0hFqmwNLrgOZ2d4LHKnw2c1GsxJZR0XMM1CJizfkss0=; b=bTiugQwnpR/aj4cyzHu7swOB8C1xTB2G9PVnJeke8eNjNUkoHmU9hyWWPRSR78x1Ed ZIgi7wh4PbwxU/oPw/aUPbCNOygmvlHJFxw5cw8eB6IGXleOnVpdqmVsdVzigcHcGFaB sZEGja5iz0P5l5E4X2GzrJzbzH1cgPJTX91Ti0qSpPNTB6tkjaRN4KlRaIJx0E5dsZcx cue3TOw9IyCUTdpuiNigbEvJFwqelVOTO9XoXgdlD4y8QvP5euAYouH75Iyzi0DTz5C/ 1yaX+7MG0OfHy86CR6H32yOEa0O6AVuRvxxLIniTakHZnA/jEG8F7nAtyFOBVCL1+47T KkuA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=oTNWEoWU; 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=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id t5si17719294plo.41.2019.05.06.22.25.52; Mon, 06 May 2019 22:26:08 -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=@chromium.org header.s=google header.b=oTNWEoWU; 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=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726427AbfEGFZD (ORCPT + 99 others); Tue, 7 May 2019 01:25:03 -0400 Received: from mail-qt1-f194.google.com ([209.85.160.194]:36990 "EHLO mail-qt1-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725843AbfEGFZD (ORCPT ); Tue, 7 May 2019 01:25:03 -0400 Received: by mail-qt1-f194.google.com with SMTP id o7so5679388qtp.4 for ; Mon, 06 May 2019 22:25:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0hFqmwNLrgOZ2d4LHKnw2c1GsxJZR0XMM1CJizfkss0=; b=oTNWEoWULY5My61dxjSyob+ke4AB8mRsMSGQA39QxxGStJqKwc6brL3ScY9Pf6MlNV cHlwWL4HZ2LL18qYr53Bt8gCq0vAEVs49chuSjny1Td+/Havv9W25UPJAwR7YrDl8KVP gd5O+H3z2FdeEtB4nJ1685Y+V8/0Vt3jWOwxA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0hFqmwNLrgOZ2d4LHKnw2c1GsxJZR0XMM1CJizfkss0=; b=oqEcTq7/KU4XMr5J6DMqRLe2tm5s8KhBNuGHU+YsJN5uWq9l/ypq1JyBIJs8idLS1d OxQLpKs8bGCyKIawLCynRrqHdJv9mFoQoFXWC6aiOekXqzq0NKWU8t7NAXfeGLSQ5/ZP mG4IVHgjTjiSIUZG8tvtHEahZkUqUruGtc4AUjmqPg9Q3d22k5T4Z+EXhDi30tpMDyz7 B3XEnSZr+lhyPGfYidQZGgd6aHZeo5MLRACqi8GFj0LqKv3HIraczvEJn4079+9u74GJ mkSzP8kuOWpFIcodzbFrRXm6Cq0OZt+uZgyycLp9obhyOmoOGQvfWSaty2iWzx4k7otI Txpw== X-Gm-Message-State: APjAAAVRaOBJLwvrSEPJFUuXfuC/Uxlqt6WCBYFcI37NJmPfBluNKJo/ ord2Djw9jP2CxeF94K/5CRNxwPNmT6kiPxokIW7Xhg== X-Received: by 2002:ac8:1ae2:: with SMTP id h31mr7545363qtk.75.1557206702363; Mon, 06 May 2019 22:25:02 -0700 (PDT) MIME-Version: 1.0 References: <20190503093117.54830-1-hsin-hsiung.wang@mediatek.com> <20190503093117.54830-5-hsin-hsiung.wang@mediatek.com> In-Reply-To: <20190503093117.54830-5-hsin-hsiung.wang@mediatek.com> From: Nicolas Boichat Date: Tue, 7 May 2019 14:24:51 +0900 Message-ID: Subject: Re: [PATCH v3 04/10] dt-bindings: mfd: Add compatible for the MediaTek MT6358 PMIC To: Hsin-Hsiung Wang Cc: Lee Jones , Rob Herring , Mark Brown , Matthias Brugger , Mark Rutland , Alessandro Zummo , Alexandre Belloni , srv_heupstream , devicetree@vger.kernel.org, Sean Wang , Liam Girdwood , lkml , "moderated list:ARM/Mediatek SoC support" , linux-arm Mailing List , Eddie Huang , linux-rtc@vger.kernel.org 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 Fri, May 3, 2019 at 6:34 PM Hsin-Hsiung Wang wrote: > > This adds compatible for the MediaTek MT6358 PMIC. > > Acked-for-MFD-by: Lee Jones > Signed-off-by: Hsin-Hsiung Wang > --- > Documentation/devicetree/bindings/mfd/mt6397.txt | 11 ++++++++--- > 1 file changed, 8 insertions(+), 3 deletions(-) > > diff --git a/Documentation/devicetree/bindings/mfd/mt6397.txt b/Documentation/devicetree/bindings/mfd/mt6397.txt > index 0ebd08af777d..62f1c17c7738 100644 > --- a/Documentation/devicetree/bindings/mfd/mt6397.txt > +++ b/Documentation/devicetree/bindings/mfd/mt6397.txt > @@ -17,22 +17,27 @@ Documentation/devicetree/bindings/soc/mediatek/pwrap.txt > This document describes the binding for MFD device and its sub module. > > Required properties: > -compatible: "mediatek,mt6397" or "mediatek,mt6323" > +compatible: > + "mediatek,mt6323" for PMIC MT6323 > + "mediatek,mt6358" for PMIC MT6358 > + "mediatek,mt6397" for PMIC MT6397 > > Optional subnodes: > > - rtc > Required properties: > - - compatible: "mediatek,mt6397-rtc" > + - compatible: "mediatek,mt6397-rtc" or "mediatek,mt6358-rtc" > - regulators > Required properties: > - compatible: "mediatek,mt6397-regulator" > see Documentation/devicetree/bindings/regulator/mt6397-regulator.txt > + - compatible: "mediatek,mt6358-regulator" > + see Documentation/devicetree/bindings/regulator/mt6358-regulator.txt > - compatible: "mediatek,mt6323-regulator" > see Documentation/devicetree/bindings/regulator/mt6323-regulator.txt > - codec > Required properties: > - - compatible: "mediatek,mt6397-codec" > + - compatible: "mediatek,mt6397-codec" or "mediatek,mt6358-sound" Sean had a question about this (https://patchwork.kernel.org/patch/10846669/#22524299): "why didn't we use a more consistent naming as mt6358-codec?" > - clk > Required properties: > - compatible: "mediatek,mt6397-clk" > -- > 2.18.0 > > > _______________________________________________ > Linux-mediatek mailing list > Linux-mediatek@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-mediatek