From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail.zeus03.de (zeus03.de [194.117.254.33]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 32EB5389DEB for ; Wed, 4 Feb 2026 15:47:04 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=194.117.254.33 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770220025; cv=none; b=ceEVpTXqIlxKrrjejRz3PzR+n8xM9ltCKG1hoGyURkLhmteTngxlLUBQFp+ULh8soUQM47nG+eIE8fe/NWrYqAoWboCgV65vYnkUVD9tHCshQcgNdHYM0vspHJcuaOkfYLiDflOAjaSt2XJ10jFkGt10hbfhpGnDhB5dZhvgBIM= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770220025; c=relaxed/simple; bh=NhBMhptCDXkwpcXyoAjy4paUP5kVjoY/noDcDnftIxM=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=ILFUhN+pnImh+cqCWX0f+idxY8pkd+lmB3r62X5lEJHOg5d9tkY/6yugQ3+4tw9kNo4usHb3J+KpyCAbt6i6TmjqyWjIco+KcG/nzyEavcM5IdVD38m5s9eAvzMENTQm7rYpV0L55D4oDeMh39zv3YfpkgZhyLyBaBGYRakttsU= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com; spf=pass smtp.mailfrom=sang-engineering.com; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b=mVzufcXf; arc=none smtp.client-ip=194.117.254.33 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=sang-engineering.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=sang-engineering.com header.i=@sang-engineering.com header.b="mVzufcXf" DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= sang-engineering.com; h=date:from:to:cc:subject:message-id :references:mime-version:content-type:in-reply-to; s=k1; bh=9pjd 1Z0abUIs/vb7jSYDYMKbNGzdvIiPE6k3qOxN4n0=; b=mVzufcXf2pCcfgow2H4I 4WfypG+vvaw0CzCW++E6pTpghodG+FWoDs6BVs6KJ0S5ax+QoUq9WKejdXaFgdDC zLja6YCEkfnadgfeB1VGSe2SCvda7B7N7i2L8+ThOPWO9qFK20FjQCcWYDFmzdBC 20U6oQTvaFskSjER5kpMuCM4lZEjNlShSfl00FqW0aiQcE2/I0pnskekj+3kXGSG 4vayQRhLxRv0jJveM/536o64o1xRf/RQb4L8pfKRfs7W9BdcEh6qNzsELNadNr4O XcQcEjfYwfip0kGKCO/okuRxMzt2MGQVFxckDlBloIeyrt5bstYIvkkuhSTgNxB3 cg== Received: (qmail 2418933 invoked from network); 4 Feb 2026 16:47:02 +0100 Received: by mail.zeus03.de with UTF8SMTPSA (TLS_AES_256_GCM_SHA384 encrypted, authenticated); 4 Feb 2026 16:47:02 +0100 X-UD-Smtp-Session: l3s3148p1@UtCVdwFKnOkqAAAQagvIAoH29ntsUY5F Date: Wed, 4 Feb 2026 16:47:01 +0100 From: Wolfram Sang To: Josua Mayer Cc: Marc Kleine-Budde , Vincent Mailhol , Vinod Koul , Neil Armstrong , Peter Rosin , Aaro Koskinen , Andreas Kemnade , Kevin Hilman , Roger Quadros , Tony Lindgren , Janusz Krzysztofik , Vignesh R , Andi Shyti , Ulf Hansson , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Geert Uytterhoeven , Magnus Damm , Yazan Shhady , Jon Nettleton , Mikhail Anikin , linux-can@vger.kernel.org, linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, linux-i2c@vger.kernel.org, linux-mmc@vger.kernel.org, devicetree@vger.kernel.org, linux-renesas-soc@vger.kernel.org Subject: Re: [PATCH v8 7/7] mmc: host: renesas_sdhi_core: support selecting an optional mux Message-ID: References: <20260203-rz-sdio-mux-v8-0-024ea405863e@solid-run.com> <20260203-rz-sdio-mux-v8-7-024ea405863e@solid-run.com> Precedence: bulk X-Mailing-List: linux-mmc@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260203-rz-sdio-mux-v8-7-024ea405863e@solid-run.com> On Tue, Feb 03, 2026 at 03:01:40PM +0200, Josua Mayer wrote: > Some hardware designs route data or control signals through a mux to > support multiple devices on a single sdhi controller. > > In particular SolidRun RZ/G2L/G2LC/V2L System on Module use a mux for > switching between soldered eMMC and an optional microSD on a carrier > board, e.g. for development or provisioning. > > SD/SDIO/eMMC are not well suited for runtime switching between different > cards, however boot-time selection is possible and useful - in > particular considering dt overlays. > > Add support for an optional SD/SDIO/eMMC mux defined in dt, and select > it during probe. > > Similar functionality already exists in other places, e.g. i2c-omap. > > Reviewed-by: Geert Uytterhoeven > Signed-off-by: Josua Mayer And to confirm the obvious, no regression found on a Renesas SparrowHawk (R-Car V4H) not using muxes: Tested-by: Wolfram Sang