Received: by 2002:a05:6a10:206:0:0:0:0 with SMTP id 6csp4237585pxj; Wed, 12 May 2021 00:43:30 -0700 (PDT) X-Google-Smtp-Source: ABdhPJyIf6XehpS+n0vJQhWMd3CgiliN5++8mDsUIu2FC/68FLP8YMmGU6437Dyal3W7y71lCn7b X-Received: by 2002:a92:d903:: with SMTP id s3mr4206250iln.140.1620805410384; Wed, 12 May 2021 00:43:30 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1620805410; cv=none; d=google.com; s=arc-20160816; b=DiZPF87woQaCzc5Rgvyi9bNFfOVRoXaWoPGVUZVAmxwaVUSWSt75ObtIv5LnhY19AI a/JqO95GoRrNdBLX5Qrb5H8kTFyRfuAJluT8qddxbYcv6steNsPPj7bWFkhZ/LU91d/i uM7XPMI528O20zImXB6jimEnqtV/e3/fDo1RfQLzq2yZT8bSCzWc0ao+iIhK0KtUZPxZ YqBNdTJsPs5gmftdgjHnylWvNDM/lHOQIgMs7tYntjgFQuJJhhpKhqUNWQo5vbEXBZpc O8SM/0Zu8ucCZI4MhmOxW08Rvk26fKLvDB4AODYias39wb3ZtByfMnsibWU4VWKPOQAo /jDA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:content-language :in-reply-to:mime-version:user-agent:date:message-id:from:references :cc:to:subject:dkim-signature:dkim-filter; bh=SOgrwpFFY+YzKw7ZoYA87zklR2FlA7RT4tyiYC6DbQs=; b=nVYD3u3VZlnExRy+go+s5HEK8SNw95mX9dRa5FcSNIpZJjc3TVSI651+8loFJvQJg5 vCc8EstQbQNK+pYvas3c+//cHyxbCy7xt9Ac9HlHKkZw3ZRunbhl6g4bnsHDntu5h7ky ZwKw5e6ClE3bSGHk9be2Fz+Yv/KtC8/+aWWLa2MrdUCiVcRTpJNWPvG+kNH7MFVmd8ut qpojz0ZSVU6R0u1ZgN0ndvJ4kXIRYSI9ECvh0kyTb79doTiMzisRRq6H6GTeHve2ma96 7/3Ffg92Qj9mE9wnA/zZczwYSy6NAi/ctM4Hg00gcWBU766RrI/hf9oMYmmhaVG5hoT9 rSTg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@broadcom.com header.s=dkimrelay header.b=vb2Js1EU; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s201si5814423ios.76.2021.05.12.00.43.14; Wed, 12 May 2021 00:43:30 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-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=@broadcom.com header.s=dkimrelay header.b=vb2Js1EU; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=broadcom.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230097AbhELHoJ (ORCPT + 99 others); Wed, 12 May 2021 03:44:09 -0400 Received: from relay.smtp-ext.broadcom.com ([192.19.11.229]:37330 "EHLO relay.smtp-ext.broadcom.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229627AbhELHoJ (ORCPT ); Wed, 12 May 2021 03:44:09 -0400 Received: from bld-lvn-bcawlan-34.lvn.broadcom.net (bld-lvn-bcawlan-34.lvn.broadcom.net [10.75.138.137]) by relay.smtp-ext.broadcom.com (Postfix) with ESMTP id BEA727DAE; Wed, 12 May 2021 00:43:00 -0700 (PDT) DKIM-Filter: OpenDKIM Filter v2.11.0 relay.smtp-ext.broadcom.com BEA727DAE DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=broadcom.com; s=dkimrelay; t=1620805380; bh=9SE0dT91kgD5j8uvnhdwRHCQewZhC/i1wftrkfsm05A=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=vb2Js1EUuos9SeJ6ogtnd4FLOOXlyLvFYRKmxNAubmBvvCAeTPAzr55kCqKOwtsVZ YKbEk7JHkPZKWXqWbQ6lfPeaQbjUMMnQln0pjnfgGCYr6806apjj3ehlTvME657CG1 Zwkp0iTjCcUFxV1IY9RAI8lrxt5PCUGYC/uEJfRg= Received: from [10.230.41.88] (unknown [10.230.41.88]) by bld-lvn-bcawlan-34.lvn.broadcom.net (Postfix) with ESMTPSA id 7BF001874BE; Wed, 12 May 2021 00:42:58 -0700 (PDT) Subject: Re: [PATCH] brcmfmac: Obtain reset GPIO To: Ulf Hansson Cc: Linus Walleij , Arend van Spriel , Franky Lin , Hante Meuleman , Chi-hsien Lin , Wright Feng , Chung-hsien Hsu , linux-wireless References: <20210509224226.348127-1-linus.walleij@linaro.org> <30a7bbeb-d588-4780-bd6c-d99f72898138@broadcom.com> From: Arend van Spriel Message-ID: <4e2f8e28-8b4c-fb80-6a41-7d71e33a6d1c@broadcom.com> Date: Wed, 12 May 2021 09:42:56 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.10.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On 5/11/2021 10:48 AM, Ulf Hansson wrote: > On Mon, 10 May 2021 at 11:27, Arend van Spriel > wrote: >> >> >> >> On 5/10/2021 11:14 AM, Ulf Hansson wrote: >>> On Mon, 10 May 2021 at 09:37, Arend Van Spriel >>> wrote: >>>> >>>> + Uffe >>>> >>>> On 5/10/2021 12:42 AM, Linus Walleij wrote: >>>>> This grabs the reset GPIO and holds it de-asserted, if available. >>>>> Asserting this signal will make the SDIO card re-enumerate. >>>> >>>> looks ok to me, but could this also be done through SDIO power sequence >>>> stuff? >>> >>> Yes, it certainly looks like that to me. It should be the mmc >>> host/core that manages the power on/off thingy for the SDIO card. >> >> Thanks, Uffe >> >> This is not directly power on/off, but a separate "reset" GPIO. However, >> checking in pwrseq_simple.c I see: >> >> struct mmc_pwrseq_simple { >> struct mmc_pwrseq pwrseq; >> bool clk_enabled; >> u32 post_power_on_delay_ms; >> u32 power_off_delay_us; >> struct clk *ext_clk; >> struct gpio_descs *reset_gpios; >> }; >> >> So the term 'reset_gpios' is also used in pwrseq context. > > I think this boils down to that to allow the mmc core to detect and > initialize the SDIO card, it needs to manage potential reset pins as > well. > > In cases when the SDIO func driver may need to execute a reset, the > mmc core provides two APIs, mmc_hw|sw_reset(). > > Does this make sense to you? It does to me. Regards, Arend