Received: by 2002:ac0:a5b6:0:0:0:0:0 with SMTP id m51-v6csp937313imm; Wed, 13 Jun 2018 10:35:49 -0700 (PDT) X-Google-Smtp-Source: ADUXVKJ4oZGnU6mXBzPTKE6TFHZP216nf2AtiXG0ISJY5K31otq3uiCa6BEOlj4boIWWlDCsJx8K X-Received: by 2002:a17:902:7293:: with SMTP id d19-v6mr6172580pll.142.1528911349140; Wed, 13 Jun 2018 10:35:49 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1528911349; cv=none; d=google.com; s=arc-20160816; b=ScjWT7V93mqdPC2KB6fG2Epl28M5XoRldC0T+TWn7Z3LJ9KThRBhfMvoUEEm1t167J n/8JeaVNgopPU8hf+R6uOUU4AjFoODYUWklTsQIVmCWX4Uwv9UAvJmsQTJSJ4DY0fPKp TfYHg0qALdIjfqoCEzFibEWVDikgkjQxE9gsk3h2Bs39EiZoILl/q0lNMVMe83Pv6/tK J3U1fnFP98hAT8vS1q5VOxVZNpwkN8wQ9A465sinZ03G/2BkiuAUT5hA0eROSDAnIvnJ /56pdh/n5LEY99tiueUjuNTBKULkJtcnEvIJSVJdSbZI44LqsbNWB0/f+mHrRPHCuSTS D4KA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:arc-authentication-results; bh=hUVV4rZ77+uKy0LDAZud6LOIHabsX1qRbc2C4tLy9os=; b=jDhGK0/GmLaTotHfhf+kkM6KbjOGAUffdvOcsS6E34s7r1RxyPFuwodgpz1XaOQ/2w OSR5fVtDcHKTfKFy42UQclRcBnt/xUxbk6PGRBKvGk7gH0vlkPyoBD3ISt5QUmGdWLly iSuPNNSS3/JF3sc3PGQMIKNzydCRBOjVJnag8SAgUOdiPH3UknS6UuHN7t8ExnKlKM79 +NMquzZr3UL56+lHzI7rHIx7Jaoz9lzYA9VcZKHWyMZa4p7CQQgio+PY6cKJzahkxCRB SLXQyASIxEtek9cJONpbjH/pOpUj5aeTPJre3+F2FQ+EBhUbRddnlqacA+8PJIR1lRYg BArA== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id j12-v6si2597365pgf.359.2018.06.13.10.35.34; Wed, 13 Jun 2018 10:35:49 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935446AbeFMRet (ORCPT + 99 others); Wed, 13 Jun 2018 13:34:49 -0400 Received: from foss.arm.com ([217.140.101.70]:50332 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S934979AbeFMRes (ORCPT ); Wed, 13 Jun 2018 13:34:48 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.72.51.249]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id D58AF1435; Wed, 13 Jun 2018 10:34:47 -0700 (PDT) Received: from [10.1.206.36] (e113632-lin.cambridge.arm.com [10.1.206.36]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPA id 27F7E3F25D; Wed, 13 Jun 2018 10:34:46 -0700 (PDT) Subject: Re: [PATCH] arm64: dts: hikey: Define wl1835 power capabilities To: Ryan Grachek Cc: Wei Xu , Rob Herring , Mark Rutland , Catalin Marinas , Will Deacon , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, John Stultz References: <20180613151305.17240-1-ryan@edited.us> From: Valentin Schneider Message-ID: <521dd38a-29b8-5670-4296-84b300921b3d@arm.com> Date: Wed, 13 Jun 2018 18:34:45 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0 MIME-Version: 1.0 In-Reply-To: <20180613151305.17240-1-ryan@edited.us> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On 13/06/18 16:13, Ryan Grachek wrote: > These properties are required for compatibility with runtime PM. > Without these properties, MMC host controller will not be aware > of power capabilities. When the wlcore driver attempts to power > on the device, it will erroneously fail with -EACCES. > I don't have a hikey620 to test this, but the hikey960 is suffering from the same issue (see [1]). I added these properties to the dwmmc2 node of the hikey960 (see snippet) and wlan0 does show up. Would you mind sending a similar patch for that board ? Thanks ! Valentin [1]: https://lkml.org/lkml/2018/6/12/930 --->8 diff --git a/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts b/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts index 85aadf1b..c706f70 100644 --- a/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts +++ b/arch/arm64/boot/dts/hisilicon/hi3660-hikey960.dts @@ -613,6 +613,8 @@ vmmc-supply = <&wlan_en>; ti,non-removable; non-removable; + cap-power-off-card; + keep-power-in-suspend; #address-cells = <0x1>; #size-cells = <0x0>; status = "ok";