From: Conor Dooley <conor@kernel.org>
To: Biju Das <biju.das.jz@bp.renesas.com>
Cc: Ulf Hansson <ulf.hansson@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
linux-mmc@vger.kernel.org, devicetree@vger.kernel.org,
linux-renesas-soc@vger.kernel.org,
Prabhakar Mahadev Lad <prabhakar.mahadev-lad.rj@bp.renesas.com>,
Biju Das <biju.das.au@gmail.com>
Subject: Re: [PATCH v2 1/8] dt-bindings: mmc: renesas,sdhi: Document RZ/G3E support
Date: Fri, 31 Jan 2025 17:17:35 +0000 [thread overview]
Message-ID: <20250131-dangle-obtain-30ffa8a44083@spud> (raw)
In-Reply-To: <20250131112429.119882-2-biju.das.jz@bp.renesas.com>
[-- Attachment #1: Type: text/plain, Size: 763 bytes --]
On Fri, Jan 31, 2025 at 11:24:16AM +0000, Biju Das wrote:
> The SD/MMC block on the RZ/G3E ("R9A09G047") SoC is similar to that
> of the RZ/V2H, but the SD0 channel has only dedicated pins, so we must
> use SD_STATUS register to control voltage and power enable (internal
> regulator), for non-fixed voltage (SD) MMC interface. However, it is
> optional for fixed voltage MMC interface (eMMC).
>
> For SD1 and SD2 channels, we can either use gpio regulator or internal
> regulator (using SD_STATUS register) for voltage switching.
>
> Document RZ/G3E SDHI IP support with optional internal regulator for
> both RZ/G3E and RZ/V2H SoC.
>
> Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com>
Acked-by: Conor Dooley <conor.dooley@microchip.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2025-01-31 17:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 11:24 [PATCH v2 0/8] Add RZ/G3E SDHI support Biju Das
2025-01-31 11:24 ` [PATCH v2 1/8] dt-bindings: mmc: renesas,sdhi: Document RZ/G3E support Biju Das
2025-01-31 17:17 ` Conor Dooley [this message]
2025-02-06 8:47 ` Geert Uytterhoeven
2025-01-31 11:24 ` [PATCH v2 4/8] arm64: dts: renesas: r9a09g047: Add SDHI0-SDHI2 nodes Biju Das
2025-02-05 8:16 ` Geert Uytterhoeven
2025-02-05 9:19 ` Biju Das
2025-01-31 11:24 ` [PATCH v2 6/8] arm64: dts: renesas: rzg3e-smarc-som: Enable SDHI{0,2} Biju Das
2025-02-06 9:35 ` Geert Uytterhoeven
2025-02-06 9:47 ` Biju Das
2025-02-06 9:52 ` Geert Uytterhoeven
2025-02-06 11:07 ` Biju Das
2025-02-06 9:48 ` Geert Uytterhoeven
2025-02-06 11:06 ` Biju Das
2025-01-31 11:24 ` [PATCH v2 7/8] arm64: dts: renesas: rzg3e-smarc-som: Add support for enable SD on SDHI0 Biju Das
2025-02-06 9:47 ` Geert Uytterhoeven
2025-02-06 10:58 ` Biju Das
2025-01-31 11:24 ` [PATCH v2 8/8] arm64: dts: renesas: r9a09g047e57-smarc: Enable SDHI1 Biju Das
2025-02-06 10:04 ` Geert Uytterhoeven
2025-02-06 11:08 ` Biju Das
2025-02-06 8:50 ` [PATCH v2 0/8] Add RZ/G3E SDHI support Geert Uytterhoeven
2025-02-06 9:26 ` Biju Das
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=20250131-dangle-obtain-30ffa8a44083@spud \
--to=conor@kernel.org \
--cc=biju.das.au@gmail.com \
--cc=biju.das.jz@bp.renesas.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=krzk+dt@kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=prabhakar.mahadev-lad.rj@bp.renesas.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
/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