Received: by 2002:a05:6359:c8b:b0:c7:702f:21d4 with SMTP id go11csp96078rwb; Wed, 5 Oct 2022 15:20:41 -0700 (PDT) X-Google-Smtp-Source: AMsMyM7ouFUUrsk+WIbAodVCc9EsLnJL8NWZu8T+9dIcmDi1oCQCIP+ffaSi/4ra47QCDJOY4zY9 X-Received: by 2002:a17:902:ce8d:b0:178:6e80:bcb4 with SMTP id f13-20020a170902ce8d00b001786e80bcb4mr1466740plg.82.1665008441213; Wed, 05 Oct 2022 15:20:41 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1665008441; cv=none; d=google.com; s=arc-20160816; b=O4T+hFS4aEhLS90gSgyfKjFmzn2lZLZbvEgyAs+Lzt+wOstz1m5yucR5UncuQZtxJ8 8Ujc+TKF4dG/VjUGgrpkSjEAiA//KG+75B1gZTtzVYTseVXg1E08Grd9X33l482BdrkC QyZO6frAU28V9DLNBPyCYFnt7kAtZN5/EY1nIYmSjkr+JvIVO0GY5Q++MYogvYRswhcg /sgAeKvyLfyTTWt0lLKdozH4jXAd6PPmHDVgiE2ntzMoxe1kgAMzsieR0mMZRkQbvUNy 4LHgD++PdevzlLvvGXv5gEsCLcgraWHI311HpAv9RGxpDpyUPJoRCLLLDreaTJQvdpFd m1YQ== 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=IaSwJXg8SQCpscbMNIy36UG1J8+Pj+2QgAtXXyqOO6oqs8h40CZC/r5Mmrk/nL0YLG C5YjpnUIMdmmNi3KoGTWMZw7sJv1StR2BDnCTARViG+CE82EZ60Oceu+iMMSf0KlsbLE DmOXjL4dRD+L1y+1JXWg96KBnBRyKmJZmSIYQBrkoNURftnwQINRFVLFLOiEHsQO6hbP y6lMSpwu7dEnfaNKCzc0hwjhNnxLImhR9IU104gfLpC5kIMsmUmcGu2CXAIDzAxxS8Fv LmqAjOt5FAPAk3Ex1PWut9cnOdwJu82ZbqPaMSAbdYcyIoHxJB7hZEfY7UYywiyID8MS DB9g== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sifive.com header.s=google header.b=fT+awGr6; 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 j3-20020a056a00130300b005349ae658a7si3985216pfu.354.2022.10.05.15.20.05; Wed, 05 Oct 2022 15:20:41 -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=fT+awGr6; 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 S229837AbiJEWNj (ORCPT + 99 others); Wed, 5 Oct 2022 18:13:39 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:39128 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229751AbiJEWNH (ORCPT ); Wed, 5 Oct 2022 18:13:07 -0400 Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id F158483220 for ; Wed, 5 Oct 2022 15:12:57 -0700 (PDT) Received: by mail-wr1-x430.google.com with SMTP id b4so20891212wrs.1 for ; Wed, 05 Oct 2022 15:12:57 -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; bh=phcPBaGxOFAemR9YFsCDrE8yrlHvz+AvjsJ/jn+/KmI=; b=fT+awGr6HC6jkA8sx0VnpDhh6dUhw8YNN/6TYOobvNj54/0CpejDoJni+sVbPpx5wK 0DYNIt+gu5YDonucOoiaZtoAYsZ5PV7+qWbo35oR6JatzcqcjAiU43KSOqZ40yFONe7U wUwAAKK4GxlvcmvMTCcyKwbE6kciH3+6k/AMwUujo19TFDZWrU/Kqk1kDBRU5ryvpMN1 6pwFy0LU3gGg5TbFigo5GB4XxSst2U5KmBukaJg0LOaq5U30xBmG243cduPHJ77iuwUS ml+q5k/JI19wC5wz4TO0NvOUZFuM6jiVL9VC62+Uwvtb2W05q/avOkgCfSZg6M5Rv7Zr PSLg== 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; bh=phcPBaGxOFAemR9YFsCDrE8yrlHvz+AvjsJ/jn+/KmI=; b=eB91mETQDcwwQG+IVl3SLW1Id6nTkG75hqDrtqt1Ztft8FPACgqkQC4JQBRBIG5g+l +0oM8td1aCmroR0PCFe5JTmgfNMM4O0u+BaqKb8Fs51TOzHang7Vsh9BHAdxGr23nUjt BOW50CNyjYun4XIw5q/IbG3ctgtNkncvxyasTVc6oPeENPlwcrY2NzDxAmjXy7viXLz4 o5TBMX6kzX1NnIQqfMjD1cVj5rIqg9FfXbRW4FmsgWPNK0jlVMRaLrG4d/459MSJMF/K axBDHmw7Bdqv+jiwhAlIA4ZE74bn0lFJxO6kLz6ktKMScxcNDXKAT9UIS+JzPplTSg9A 5KVA== X-Gm-Message-State: ACrzQf34m+0AptrVoQ/CTUXsGFabZikO/c0KXIu1lIxI+p+5ru01GKxu j7bfQ4NSUd+pBoWdp3mn5z++DA== X-Received: by 2002:a5d:5846:0:b0:22a:f7d2:9045 with SMTP id i6-20020a5d5846000000b0022af7d29045mr1107603wrf.250.1665007976181; Wed, 05 Oct 2022 15:12:56 -0700 (PDT) Received: from rainbowdash.. (cpc152649-stkp13-2-0-cust121.10-2.cable.virginm.net. [86.15.83.122]) by smtp.gmail.com with ESMTPSA id d2-20020adffd82000000b0022e327f849fsm12184437wrr.5.2022.10.05.15.12.54 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 05 Oct 2022 15:12:55 -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 v5 09/10] pwm: dwc: add PWM bit unset in get_state call Date: Wed, 5 Oct 2022 23:12:41 +0100 Message-Id: <20221005221242.470734-10-ben.dooks@sifive.com> X-Mailer: git-send-email 2.35.1 In-Reply-To: <20221005221242.470734-1-ben.dooks@sifive.com> References: <20221005221242.470734-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 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