From: Josua Mayer <josua@solid-run.com>
To: Conor Dooley <conor@kernel.org>
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>,
Mikhail Anikin <mikhail.anikin@solid-run.com>,
Yazan Shhady <yazan.shhady@solid-run.com>,
Jon Nettleton <jon@solid-run.com>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: Re: [PATCH 1/2] dt-bindings: mmc: renesas,sdhi: Add mux-states property
Date: Mon, 1 Dec 2025 12:01:12 +0000 [thread overview]
Message-ID: <6a392466-3aa3-49df-b96c-de2d272fca18@solid-run.com> (raw)
In-Reply-To: <20251128-strongbox-craziness-cea572479d17@spud>
Am 28.11.25 um 19:49 schrieb Conor Dooley:
> On Fri, Nov 28, 2025 at 05:15:38PM +0100, Josua Mayer wrote:
>> Add mux controller support for when sdio lines are muxed between a host
>> and multiple cards.
>>
>> There are several devices supporting a choice of eMMC or SD on a single
>> board by both dip switch and gpio, e.g. Renesas RZ/G2L SMARC SoM and
>> SolidRun RZ/G2L SoM.
>>
>> In-tree dts for the Renesas boards currently rely on preprocessor macros
>> to hog gpios and define the card.
>>
>> By adding mux-states property to sdio controller description, boards can
>> correctly describe the mux that already exists in hardware - and drivers
>> can coordinate between mux selection and probing for cards.
>>
>> Signed-off-by: Josua Mayer <josua@solid-run.com>
>> ---
>> Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml | 14 ++++++++++++++
>> 1 file changed, 14 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml b/Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml
>> index c754ea71f51f7..55635c60ad73a 100644
>> --- a/Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml
>> +++ b/Documentation/devicetree/bindings/mmc/renesas,sdhi.yaml
>> @@ -106,6 +106,11 @@ properties:
>> iommus:
>> maxItems: 1
>>
>> + mux-states:
>> + description:
>> + mux controller node to route the SDIO signals from SoC to cards.
>> + maxItems: 1
>> +
>> power-domains:
>> maxItems: 1
>>
>> @@ -262,9 +267,17 @@ unevaluatedProperties: false
>> examples:
>> - |
>> #include <dt-bindings/clock/r8a7790-cpg-mssr.h>
>> + #include <dt-bindings/gpio/gpio.h>
>> #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/pinctrl/rzg2l-pinctrl.h>
>> #include <dt-bindings/power/r8a7790-sysc.h>
>>
>> + mux: mux-controller {
>> + compatible = "gpio-mux";
>> + #mux-state-cells = <1>;
>> + mux-gpios = <&pinctrl RZG2L_GPIO(22, 1) GPIO_ACTIVE_LOW>;
>> + };
> This node should be removed, the tooling will provide a fake phandle to
> satisfy your mux-states property.
Will drop, thanks!
>
> pw-bot: changes-requested
>
>> +
>> sdhi0: mmc@ee100000 {
>> compatible = "renesas,sdhi-r8a7790", "renesas,rcar-gen2-sdhi";
>> reg = <0xee100000 0x328>;
>> @@ -275,6 +288,7 @@ examples:
>> max-frequency = <195000000>;
>> power-domains = <&sysc R8A7790_PD_ALWAYS_ON>;
>> resets = <&cpg 314>;
>> + mux-states = <&mux 0>;
>> };
>>
>> sdhi1: mmc@ee120000 {
>>
>> --
>> 2.51.0
>>
next prev parent reply other threads:[~2025-12-01 12:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 16:15 [PATCH 0/2] mmc: host: renesas_sdhi_core: support configuring an optional sdio mux Josua Mayer
2025-11-28 16:15 ` [PATCH 1/2] dt-bindings: mmc: renesas,sdhi: Add mux-states property Josua Mayer
2025-11-28 18:49 ` Conor Dooley
2025-12-01 12:01 ` Josua Mayer [this message]
2025-11-30 8:22 ` Krzysztof Kozlowski
2025-12-01 12:02 ` Josua Mayer
2025-11-28 16:15 ` [PATCH 2/2] mmc: host: renesas_sdhi_core: support configuring an optional sdio mux Josua Mayer
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=6a392466-3aa3-49df-b96c-de2d272fca18@solid-run.com \
--to=josua@solid-run.com \
--cc=conor+dt@kernel.org \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=jon@solid-run.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=mikhail.anikin@solid-run.com \
--cc=robh@kernel.org \
--cc=ulf.hansson@linaro.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yazan.shhady@solid-run.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