Received: by 2002:a25:d7c1:0:0:0:0:0 with SMTP id o184csp459077ybg; Sat, 26 Oct 2019 01:16:24 -0700 (PDT) X-Google-Smtp-Source: APXvYqxJhbkYDWwiB0wsld0nsl8yARGVeeHe+WgiNxatv8MDACwLK7/5Zjff0ytlGTQplLgV4Jxc X-Received: by 2002:a50:b6e1:: with SMTP id f30mr8383542ede.212.1572077784886; Sat, 26 Oct 2019 01:16:24 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1572077784; cv=none; d=google.com; s=arc-20160816; b=VSWTprdKyqclvDzfgCi9KJgyu3EhDGzcAXe/Ka/ItP4L0o8/Ec8NDEgDm9zFWmxMt1 XGYtFfuWkKxp8b1+63eNOwbHPln/UGuL9GLL4tVPWKsqOqC/9UEd7f/E1dHpdwU+x0Pj FI01X8ChEKYE4m6Fa5a+3c85ItYi4MtfNIt/8dwCFll/Y1MKMJLG2qLBfwCWOdfl8X9j /t8NQ6bdRMFFcuojo2TCDfvQex1fdNvYDcuPfkiznJhmHkFt2M8DJRfNpU13R49pvErb lk4RQBPWY0Vlnzr0SH+NWMukkob8dBJnZW6LqpBSHAF8RmokaO6QqrWjtg9zSgrfQmX6 4mZg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=UJkZcqFkwy4TKntXC8AAm0UWkBOApptiJzBK415CJ9Q=; b=wFX0A8qxn8fp9bcxEL+nPElri6vBSESBU6bayR39N1HR5iHIglGZa2uKHWtsQ8wXEA b9QGT3b7kqFS9HsxlJ554G1GzddQBvjK3tmRmQ5MrszXo/CW611pQZSkFP+5u7TymFrl mPIruJ3JvgIXBmLrFLbGzGzCorVemn2lV7Pg8raRbxXMvQYT/LdwgdEm9Nkt0/u7QWaC 0YUmyzaDwU0EZ1avvBy3P7R3youbLljD+IToh9BV9DshuGjkIXR4P++cUAszdSWhLQhL YWmI1xCKgmu3aYqyEXYAb1qWWnF/8W1Y/9duVSTfP2izHeYAdxpBTH5pUOORaAb9Zhlz FHfg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wRieEcbL; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id mj11si46352ejb.140.2019.10.26.01.16.01; Sat, 26 Oct 2019 01:16:24 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=wRieEcbL; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726115AbfJZIMg (ORCPT + 99 others); Sat, 26 Oct 2019 04:12:36 -0400 Received: from mail.kernel.org ([198.145.29.99]:59056 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725996AbfJZIMf (ORCPT ); Sat, 26 Oct 2019 04:12:35 -0400 Received: from dragon (98.142.130.235.16clouds.com [98.142.130.235]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id BBBD6214DA; Sat, 26 Oct 2019 08:12:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1572077555; bh=uLrgR5dduFiKpCf2zS/LUfYO4qdcUR5sKFqtU9Ua3Xc=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=wRieEcbL9aSAvlkBKLiSjJvhvYjxTr7M/1F5X6n/1gwJb+4tm0rqZjlUNkmpTYBzR FSfVZf99PGNvd9h8CuatnG7fM6hyTPAc7Ab4mtZ1aUCi/aDRCTrxz7Up34ZLFBifko asjSu+zFgko2TZlDVN1OZjhZ57/BCAurusF6BDVs= Date: Sat, 26 Oct 2019 16:12:15 +0800 From: Shawn Guo To: Andreas Kemnade Cc: robh+dt@kernel.org, mark.rutland@arm.com, s.hauer@pengutronix.de, kernel@pengutronix.de, festevam@gmail.com, linux-imx@nxp.com, manivannan.sadhasivam@linaro.org, andrew.smirnov@gmail.com, marex@denx.de, angus@akkea.ca, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org, j.neuschaefer@gmx.net, Discussions about the Letux Kernel , Marco Felsch Subject: Re: [PATCH v3 3/3] ARM: dts: imx: add devicetree for Kobo Clara HD Message-ID: <20191026081214.GB14401@dragon> References: <20191010192357.27884-1-andreas@kemnade.info> <20191010192357.27884-4-andreas@kemnade.info> <20191025134621.GN3208@dragon> <20191025200743.48455cc9@aktux> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20191025200743.48455cc9@aktux> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 25, 2019 at 08:07:43PM +0200, Andreas Kemnade wrote: > Hi, > > On Fri, 25 Oct 2019 21:46:24 +0800 > Shawn Guo wrote: > > [...] > > > + > > > + pinctrl_wifi_reset: wifi_reset_grp { > > > + fsl,pins = < > > > + MX6SLL_PAD_SD2_DATA7__GPIO5_IO00 0x10059 /* WIFI_RST */ > > > + >; > > > + }; > > > + > > > + pinctrl_wifi_power: wifi_power_grp { > > > > I guess you can have one pinctrl node to include both reset and power > > pins? Also, to be consistent with other pinctrl nodes on naming, the > > node name should probably be wifigrp. > > > well, the problems they are used in different nodes, so I cannot do > that: > > reg_wifi: regulator-wifi { > compatible = "regulator-fixed"; > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_wifi_power>; > regulator-name = "SD3_SPWR"; > regulator-min-microvolt = <3000000>; > regulator-max-microvolt = <3000000>; > gpio = <&gpio4 29 GPIO_ACTIVE_HIGH>; > enable-active-high; > }; > > wifi_pwrseq: wifi_pwrseq { > compatible = "mmc-pwrseq-simple"; > pinctrl-names = "default"; > pinctrl-0 = <&pinctrl_wifi_reset>; > post-power-on-delay-ms = <20>; > reset-gpios = <&gpio5 0 GPIO_ACTIVE_LOW>; > }; Ah, yes, it makes more sense. I missed that. Shawn > > So having them combined breaks the mux where you use it rule. > I got in earlier mails: > > > > + wifi_pwrseq: wifi_pwrseq { > > > + compatible = "mmc-pwrseq-simple"; > > > + post-power-on-delay-ms = <20>; > > > + reset-gpios = <&gpio5 0 GPIO_ACTIVE_LOW>; > > > Can you add a pinctrl-entry here please? The general rule is to mux > > things where you use it > [...] > > > + compatible = "regulator-fixed"; > > > + regulator-name = "SD3_SPWR"; > > > + regulator-min-microvolt = <3000000>; > > > + regulator-max-microvolt = <3000000>; > > > + > > > + gpio = <&gpio4 29 GPIO_ACTIVE_HIGH>; > > > Please add a pinctrl here to mux this gpio. > > Regards, > Andreas