Received: by 10.192.165.148 with SMTP id m20csp1851173imm; Thu, 26 Apr 2018 03:16:02 -0700 (PDT) X-Google-Smtp-Source: AB8JxZpU6Mlx/+hXJYRDun0Vjr3hOWm+puBLOWI7PeI4Mw3kNQDLeQfFGEM41Q4ckGnVcYzY5N9h X-Received: by 2002:a17:902:526f:: with SMTP id z102-v6mr8972109plh.223.1524737762632; Thu, 26 Apr 2018 03:16:02 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1524737762; cv=none; d=google.com; s=arc-20160816; b=LiLlY2ljbDMiVMI1AUPIGOUTSqfJ5+N8rrSUFAUQ23kQRNp+Su8bnCXyQzD7uwS3mU yIENLKybgYjwryY6MzRtezaDfsRY0/oflXToOiljf/dKooNRzrjI1IKx9oQHEanUboUL R5qC6nT/1lG010V+bskJcEpW0VOxeD44s0w7ju+cILYbWcJ17wnNtGnhEzP9pnzb0inY mR2gB89QshkHNBOWg++eqx2UJfsBoe4eedGUlGmykDSQO5CKUwoPovMINpmLLo8W1UEM F/AvSgApLvZ8pvJd0pjgZ5FBUCKiVTXBjbRWF9/tCWATGXTg+iP7vPrmSzaP9ZzMU222 BaTw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:mime-version:content-transfer-encoding :content-language:accept-language:in-reply-to:references:message-id :date:thread-index:thread-topic:subject:cc:to:from:dkim-signature :arc-authentication-results; bh=IMN+ZmUfXBpZ6s01t94MqtpeFJ+kO22Og6ovj8ZTisA=; b=JREl76SwTnPBgVLNVykeFuC8k5BFgv2D9PRSHnUfUe86EOx8LhHWs7FzXoeW4ZTazi vQNi4Dj5K7u+hRjkX95eeEmbFPdUjSCAh3KGeLJZPH4/uJ2jNQeCRFdYJ9I3p+fKMmRE Sl709l197tJCzaErAWjgDIOpct4KGgHlfdc+jrV7dDkuHT2QUyapocGmnd6VNofhvMaQ Anih80N+sdRTajfmGpm05Ku9EbpWqIFxtrMe6af7imHc1g1hr0Ppas9cv+Q/T47xs6JI EcwxL6yuIq3uOV67LwyM7n3JpHHhWpoy0Be3uHTBXZgU/E2LXowJ8i2xzertkN3oZp1K 23hA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=rx5wTkSD; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id p5si15537083pgr.472.2018.04.26.03.15.48; Thu, 26 Apr 2018 03:16:02 -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=@ti.com header.s=ti-com-17Q1 header.b=rx5wTkSD; 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=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755228AbeDZKOW (ORCPT + 99 others); Thu, 26 Apr 2018 06:14:22 -0400 Received: from lelnx193.ext.ti.com ([198.47.27.77]:55023 "EHLO lelnx193.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754277AbeDZKOU (ORCPT ); Thu, 26 Apr 2018 06:14:20 -0400 Received: from dflxv15.itg.ti.com ([128.247.5.124]) by lelnx193.ext.ti.com (8.15.1/8.15.1) with ESMTP id w3QAEDcO031320; Thu, 26 Apr 2018 05:14:13 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=ti.com; s=ti-com-17Q1; t=1524737654; bh=IMN+ZmUfXBpZ6s01t94MqtpeFJ+kO22Og6ovj8ZTisA=; h=From:To:CC:Subject:Date:References:In-Reply-To; b=rx5wTkSD9RuN+hCg17sXcBnxy1a65ZwfcMmgzvzmsoRmV/bNxXaV79n/rTzcLk4rG qoK0xdUYOX0zUw5i43P7146ruSKJnwshy13TsdhMGW2NOquJ/gfykfyrW/b5viJwfh ynATuhoaCfYi3rzMsuuJGFKJahhKCfYOktQjCUX8= Received: from DFLE103.ent.ti.com (dfle103.ent.ti.com [10.64.6.24]) by dflxv15.itg.ti.com (8.14.3/8.13.8) with ESMTP id w3QAEDFJ004821; Thu, 26 Apr 2018 05:14:13 -0500 Received: from DFLE103.ent.ti.com (10.64.6.24) by DFLE103.ent.ti.com (10.64.6.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1466.3; Thu, 26 Apr 2018 05:14:13 -0500 Received: from DFLE103.ent.ti.com ([fe80::7431:ea48:7659:dc14]) by DFLE103.ent.ti.com ([fe80::7431:ea48:7659:dc14%17]) with mapi id 15.01.1466.003; Thu, 26 Apr 2018 05:14:13 -0500 From: "Reizer, Eyal" To: Kalle Valo CC: Eyal Reizer , "linux-wireless@vger.kernel.org" , "robh@kernel.org" , "sre@kernel.org" , "tony@atomide.com" , "linux-kernel@vger.kernel.org" Subject: RE: [EXTERNAL] Re: [PATCH v2] wlcore: sdio: allow pm to handle sdio power Thread-Topic: [EXTERNAL] Re: [PATCH v2] wlcore: sdio: allow pm to handle sdio power Thread-Index: AQHT3UCfetw9p/qzd0ix7CJgDFtru6QS1AWQ Date: Thu, 26 Apr 2018 10:14:13 +0000 Message-ID: References: <1524721631-5983-1-git-send-email-eyalr@ti.com> <87po2m7573.fsf@kamboji.qca.qualcomm.com> <4750eeeedcde47d39cd207a8c21ef802@ti.com> <87lgda71zl.fsf@kamboji.qca.qualcomm.com> In-Reply-To: <87lgda71zl.fsf@kamboji.qca.qualcomm.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [137.167.25.139] x-exclaimer-md-config: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org >=20 > >> > >> > pm_runtime handles sdio power on and power off transitions. > >> > An old workaround for trying to control the power explicitly from th= e > >> > driver was in fact causing failures on suspend/resume as the mmc lay= er > >> > already power the module on resume. > >> > > >> > In case of resume pm_runtime_get sync returns a positive device's > usage > >> > count causing the driver to try an re-initialize an already initiali= zed > >> > device. This was causing sdio bus failure on resume. > >> > > >> > Remove this manual power on/off sequence as it is in-fact not needed= . > >> > > >> > Signed-off-by: Eyal Reizer > >> > Acked-by: Tony Lindgren > >> > >> No changelog. > >> > >> > https://wireless.wiki.kernel.org/en/developers/documentation/submittingp > >> atches#changelog_missing > >> > >> No need to resubmit because of this, I guess you just fixed the title > >> and added Tony's Acked-by? > > > > Yes, this is correct. No change in the actual patch hence there was no > change > > Log. >=20 > _Always_ include a change log, even if you didn't actually change > anything. Otherwise the maintainer has no clue what has changed and why > a new version was submitted. >=20 Understood. Thanks! BR, Eyal