Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4325640imm; Mon, 14 May 2018 06:05:00 -0700 (PDT) X-Google-Smtp-Source: AB8JxZo19O+sU3W5+RYdb5UfKs11l8msmirO3fpRyaVMh+1x1PnMXaZbbsnDx57BKUnd8UfQN0e1 X-Received: by 2002:a63:2783:: with SMTP id n125-v6mr7063270pgn.377.1526303100113; Mon, 14 May 2018 06:05:00 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526303100; cv=none; d=google.com; s=arc-20160816; b=DmD7O+k5Urx/8RJnTT+aiu4Y1/1LXvIH4jpAye2nbgM0lYQ9P1F/2iRDXeGS+NL93V zQspAGvGEtKkI4zEbt739ZEEDPEpEmmKznLu/K7RjTUWepgLKCZLqtOw6ZuTFrOrhdTq 9IpcmlSFIBMUTL5XdCvdAc42NcwWq1nWOyl0GKaPmx9zdGD4XZT/kJfv658OIDc1LAQd vpgMB4NFQDv3Okc0jkaM1tOfu+oRMjPUHhsaRZwpSHciw1WcZ3iV0MnlByPSWJJnjKjp XrIWENl5hc4cL1U4oDufhKASOOCsmXvgTz9DjQrkM24wP0DeSmSkiGbgyaybbPxj8cOh R1Lg== 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:autocrypt:openpgp:from:references:cc:to:subject :dkim-signature:arc-authentication-results; bh=zJTF4sMr6eWqI+rTnRJn0kKScQwAuMruhbj+NRxzEKs=; b=SlFtmX8pBF9wBruJRQxG82SUdBgYp8LNB17eST1VbLcD1EWCyiKITP3e3xt8b/eLp3 qubgJm7+qckMSy6TexaS53a3KGcHWQ0KNBSdC4hG5/cv0mRkW1UxTS1dyLTrzI0qmmCB rkKOHgjZiDQgsJH6E5O2l24XjYbVnUlf/056O477KWTw85LtP06WReq5bJnfazKGOr6U uVD3OvdX41+Cfjhh+grU3fYclJKR/QswH8J/UAsFqE0rMWo9SPQp7IO3mo6HcOwfZO1z RRGzQ1F3cfj2phkSwvgILf2g0vbcMcDm/s1OYMWqvVTgCVgHb/Br7PsZfo5Gai8MUjj1 epHQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@gmail.com header.s=20161025 header.b=cLYvXUG+; 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=QUARANTINE dis=NONE) header.from=gmail.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id f15-v6si8952062plr.365.2018.05.14.06.04.14; Mon, 14 May 2018 06:05:00 -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=@gmail.com header.s=20161025 header.b=cLYvXUG+; 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=QUARANTINE dis=NONE) header.from=gmail.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1753650AbeENNEC (ORCPT + 99 others); Mon, 14 May 2018 09:04:02 -0400 Received: from mail-lf0-f66.google.com ([209.85.215.66]:45108 "EHLO mail-lf0-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752463AbeENNDy (ORCPT ); Mon, 14 May 2018 09:03:54 -0400 Received: by mail-lf0-f66.google.com with SMTP id q2-v6so17828777lfc.12; Mon, 14 May 2018 06:03:53 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:openpgp:autocrypt:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=zJTF4sMr6eWqI+rTnRJn0kKScQwAuMruhbj+NRxzEKs=; b=cLYvXUG+QcZWX9m8g1pA3j63DOC5YMC26TTwbVkM2ahLpz3hZjPgEO9qut+gvAKLle EUZG85aHZfUi9Q+ztThKgwD4oqbciCBqUo3PCZIYUjVTI+WsV9xCzldo+IbmZaeSRh7d H4Z9eexyWyUjt/ibwuJpazYRLYT337pQrN5P66mqGUdI2PUV2UMp7U7VQjPnUwqB7PKO dZJCDH9rxeKfj0b/DuRWidutK6Ehfz6vcr2VpPaKb3Bw2uSNcMvD3UBAfSK/W5WFtox1 zL+QmEKRMUF+lbF7p0JZLrvYiBluVX3Al98PFPdvqIMwg28LPgzAtUMSAeochM0AFjLe 95Kw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:openpgp:autocrypt :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=zJTF4sMr6eWqI+rTnRJn0kKScQwAuMruhbj+NRxzEKs=; b=DxpN81E+BAGCw9JErvLgSy6Hgg5BOSIO3rtmnYfb5YGI6H/4IarMvxGPT0h4Ie9A0Z M1le+M2rdqrVlV5ayQDszEdFceZbe1oW7l7t+ZSq795+56Yo6OzHd4FqXo4jwd0bmzlr KW/8rcUhJsqjgDIFe7SwMHJ1QmZ8BMlbj0EjssdYEATOe98aRZHpa4XuodQ4LQuhLsO8 elJL4W45+cKCtt7TyHUgOBfu0qHfB/cZ4sJeTr52SzD2AWSvl3L1yymgcQNAF/7WX0fq VjgtwnDQD9BXDr/D+fiBaYYtvaK8lATd9eZlbc1jY1A5bzHyGarGQ0x/T/KnvKGQKN45 n6AA== X-Gm-Message-State: ALKqPwfAohQePt5mWpIwYohI3fRvcP7bczvzKQCaUiVR3ccYsYpqRfKr BIyHizX2rRY8PuzIAWV025hcRFv3 X-Received: by 2002:a19:94c7:: with SMTP id o68-v6mr9167226lfk.111.1526303032283; Mon, 14 May 2018 06:03:52 -0700 (PDT) Received: from [192.168.1.145] (109-252-91-232.nat.spd-mgts.ru. [109.252.91.232]) by smtp.googlemail.com with ESMTPSA id g132-v6sm2402791lfg.23.2018.05.14.06.03.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 14 May 2018 06:03:51 -0700 (PDT) Subject: Re: [PATCH v1] i2c: tegra: Remove suspend-resume To: Wolfram Sang , Thierry Reding Cc: Jonathan Hunter , Laxman Dewangan , Shardar Shariff Md , linux-tegra@vger.kernel.org, linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org References: <20180513211347.7187-1-digetx@gmail.com> <20180514115933.GH18312@ulmo> <20180514121833.2hcpuwfjxmzi3rcx@katana> From: Dmitry Osipenko Openpgp: preference=signencrypt Autocrypt: addr=digetx@gmail.com; prefer-encrypt=mutual; keydata= xsBNBFpX5TwBCADQhg+lBnTunWSPbP5I+rM9q6EKPm5fu2RbqyVAh/W3fRvLyghdb58Yrmjm KpDYUhBIZvAQoFLEL1IPAgJBtmPvemO1XUGPxfYNh/3BlcDFBAgERrI3BfA/6pk7SAFn8u84 p+J1TW4rrPYcusfs44abJrn8CH0GZKt2AZIsGbGQ79O2HHXKHr9V95ZEPWH5AR0UtL6wxg6o O56UNG3rIzSL5getRDQW3yCtjcqM44mz6GPhSE2sxNgqureAbnzvr4/93ndOHtQUXPzzTrYB z/WqLGhPdx5Ouzn0Q0kSVCQiqeExlcQ7i7aKRRrELz/5/IXbCo2O+53twlX8xOps9iMfABEB AAHNIkRtaXRyeSBPc2lwZW5rbyA8ZGlnZXR4QGdtYWlsLmNvbT7CwJQEEwEIAD4WIQSczHcO 3uc4K1eb3yvTNNaPsNRzvAUCWlflPAIbAwUJA8JnAAULCQgHAgYVCgkICwIEFgIDAQIeAQIX gAAKCRDTNNaPsNRzvFjTCACqAh1M9/YPq73/ai5h2ExDquTgJnjegL8KL2yHL3G+XINwzN5E nPI7esoYm+zVWDJbv3UuRqylpookLNSRA01yyvkaMcipB/B128UnqmUiGRqezj9QE20yIauo uHRuwHPE2q+UkfUhRX9iuOaEyQtZDiCa0myMjmRkJ+Z8ZetclEPG8dYZu47w04phuMlu1QAt a0gkZOaMKvXgj21ushALS6nYnvm7HiIPQXfnEXThartatRvFdmbG4PCn0IoICkQBizwJtXrL HEjELIFap0M8krVJlUoZTFaZnaZkGpUDWikeFtAuie2KuIxmVBYPM4X7pM3eP3AVvIPGS7EE UUFuzsBNBFpX5TwBCADFNDou220thijaLLGaQsebWjzc/gPRxMixIpk856MRyRaQin+IbGD6 YskMb5ZSD3nS88LIKNfY4MMH0LwfYztI++ICG2vdFLkbBt78E+LqEa+kZ9072l4W5KO3mWQo +jMfxXbpgGlc7iuEReDgl8iyZ27r51kSW665CYvvu2YJhLqgdj6QM1lN2D1UnhEhkkU+pRAj 1rJVOxdfJaQNQS4+204p3TrURovzNGkN/brqakpNIcqGOAGQqb8F0tuwwuP7ERq/BzDNkbdr qJOrVC/wkHRq1jfabQczWKf8MwYOvivR3HY8d3CpSQxmUXDtdOWfg0XGm1dxYnVfqPjuJaZt ABEBAAHCwHwEGAEIACYWIQSczHcO3uc4K1eb3yvTNNaPsNRzvAUCWlflPAIbDAUJA8JnAAAK CRDTNNaPsNRzvJzuB/9d+sxcwHbO8ZDcgaLX9N+bXFqN9fIRVmBUyWa+qqTSREA4uVAtYcRT lfPE2OQ7aMFxaYPwo+/z5SLpu8HcEhN/FG9uIkfYwK0mdCO0vgvlfvBJm4VHe7C6vyAeEPJQ DKbBvdgeqFqO+PsLkk2sawF/9sontMJ5iFfjNDj4UeAo4VsdlduTBZv5hHFvIbv/p7jKH6OT 90FsgUSVbShh7SH5OzAcgqSy4kxuS1AHizWo6P3f9vei987LZWTyhuEuhJsOfivDsjKIq7qQ c5eR+JJtyLEA0Jt4cQGhpzHtWB0yB3XxXzHVa4QUp00BNVWyiJ/t9JHT4S5mdyLfcKm7ddc9 Message-ID: <35bb3f47-2767-bc6c-62c0-b568f80a1cfb@gmail.com> Date: Mon, 14 May 2018 16:03:50 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0 MIME-Version: 1.0 In-Reply-To: <20180514121833.2hcpuwfjxmzi3rcx@katana> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 14.05.2018 15:18, Wolfram Sang wrote: > On Mon, May 14, 2018 at 01:59:33PM +0200, Thierry Reding wrote: >> On Mon, May 14, 2018 at 12:13:47AM +0300, Dmitry Osipenko wrote: >>> Nothing prevents I2C clients to access I2C while Tegra's driver is being >>> suspended, this results in -EBUSY error returned to the clients and that >>> may have unfortunate consequences. In particular this causes problems >>> for the TPS6586x MFD driver which emits hundreds of "failed to read >>> interrupt status" error messages on resume from suspend. This happens if >>> TPS6586X is used to wake system from suspend by the expired RTC alarm >>> timer because TPS6586X is an I2C device driver and its IRQ handler reads >>> the status register while Tegra's I2C driver is suspended, i.e. just after >>> kernel enabled IRQ's during of resume-from-suspend process. >>> >>> Note that the removed tegra_i2c_resume() invoked tegra_i2c_init() which >>> performs HW reset. That seems was also not entirely correct because moving >>> tegra_i2c_resume to an earlier stage of resume-from-suspend process causes >>> I2C transfer to fail in the case of TPS6586X. It is fine to remove the >>> HW-reinitialization for now because it should be only needed in a case of >>> using lowest power-mode during suspend, which upstream kernel doesn't >>> support. >>> >>> Signed-off-by: Dmitry Osipenko >>> Cc: >>> --- >>> drivers/i2c/busses/i2c-tegra.c | 33 --------------------------------- >>> 1 file changed, 33 deletions(-) >> >> Shardar, Laxman, any thoughts on this? The is_suspended thing looks to >> me like a workaround of some sort that may not be needed if clients have >> proper suspend/resume implementations. Even without suspend/resume >> support in client drivers, the driver core should resume devices in the >> right order (I2C adapter before any of the clients), so I don't see any >> cases where the is_suspended logic would be useful. > > Thanks for this patch! > > This is closely related to a discussion we started recently: > > "I2C PM overhaul needed?" https://lkml.org/lkml/2018/5/4/329 > > And part of the outcome is that the I2C core should print a WARN if an > I2C client tries to use I2C at suspend_noirq state or later. This is to > remove logic like in this patch from all I2C host drivers and to make it > more explicit that those I2C client drivers need their PM fixed. > Thank you very much for pointing at the discussion. Indeed it should be nicer if I2C core handled the buggy client drivers and the rest of related suspend/resume issues instead of having each I2C BUS driver to do it on its own.