linux-kernel - RE: [PATCH v4 3/3] mmc: renesas_sdhi: Add support for RZ/V2H(P) SoC

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID:
 <TY3PR01MB113468B2E0C2591024A7933CE86DD2@TY3PR01MB11346.jpnprd01.prod.outlook.com>
Date: Wed, 3 Jul 2024 11:11:30 +0000
From: Biju Das <biju.das.jz@...renesas.com>
To: Wolfram Sang <wsa+renesas@...g-engineering.com>
CC: Prabhakar <prabhakar.csengg@...il.com>, Ulf Hansson
	<ulf.hansson@...aro.org>, Geert Uytterhoeven <geert+renesas@...der.be>, Rob
 Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor
 Dooley <conor+dt@...nel.org>, Magnus Damm <magnus.damm@...il.com>,
	"linux-mmc@...r.kernel.org" <linux-mmc@...r.kernel.org>,
	"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	"linux-renesas-soc@...r.kernel.org" <linux-renesas-soc@...r.kernel.org>,
	Fabrizio Castro <fabrizio.castro.jz@...esas.com>, Prabhakar Mahadev Lad
	<prabhakar.mahadev-lad.rj@...renesas.com>, Claudiu Beznea
	<claudiu.beznea.uj@...renesas.com>
Subject: RE: [PATCH v4 3/3] mmc: renesas_sdhi: Add support for RZ/V2H(P) SoC

Hi Wolfram,

Thanks for the feedback.

> -----Original Message-----
> From: Wolfram Sang <wsa+renesas@...g-engineering.com>
> Sent: Wednesday, July 3, 2024 10:36 AM
> Subject: Re: [PATCH v4 3/3] mmc: renesas_sdhi: Add support for RZ/V2H(P) SoC
> 
> 
> > If I understand correctly,
> > VMMC(Always on 3.3V) for card detection -->PWEN pin
> > Vqmmc(1.8v-3.3V) for UHS operation for voltage switch-->IOVS pin
> 
> If these assumptions are correct, then I am sorry to have missed it. I thougaht PWEN is for vqmmc.

The assumptions are correct. PWEN is basically vmmc, which needs to be on always for 
the card detection.

> If it is not, then we need two regulators, one for vmmc and one for vqmmc. This is what the TMIO core
> expects and already handles correctly on its own, or? Except for the reset handling where we need to
> preserve some value in the SDHI core.

Yes, probably for PWEN, vmmc regulator with "always on" and "boot on" property enabled in regulator node.
So that it will be always on.

Cheers,
Biju