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 4BF8EC77B6C for ; Fri, 31 Mar 2023 11:09:36 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231889AbjCaLJf (ORCPT ); Fri, 31 Mar 2023 07:09:35 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50092 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230429AbjCaLJR (ORCPT ); Fri, 31 Mar 2023 07:09:17 -0400 Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id AF9EF1D2CB for ; Fri, 31 Mar 2023 04:08:55 -0700 (PDT) Received: by mail-yb1-xb31.google.com with SMTP id b18so26956729ybp.1 for ; Fri, 31 Mar 2023 04:08:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20210112.gappssmtp.com; s=20210112; t=1680260935; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=DrZ4nuKFRbdrvkseheS7XRYqEh2EC/QvjKLix2jXZFM=; b=p8HE8uYDQXIMNWouHzNhuIPq4ZYpcpiB2tjtZuopwJd/AlYTllfvkZumoyD3e/aM7a Rsituuiso2kH/VdZb40vv8jtPdJNbYku8HkT1NxamcWm15rgUETuxgZWfce3K4OlsyJT 8EYq24i6h1AxbQKxcbsErcKtHV0SISL4sLOHWGtxxHXScAUsEopBmv6kXPUb2UP3kamx 7ejJ4g3jcDtINsK2lt0tIFmNU5xb6+K0y6cGos/6qAj9HGe3eQ9yrRkXgJxG1CWCQDv4 U50TBQ8X7/8T8XMPSnMernOOPbz8JoPb/BIhGLvpV6JYEt/IuIVi75EXyJsAZUXykI0w 2u1A== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1680260935; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=DrZ4nuKFRbdrvkseheS7XRYqEh2EC/QvjKLix2jXZFM=; b=SCYNDlL2bWgflUuLgYIgwR4LNC1ayGe5a6PEdeku5jL6S7EyTCTGoQgFnOQ0fcPzdm Tf6WIykkTyhRpqcZpalnjszeNe9P5GpgwImqvQ1TVr0iT1nT1tYrhNBzdxDGftuIoGRS NheuXcXXGOaCN8Tg3BnRLugQcOpK4/MiAuzEP01Vt2QVEs/S3jPxBmay9a4UBiqkLOwg TGf4rQxxzZ+bScpAdUnCuSjE1bCpMg5cmBxxM1wpe0Lu87s81otqAquM7OyiRzcsw9O4 67EGAoRif0XqXB8pNyiMg6pa76h3SZS4y+ujiZHlJfDHMZTZmnF4rnARlJp3yeuLYtm+ zqDA== X-Gm-Message-State: AAQBX9cAmrrYZNisc807iGX9U2QPhAdD7JRegAsd24BM6boiEMa50wEz WiJVYTkviEXnHMNG2xLopbD2/f/y/XoXpsAtPJNnZw== X-Google-Smtp-Source: AKy350bS9SyNRus3dGUyYtiJgys+HJA9rC8VrYDEuvi3iswc8ROzk0fLQpNKXYrIlL5r6jnukfZX+uNeYtTgRvFeeN4= X-Received: by 2002:a05:6902:18d5:b0:b75:3fd4:1b31 with SMTP id ck21-20020a05690218d500b00b753fd41b31mr18131967ybb.1.1680260934863; Fri, 31 Mar 2023 04:08:54 -0700 (PDT) MIME-Version: 1.0 References: <20230203-evk-board-support-v3-0-0003e80e0095@baylibre.com> <20230203-evk-board-support-v3-10-0003e80e0095@baylibre.com> <7b6be990-9e90-8e44-7c5e-f8b7a2701ce7@collabora.com> In-Reply-To: <7b6be990-9e90-8e44-7c5e-f8b7a2701ce7@collabora.com> From: Alexandre Mergnat Date: Fri, 31 Mar 2023 13:08:43 +0200 Message-ID: Subject: Re: [PATCH v3 10/17] arm64: dts: mediatek: set vmc regulator as always on To: AngeloGioacchino Del Regno Cc: Wim Van Sebroeck , Guenter Roeck , Rob Herring , Krzysztof Kozlowski , Matthias Brugger , Chaotian Jing , Ulf Hansson , Wenbin Mei , Linus Walleij , Zhiyong Tao , =?UTF-8?Q?Bernhard_Rosenkr=C3=A4nzer?= , linux-watchdog@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-mediatek@lists.infradead.org, linux-mmc@vger.kernel.org, linux-gpio@vger.kernel.org, Alexandre Bailon , Fabien Parent , Amjad Ouled-Ameur Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org Le mer. 29 mars 2023 =C3=A0 15:25, AngeloGioacchino Del Regno a =C3=A9crit : > > Il 29/03/23 10:54, amergnat@baylibre.com ha scritto: > > From: Fabien Parent > > > > MSDC1 IP block is powered by VMC. Make sure it is always on. > > Why always on? > Can't you just set mt6357_vmc_reg as VIN of mt6357_vmch_reg? :-) I'm not sure to get it. mt6357_vmc_reg & mt6357_vmch_reg come from PMIC and are supposed to be independent. You suggest to link them in the mt8365-evk dts file using something like: &mt6357_vmch_reg { vin-supply =3D <&mt6357_vmc_reg>; }; Also, regulator binding probably needs change to support that. Regards, Alex