From patchwork Fri Aug 30 18:26:41 2019 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: Andy Shevchenko X-Patchwork-Id: 1156011 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=linux-pwm-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=none (p=none dis=none) header.from=linux.intel.com Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 46Knxd4lKrz9sML for ; Sat, 31 Aug 2019 04:26:45 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727959AbfH3S0o (ORCPT ); Fri, 30 Aug 2019 14:26:44 -0400 Received: from mga12.intel.com ([192.55.52.136]:48333 "EHLO mga12.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727883AbfH3S0o (ORCPT ); Fri, 30 Aug 2019 14:26:44 -0400 X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 30 Aug 2019 11:26:44 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,447,1559545200"; d="scan'208";a="211008287" Received: from black.fi.intel.com ([10.237.72.28]) by fmsmga002.fm.intel.com with ESMTP; 30 Aug 2019 11:26:43 -0700 Received: by black.fi.intel.com (Postfix, from userid 1003) id 3EDE51A1; Fri, 30 Aug 2019 21:26:41 +0300 (EEST) From: Andy Shevchenko To: Thierry Reding , linux-pwm@vger.kernel.org Cc: Andy Shevchenko , Mika Westerberg , =?utf-8?q?Uwe_Kleine-K=C3=B6nig?= Subject: [PATCH v1] pwm: pca9685: Fix regression for GPIO use Date: Fri, 30 Aug 2019 21:26:41 +0300 Message-Id: <20190830182641.81502-1-andriy.shevchenko@linux.intel.com> X-Mailer: git-send-email 2.23.0.rc1 MIME-Version: 1.0 Sender: linux-pwm-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-pwm@vger.kernel.org The commit e926b12c611c ("pwm: Clear chip_data in pwm_put()") breaks GPIO usage by actually removing a crucial call to pwm_set_chip_data(), which is being used as a flag to understand the mode (GPIO vs. PWM) in which pin is currently working. Now, if once I requested GPIO, I may not be able to free and request it again. Fixes: e926b12c611c ("pwm: Clear chip_data in pwm_put()") breaks GPIO usage Cc: Mika Westerberg Cc: Uwe Kleine-König Signed-off-by: Andy Shevchenko --- drivers/pwm/pwm-pca9685.c | 1 + 1 file changed, 1 insertion(+) diff --git a/drivers/pwm/pwm-pca9685.c b/drivers/pwm/pwm-pca9685.c index 168684b02ebc..7cdec56ab3ec 100644 --- a/drivers/pwm/pwm-pca9685.c +++ b/drivers/pwm/pwm-pca9685.c @@ -165,6 +165,7 @@ static void pca9685_pwm_gpio_free(struct gpio_chip *gpio, unsigned int offset) pm_runtime_put(pca->chip.dev); mutex_lock(&pca->lock); pwm = &pca->chip.pwms[offset]; + pwm_set_chip_data(pwm, NULL); mutex_unlock(&pca->lock); }