Received: by 2002:a05:6358:1087:b0:cb:c9d3:cd90 with SMTP id j7csp1113609rwi; Thu, 20 Oct 2022 08:47:26 -0700 (PDT) X-Google-Smtp-Source: AMsMyM4ui3ZyoHSKWWUXpPcqfHdbYe6niNWnMOosNMpyUcijqjYbWsYRy1n3KDr1Qku6+/TStjLk X-Received: by 2002:a17:907:628f:b0:72f:58fc:3815 with SMTP id nd15-20020a170907628f00b0072f58fc3815mr11717810ejc.719.1666280845780; Thu, 20 Oct 2022 08:47:25 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1666280845; cv=none; d=google.com; s=arc-20160816; b=XbArSd4ai2+lGwBG0WjB0r9TOuOOBzPGpDtxUtcQMFndNNoFjafba8Km7N2odXLjsn x5Yjj5buHY2XIts/+0rsuIuSpxnVaoGBtkLS82BTDNgg9FUCkxIydvpNSenwMpYc4tZy QEjlrlhsyAfg9KqF+H0+hpfsog0Lmpzdst8j/aEkpkoPlNnQGcYAcPqjeUBD+w65r1w8 MeJstcjLf21cgVTyNxVmXijXjOEzu4i7Xjuni/udjQ80GkwCzr1L+tnt+dYYdzB1a+fM FmLe9SIAXnlUcTS+uyGsrGDSvfwwccLYK1VKz3nn2oxz3vcd9KMM6MR+80c/csuL3cSR BR4w== 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 :references:in-reply-to:message-id:date:subject:cc:to:from :dkim-signature; bh=phcPBaGxOFAemR9YFsCDrE8yrlHvz+AvjsJ/jn+/KmI=; b=ZsLQIwLjpZgA9LAfRWOXwIdKN7VzYtLO419ns5NiH7A4eB4HrNsOv3tm4Hs5x/yci8 +NjQAedxLTLI49rKIegOzwYIgDn3yLs0R9iYnYFrAQSsKSsmklfVJ/dOXK3PqvoaUuYm wEDrRaeTs82kT/vWUE+jPePdehvnMmTWt6GclCReDHgic492uWSuUcMnsNUXGNaYVUPX 0dEveBMmCFiAhM8hrwujgRCRcJ4+fXeKmNbzywUFHppErbS4WZ2TLzHgpcZ1f2J+qW7l vuBVNVIUT7Gb6ypYJhcp16r/Opxae7dKxQqtplZ6fy/I45LhM6kpHiv+hlvQVW8dDzjE xk4Q== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=cQZeTaLx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id f13-20020a0564021e8d00b0045d4a88c735si16891947edf.220.2022.10.20.08.46.59; Thu, 20 Oct 2022 08:47:25 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=cQZeTaLx; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230325AbiJTPRI (ORCPT + 99 others); Thu, 20 Oct 2022 11:17:08 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230041AbiJTPQ3 (ORCPT ); Thu, 20 Oct 2022 11:16:29 -0400 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E466814FD19 for ; Thu, 20 Oct 2022 08:16:24 -0700 (PDT) Received: by mail-wr1-x433.google.com with SMTP id bu30so35080804wrb.8 for ; Thu, 20 Oct 2022 08:16:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sifive.com; s=google; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:from:to:cc:subject:date :message-id:reply-to; bh=phcPBaGxOFAemR9YFsCDrE8yrlHvz+AvjsJ/jn+/KmI=; b=cQZeTaLxjf77kJiNM9B9vGBb6AMSIHOTChOwi0lz0YIl0srH5pIGZQsZqceTMc/zy3 52majJ4QY325w7Jz8E1MDjGF+WaMELJ2b6ZOQC7/M6Sxz5k0xwkPjo4X4IIxMd8asDHJ Lj4StpgQoHfHXbp0rUkXCoWlHNEoSNIE8mTgWV3RM9oRxJKUeMD9YkmqJ4Q8p23HT7cI 65VLh7vx2TduetVtra+0epqeRxU+UVLItO5FJDu+vMcNmUNkiVu8gC1CeU36Uthh3jCh dAdkIED3QycFdd4Lor8PJSecdifrlHmlBgtTUPsp6V/CsyQ2/hZd+njtryH/rEdGf91s c6Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=content-transfer-encoding:mime-version:references:in-reply-to :message-id:date:subject:cc:to:from:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=phcPBaGxOFAemR9YFsCDrE8yrlHvz+AvjsJ/jn+/KmI=; b=fKLRzNSC/Uf+nBkZOXFPRdktjYTtBZIYPAUv6OMeYiUtAoNiPSb+S8JKuCIcoIKDEH GmKuZTA10+zFhuh9r7Ws7il7cKDMTQGlL1JySTjcc7Q31anMntAKMZx6+YtUAhAyrj+V TOPtnR8NHICHktQtL/ma5eH4Zf5ksV/U8uAqY115lLGroY0I3gDQZs8zwdx5wXy36Lm+ 3n5to8eM6rjHP2IUDdiwv9tFeBpNA7uh6qZWbQ8o1YcBsXgxUuAlOTaK3OwehgwqQFLj cQ596AjydKMMaR8tETfh6cBehn4IXfQZHrECrZT/Li1f2tXSUPf3Hbt9/Aa+9h1UEsFz 60GQ== X-Gm-Message-State: ACrzQf3MrkTUZ7YmRT4bqJrda9t7dm9b6+ItaM+ltFa3Cq4tWwNa/6B9 p9wK1gczHDAdueBg4IxI+k4t4g== X-Received: by 2002:a05:6000:788:b0:22e:412b:7959 with SMTP id bu8-20020a056000078800b0022e412b7959mr8884219wrb.491.1666278984308; Thu, 20 Oct 2022 08:16:24 -0700 (PDT) Received: from rainbowdash.guest.codethink.co.uk ([167.98.27.226]) by smtp.gmail.com with ESMTPSA id bg6-20020a05600c3c8600b003c6f3e5ba42sm41362wmb.46.2022.10.20.08.16.23 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 20 Oct 2022 08:16:23 -0700 (PDT) From: Ben Dooks To: linux-pwm@vger.kernel.org Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, Lee Jones , u.kleine-koenig@pengutronix.de, Thierry Reding , Krzysztof Kozlowski , Greentime Hu , jarkko.nikula@linux.intel.com, William Salmon , Jude Onyenegecha , Ben Dooks Subject: [PATCH v6 09/10] pwm: dwc: add PWM bit unset in get_state call Date: Thu, 20 Oct 2022 16:16:09 +0100 Message-Id: <20221020151610.59443-10-ben.dooks@sifive.com> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20221020151610.59443-1-ben.dooks@sifive.com> References: <20221020151610.59443-1-ben.dooks@sifive.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_NONE, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org If we are not in PWM mode, then the output is technically a 50% output based on a single timer instead of the high-low based on the two counters. Add a check for the PWM mode in dwc_pwm_get_state() and if DWC_TIM_CTRL_PWM is not set, then return a 50% cycle. This may only be an issue on initialisation, as the rest of the code currently assumes we're always going to have the extended PWM mode using two counters. Signed-off-by: Ben Dooks --- v4: - fixed review comment on mulit-line calculations --- drivers/pwm/pwm-dwc.c | 29 ++++++++++++++++++----------- 1 file changed, 18 insertions(+), 11 deletions(-) diff --git a/drivers/pwm/pwm-dwc.c b/drivers/pwm/pwm-dwc.c index 1251620ab771..5ef0fe7ea3e9 100644 --- a/drivers/pwm/pwm-dwc.c +++ b/drivers/pwm/pwm-dwc.c @@ -121,23 +121,30 @@ static void dwc_pwm_get_state(struct pwm_chip *chip, struct pwm_device *pwm, { struct dwc_pwm *dwc = to_dwc_pwm(chip); u64 duty, period; + u32 ctrl, ld, ld2; pm_runtime_get_sync(chip->dev); - state->enabled = !!(dwc_pwm_readl(dwc, - DWC_TIM_CTRL(pwm->hwpwm)) & DWC_TIM_CTRL_EN); + ctrl = dwc_pwm_readl(dwc, DWC_TIM_CTRL(pwm->hwpwm)); + ld = dwc_pwm_readl(dwc, DWC_TIM_LD_CNT(pwm->hwpwm)); + ld2 = dwc_pwm_readl(dwc, DWC_TIM_LD_CNT2(pwm->hwpwm)); - duty = dwc_pwm_readl(dwc, DWC_TIM_LD_CNT(pwm->hwpwm)); - duty += 1; - duty *= dwc->clk_ns; - state->duty_cycle = duty; + state->enabled = !!(ctrl & DWC_TIM_CTRL_EN); - period = dwc_pwm_readl(dwc, DWC_TIM_LD_CNT2(pwm->hwpwm)); - period += 1; - period *= dwc->clk_ns; - period += duty; - state->period = period; + /* If we're not in PWM, technically the output is a 50-50 + * based on the timer load-count only. + */ + if (ctrl & DWC_TIM_CTRL_PWM) { + duty = (ld + 1) * dwc->clk_ns; + period = (ld2 + 1) * dwc->clk_ns; + period += duty; + } else { + duty = (ld + 1) * dwc->clk_ns; + period = duty * 2; + } + state->period = period; + state->duty_cycle = duty; state->polarity = PWM_POLARITY_INVERSED; pm_runtime_put_sync(chip->dev); -- 2.35.1