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 63651CE7B19 for ; Thu, 28 Sep 2023 10:25:54 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231276AbjI1KZx (ORCPT ); Thu, 28 Sep 2023 06:25:53 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:42594 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231148AbjI1KZu (ORCPT ); Thu, 28 Sep 2023 06:25:50 -0400 Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7EDCB195; Thu, 28 Sep 2023 03:25:48 -0700 (PDT) Received: from [192.168.1.100] (2-237-20-237.ip236.fastwebnet.it [2.237.20.237]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits)) (No client certificate requested) (Authenticated sender: kholk11) by madras.collabora.co.uk (Postfix) with ESMTPSA id 1B6AF6607330; Thu, 28 Sep 2023 11:25:46 +0100 (BST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com; s=mail; t=1695896746; bh=RCSdUR/osdkCB5Bl2WmbzxTRoja3hNKs1eu4r3gAs2E=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=DVXch+pbyJerTappMmJKe1mDPwvj3brTBhUrdK3j9xVX1QbSVO57F1gmBQ2vvtxnB ewY9aexnBFY82dLg+e/w/nnQ1Vcg7TNsr5G64HhqIGh+CkPxDchtYoZXT3ediAQiYJ KI2wXZrr5vRsPsJpkHknhoE0gj62ZxP56aK0lBAGCvqS6RKMdp0iaSETktc+tixi0v Z0rAAf8RGVus7HptjBDH8oFVMarFgQ4bUzahTg6uMokJ5i1ptmDxiMX0kLxive1if1 RCjWC5O7D3n+oHZrCV2iBrg94ypVwgtd7wBMSDLk3IHP5w17sb/j8OZh0e1ywqOAz+ ALdVsk7oXLh5Q== Message-ID: <58a7d962-bfa7-ac1d-a324-c78a03b6835d@collabora.com> Date: Thu, 28 Sep 2023 12:25:43 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.15.0 Subject: Re: [PATCH v4 01/12] dt-bindings: mfd: mt6397: Split out compatible for MediaTek MT6366 PMIC Content-Language: en-US To: Chen-Yu Tsai , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Matthias Brugger , Mark Brown Cc: Lee Jones , Zhiyong Tao , devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, Krzysztof Kozlowski References: <20230928085537.3246669-1-wenst@chromium.org> <20230928085537.3246669-2-wenst@chromium.org> From: AngeloGioacchino Del Regno In-Reply-To: <20230928085537.3246669-2-wenst@chromium.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Il 28/09/23 10:55, Chen-Yu Tsai ha scritto: > The MT6366 PMIC is mostly, but not fully, compatible with MT6358. It has > a different set of regulators. Specifically, it lacks the camera related > VCAM* LDOs and VLDO28, but has additional VM18, VMDDR, and VSRAM_CORE LDOs. > > The PMICs contain a chip ID register that can be used to detect which > exact model is preset, so it is possible to share a common base > compatible string. > > Add a separate compatible for the MT6366 PMIC, with a fallback to the > MT6358 PMIC. > > Fixes: 49be16305587 ("dt-bindings: mfd: Add compatible for the MediaTek MT6366 PMIC") > Signed-off-by: Chen-Yu Tsai > Acked-by: Krzysztof Kozlowski Reviewed-by: AngeloGioacchino Del Regno