Linux Watchdog driver development
 help / color / mirror / Atom feed
From: AngeloGioacchino Del Regno  <angelogioacchino.delregno@collabora.com>
To: amergnat@baylibre.com, Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Wim Van Sebroeck <wim@linux-watchdog.org>,
	Guenter Roeck <linux@roeck-us.net>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, linux-watchdog@vger.kernel.org,
	devicetree@vger.kernel.org, linux-mediatek@lists.infradead.org,
	Fabien Parent <fparent@baylibre.com>,
	Kevin Hilman <khilman@baylibre.com>
Subject: Re: [PATCH v7 06/11] arm64: dts: mediatek: set vmc regulator as always on
Date: Mon, 15 May 2023 13:44:24 +0200	[thread overview]
Message-ID: <ff7292f0-9055-1787-2543-e219fe30dddf@collabora.com> (raw)
In-Reply-To: <20230203-evk-board-support-v7-6-98cbdfac656e@baylibre.com>

Il 11/05/23 18:29, amergnat@baylibre.com ha scritto:
> From: Fabien Parent <fparent@baylibre.com>
> 
> On downstream, we observe that the MSDC IP (used by the emmc, the micro
> SD card and the WiFi) isn't working properly if the VMC regulator is
> shutdown.
> 
> Make sure it is always on.

I don't understand the power tree of this board: if your VQMMC is VIO18 and
*not* VMC, why is that required?

The real question is if we're facing one more supply as requirement for newer
MediaTek SoCs and whether it would be a better idea to add that to the actual
driver (and/or as a power domain supply!!!) to both better represent the power
tree and to eventually allow deep power saving states.

Regards,
Angelo

> 
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
> Tested-by: Kevin Hilman <khilman@baylibre.com>
> Signed-off-by: Alexandre Mergnat <amergnat@baylibre.com>
> ---
>   arch/arm64/boot/dts/mediatek/mt8365-evk.dts | 5 +++++
>   1 file changed, 5 insertions(+)
> 
> diff --git a/arch/arm64/boot/dts/mediatek/mt8365-evk.dts b/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> index 752007d0598e..5d69b39c8746 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> +++ b/arch/arm64/boot/dts/mediatek/mt8365-evk.dts
> @@ -137,6 +137,11 @@ &mt6357_pmic {
>   	#interrupt-cells = <2>;
>   };
>   
> +/* Needed by MSDC IP */
> +&mt6357_vmc_reg {
> +	regulator-always-on;
> +};
> +
>   &pio {
>   	gpio_keys: gpio-keys-pins {
>   		pins {
> 



  reply	other threads:[~2023-05-15 11:55 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-11 16:29 [PATCH v7 00/11] Improve the MT8365 SoC and EVK board support Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 01/11] arm64: defconfig: enable MT6357 regulator Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 02/11] arm64: defconfig: enable Mediatek PMIC key Alexandre Mergnat
2023-05-15 11:35   ` AngeloGioacchino Del Regno
2023-05-11 16:29 ` [PATCH v7 03/11] arm64: dts: mediatek: add watchdog support for mt8365 SoC Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 04/11] arm64: dts: mediatek: add mt6357 PMIC support for mt8365-evk Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 05/11] arm64: dts: mediatek: add mmc " Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 06/11] arm64: dts: mediatek: set vmc regulator as always on amergnat
2023-05-15 11:44   ` AngeloGioacchino Del Regno [this message]
2023-05-22 14:24     ` Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 07/11] arm64: dts: mediatek: add usb controller support for mt8365-evk Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 08/11] arm64: dts: mediatek: add ethernet " Alexandre Mergnat
2023-05-15 11:47   ` AngeloGioacchino Del Regno
2023-05-22 14:23     ` Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 09/11] arm64: dts: mediatek: add OPP support for mt8365 SoC Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 10/11] arm64: dts: mediatek: add cpufreq support for mt8365-evk Alexandre Mergnat
2023-05-11 16:29 ` [PATCH v7 11/11] arm64: dts: mediatek: Add CPU Idle support amergnat

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=ff7292f0-9055-1787-2543-e219fe30dddf@collabora.com \
    --to=angelogioacchino.delregno@collabora.com \
    --cc=amergnat@baylibre.com \
    --cc=catalin.marinas@arm.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fparent@baylibre.com \
    --cc=khilman@baylibre.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=linux-watchdog@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=matthias.bgg@gmail.com \
    --cc=robh+dt@kernel.org \
    --cc=will@kernel.org \
    --cc=wim@linux-watchdog.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox