From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 0148BE748F0 for ; Mon, 2 Oct 2023 16:10:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238411AbjJBQKd (ORCPT ); Mon, 2 Oct 2023 12:10:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:38822 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S238416AbjJBQKa (ORCPT ); Mon, 2 Oct 2023 12:10:30 -0400 Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EDB75B4 for ; Mon, 2 Oct 2023 09:10:26 -0700 (PDT) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7353DC433CA; Mon, 2 Oct 2023 16:10:25 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1696263026; bh=CfIUOjCxqP4k4PEwlJ3KWN+LSN/aN14INr8PFuBU1gc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=KmUE24gWThX+EImHY5hV0v2pHMvLxkeVCnJHZ00Ae79HwxE+sH2xf6rO2icIcHLhQ kuA8UeyUFpfQ/Rrv+WrhFR6u7+HlluCNkxLc4ZGuJMo6ouClZnoRU0/L+Ut0StCG1e 5n4Ol+PmGUNzV6aqmJVwDPZALnTtEvbd+avoD6v6N4vnmHmz5N+IBuujSzUmrpCZDw l8m09QHqaE7NDsWQ1m3Bs0PjPWniEVLWZCZC4jYP1wsgovVnDW1IDYO+nbEOFjt43z OafuSZjskWKxClwam76QWAaOnQfrNih7e5z+BOBN71TRiC/9F2lZry67Vc+t11BfAW RxMXo9xuRonwQ== Received: (nullmailer pid 1867798 invoked by uid 1000); Mon, 02 Oct 2023 16:10:24 -0000 Date: Mon, 2 Oct 2023 11:10:24 -0500 From: Rob Herring To: Chen-Yu Tsai Cc: Conor Dooley , linux-mediatek@lists.infradead.org, Lee Jones , Matthias Brugger , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Mark Brown , Zhiyong Tao , Krzysztof Kozlowski , AngeloGioacchino Del Regno , Rob Herring , devicetree@vger.kernel.org Subject: Re: [PATCH v4 02/12] regulator: dt-bindings: mt6358: Convert to DT schema Message-ID: <169626302358.1867415.15357334455488086427.robh@kernel.org> References: <20230928085537.3246669-1-wenst@chromium.org> <20230928085537.3246669-3-wenst@chromium.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230928085537.3246669-3-wenst@chromium.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 28 Sep 2023 16:55:25 +0800, Chen-Yu Tsai wrote: > Convert this from the old style text based binding to the new DT schema > style. This will make adding the MT6366 portion easier. > > The examples have been trimmed down considerably, and the remaining > entries now match what is seen in actual device trees, minus some > properties that aren't covered by the bindings yet, or don't make > sense on their own. > > The original submitter seems to have left MediaTek, so instead the > submitter and maintainer for the MT6366 binding is listed as the > maintainer here. > > Cc: Zhiyong Tao > Signed-off-by: Chen-Yu Tsai > --- > Changes since v3: > - ldo_vxo22 and ldo_vusb moved to properties > > Changes since v2: > - Added missing end-of-string match to regulator names > - regulator-coupled-* properties in example dropped > - #include and regulator-allowed-modes moved to new patch > > .../regulator/mediatek,mt6358-regulator.yaml | 98 +++++ > .../bindings/regulator/mt6358-regulator.txt | 350 ------------------ > 2 files changed, 98 insertions(+), 350 deletions(-) > create mode 100644 Documentation/devicetree/bindings/regulator/mediatek,mt6358-regulator.yaml > delete mode 100644 Documentation/devicetree/bindings/regulator/mt6358-regulator.txt > Reviewed-by: Rob Herring