Received: by 2002:a05:6a10:1287:0:0:0:0 with SMTP id d7csp3781691pxv; Mon, 19 Jul 2021 08:36:18 -0700 (PDT) X-Google-Smtp-Source: ABdhPJxND+8scXUf0jrRd0syLVJWA6w76iEuBXv9n289DR9qJjKlThOmA+xhI30dzr7w+AtwOri7 X-Received: by 2002:a50:d642:: with SMTP id c2mr34689225edj.22.1626708978353; Mon, 19 Jul 2021 08:36:18 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1626708978; cv=none; d=google.com; s=arc-20160816; b=HCCTNaCRHlftRAtptJeOsKntdfSiNahKc2jxzF35jiC2YSiaGMz6pEpBh6g58/0nEJ cb6KOIdmCBJNdyhG89yuNhu79OnqqICUeS5V77WwsDccKk+OTbUjQMbEF93oUUbOGnAh PwqWuLCI/9If8JkFftOruWNjjnnvj/Lh62SkOHFP0hmEDLg/lS/XwHRKYKspyKdV3pDo njGBN8O0L//y6V0eycN5hSVLniAZuOjk0Hf/OIDOtvvnP+MHpX+9bEPEc5ci1imVcMj/ dTF66rinU8cPTko/CYhaTqlZ68IGK3vP1MKQ7NNQijHGLCgtWlyDDk3gUIsuJRMvwFj2 8DJA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:message-id:date:subject:cc:to :from:dkim-signature; bh=Of5EgymQGVHmFbKGIe5+uO+zob9JqIl5UpML5rzLuR8=; b=H+AOnLPi4De3t2ZlVSn9Vk1hvhrQqD4p84rEBFIiIsL2J82oCEvtO44tN1IY6JzxTP 0AwvSDJKRfM2i+I0MscY7yrBYD+QrSYVcdAUBxrqX6yipVcfhZaX8YJZHknkKpBfzl7v uBDpGC12MTIvgqs/F6zoxe46YVv1KbJXSYS6UH9zbslZeh8ODvUo5+eFezHl2DRdGiiS V56PBuz3OGVKsej3odKePQyZDjQ9rnjXsiTt2iOm+Z7Bvt6KtVpX90O+p0E+r8SzMWHw F9mgBxUnFNgGF4EXTPFho8B3Nf5k1jZA+lEiHh6wQoJw1wlX1OQXtDUF0999WHfofVfu wHrg== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@linuxfoundation.org header.s=korg header.b=ZGj+PzOn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id w5si22156065edd.90.2021.07.19.08.35.53; Mon, 19 Jul 2021 08:36:18 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-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=@linuxfoundation.org header.s=korg header.b=ZGj+PzOn; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=linuxfoundation.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S241230AbhGSOv2 (ORCPT + 99 others); Mon, 19 Jul 2021 10:51:28 -0400 Received: from mail.kernel.org ([198.145.29.99]:47840 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S244244AbhGSOcp (ORCPT ); Mon, 19 Jul 2021 10:32:45 -0400 Received: by mail.kernel.org (Postfix) with ESMTPSA id EA7CF6120E; Mon, 19 Jul 2021 15:12:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=linuxfoundation.org; s=korg; t=1626707576; bh=yZiHhf7MDMsrBOm+Rfirza9bKGPc4BGe3mcHCLe6UbU=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=ZGj+PzOniICMjCS7vlb/zkcnm+Z4USLEnE7DhE6I5+BYrvbhnQz8FAQw4DjxjzKJ2 r6yKStE4ySh/mQsNu+q7GeDEAbibmS/wPGo9LXDaETajG4DSMXngj/3pFFDc9Rh8c8 DALr8+i06d2LGCT03cX6N4rLZIHJTqMrDT+g3QdE= From: Greg Kroah-Hartman To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman , stable@vger.kernel.org, =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?= , Thierry Reding , Sasha Levin Subject: [PATCH 4.9 220/245] pwm: tegra: Dont modify HW state in .remove callback Date: Mon, 19 Jul 2021 16:52:42 +0200 Message-Id: <20210719144947.492624219@linuxfoundation.org> X-Mailer: git-send-email 2.32.0 In-Reply-To: <20210719144940.288257948@linuxfoundation.org> References: <20210719144940.288257948@linuxfoundation.org> User-Agent: quilt/0.66 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Uwe Kleine-König [ Upstream commit 86f7fa71cd830d18d7ebcaf719dffd5ddfe1acdd ] A consumer is expected to disable a PWM before calling pwm_put(). And if they didn't there is hopefully a good reason (or the consumer needs fixing). Also if disabling an enabled PWM was the right thing to do, this should better be done in the framework instead of in each low level driver. So drop the hardware modification from the .remove() callback. Signed-off-by: Uwe Kleine-König Signed-off-by: Thierry Reding Signed-off-by: Sasha Levin --- drivers/pwm/pwm-tegra.c | 13 ------------- 1 file changed, 13 deletions(-) diff --git a/drivers/pwm/pwm-tegra.c b/drivers/pwm/pwm-tegra.c index 7e8906d6ab7a..d76698ce6472 100644 --- a/drivers/pwm/pwm-tegra.c +++ b/drivers/pwm/pwm-tegra.c @@ -228,7 +228,6 @@ static int tegra_pwm_probe(struct platform_device *pdev) static int tegra_pwm_remove(struct platform_device *pdev) { struct tegra_pwm_chip *pc = platform_get_drvdata(pdev); - unsigned int i; int err; if (WARN_ON(!pc)) @@ -238,18 +237,6 @@ static int tegra_pwm_remove(struct platform_device *pdev) if (err < 0) return err; - for (i = 0; i < pc->chip.npwm; i++) { - struct pwm_device *pwm = &pc->chip.pwms[i]; - - if (!pwm_is_enabled(pwm)) - if (clk_prepare_enable(pc->clk) < 0) - continue; - - pwm_writel(pc, i, 0); - - clk_disable_unprepare(pc->clk); - } - reset_control_assert(pc->rst); clk_disable_unprepare(pc->clk); -- 2.30.2