Received: by 2002:a05:6a11:4021:0:0:0:0 with SMTP id ky33csp510780pxb; Tue, 14 Sep 2021 02:42:39 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzauRbmIN8Tkj8qZlK+0CEcA8+Zn2Bt292NCw2YncJQM0BjY7h/vnSvHsBIf4JRdIY/9BUL X-Received: by 2002:a17:906:2ac1:: with SMTP id m1mr17586890eje.518.1631612559139; Tue, 14 Sep 2021 02:42:39 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1631612559; cv=none; d=google.com; s=arc-20160816; b=SprKfXobHYESluKmcH5IlCybHh5vzcH3MqEr8ZogzFfQGeLyIsxMSw1+DIG1kZ57dA EUJ0q6eyS+73QUtxMI9kSn51yVmIQU9wgM+L3MjDhCzwsrqcPWr0p3iYsjNabnxL0DLD oLR4sdx/rC/VQp2rzWX7nbUNH4nawHtyEOQqjuB5PoBWbYl1iluAuayjBYcfHNwQynyP kTG39QtU5hjqZ2WV9Iqn4rRpzLTbSrIVBxtlGu+HUvy1/l8KH3ahqECW10nK04+Ybjfe 2KQzcpw/m1ihSNao4gjNtDDu28sjztP4sqLeeOhLSHe0qG2g3GddIbP06ITQQFYb7L1T yqCg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:message-id:user-agent:references:in-reply-to :subject:cc:to:from:date:content-transfer-encoding:mime-version :dkim-signature; bh=z6Mv7Yd2Rs+noRI7tvkJjhObNXbkREoufLm5c9rZxBE=; b=ggos8hADX0aa49K3FK2N7i5qjeUb0a4SQ3yYN5KvIH1+0Jp75c+80O8bByzI1rnCJ7 j9ShulkSbH1b22M2iyM+IUneU7raL1aRp3fE4HZtcPsGWOGuWcztxuSaJuAatrP5On3c PJ63OVQdQ4VvAcbliq1csGLMoFRBHYkISPBrTKcRAT0+7dY0rNXTyzKVQtyuYv2qE4Th F28AQjwKrJzj47Qw8v1LnHgXejHizU4YdRYFbJbcZ2rrXC3JR2YjAlZ4FgDcfBQxXov/ QMu3lxxF31b/IrrEy9YHNQvcERmPczAxGAaCATwXOkWtClo2pBvAFWZ4RElOB3F/ozys O7vA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b="Lu5Wwd/6"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id go17si9771514ejc.354.2021.09.14.02.42.15; Tue, 14 Sep 2021 02:42:39 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@walle.cc header.s=mail2016061301 header.b="Lu5Wwd/6"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229969AbhINJlK (ORCPT + 99 others); Tue, 14 Sep 2021 05:41:10 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:55004 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229560AbhINJlJ (ORCPT ); Tue, 14 Sep 2021 05:41:09 -0400 Received: from ssl.serverraum.org (ssl.serverraum.org [IPv6:2a01:4f8:151:8464::1:2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BE32CC061574; Tue, 14 Sep 2021 02:39:52 -0700 (PDT) Received: from ssl.serverraum.org (web.serverraum.org [172.16.0.2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ssl.serverraum.org (Postfix) with ESMTPSA id 18BD822236; Tue, 14 Sep 2021 11:39:51 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=walle.cc; s=mail2016061301; t=1631612391; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=z6Mv7Yd2Rs+noRI7tvkJjhObNXbkREoufLm5c9rZxBE=; b=Lu5Wwd/6hGrxKxmtOC5tSHcoTRCF4pVt00VJvSOsgnhOyKpKCFTUbF7YcReCBnyVuo2tu6 rEDAIsAU6ct2ilQqsFWPHeLfAy82reU0NdQ4wyUsj9xK37eURBef/LCI6SN4EDuj/w6pXk zOIHkizNrgnCzvHO7BohAgMfcCJKFkM= MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII; format=flowed Content-Transfer-Encoding: 7bit Date: Tue, 14 Sep 2021 11:39:51 +0200 From: Michael Walle To: Lucas Stach Cc: Heiko Thiery , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Fabio Estevam , Shengjiu Wang , Joakim Zhang , Krzysztof Kozlowski , Rob Herring , NXP Linux Team , Pengutronix Kernel Team , Shawn Guo , Sascha Hauer Subject: Re: [PATCH v2] arm64: dts: imx8mq-kontron-pitx-imx8m: remove vqmmc-supply node In-Reply-To: <2dc72116ec935a5a5d7a1a176868b7af7ff3227c.camel@pengutronix.de> References: <20210914072627.24173-1-heiko.thiery@gmail.com> <449f718706fd5af03190bdda986de37aa8fa14e3.camel@pengutronix.de> <79fb60ea9a002ea553a92ea08b28b866@walle.cc> <2dc72116ec935a5a5d7a1a176868b7af7ff3227c.camel@pengutronix.de> User-Agent: Roundcube Webmail/1.4.11 Message-ID: <9c4ada4b9ca1e806ea1916f195598b40@walle.cc> X-Sender: michael@walle.cc Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Am 2021-09-14 10:52, schrieb Lucas Stach: > Am Dienstag, dem 14.09.2021 um 10:32 +0200 schrieb Michael Walle: >> Hi Lucas, >> >> Am 2021-09-14 10:20, schrieb Lucas Stach: >> > Am Dienstag, dem 14.09.2021 um 09:26 +0200 schrieb Heiko Thiery: >> > > The sw4 output (V_1V8_S0 voltage) from the PMIC is the main supply for >> > > the 1V8 power domain. It is not only used as supply for the eMMC. >> > > So this voltage can not be changed and is not allowed to switched off. >> > > Therefore we do not want to provide this regulator to the SDHC driver >> > > to >> > > control this voltage. >> > > >> > This specific requirement should not be solved by removing the >> > regulator connection from the SDHCI node, but instead by constraining >> > the regulator voltage range to a fixed 3.3V and marking the regulator >> > as always-on to reflect the hardware requirements in the DT. >> > >> > Also if your eMMC vqmmc is a fixed 3.3V, I don't think you need the >> > faster pinctrl states, as you can't use the faster pin states anyways, >> > as they require a 1.8V signaling voltage. >> >> Are you speaking of the 1.8V signalling modes? As far as I know the >> IMX SDHC controller will switch the voltage by its own function pin. >> That is, its not a GPIO. > > Ah, I mixed things up here. This is a fixed 1.8V supply, which is valid > for eMMC, so the high-speed modes are available. My comment still > applies that this should be fixed by constraining the regulator, not by > removing the DT connection. > > vqmmc is the MMC IO voltage, which can be switched either by the > function pin, which gets toggled automatically when software does the > voltage switch, or by explicitly switching the regulator voltage. eMMCs > are a bit special as they can work with a fixed 1.8V IO supply and > don't need to start with 3.3V. Mh, I have some kind of general question though. Lets take the SDHC controller for the SD card, which needs to change the voltage if you want to use the high speed mode of the cards. Ie. from 3.3V to 1.8V. The controller does this autonomously with the help of a pin which is controlled by the controller itself. Will it have a vqmmc-supply property? And if so what whould the supply be? -michael