From: Sean Young <sean@mess.org>
To: Binbin Zhou <zhoubb.aaron@gmail.com>
Cc: "Binbin Zhou" <zhoubinbin@loongson.cn>,
"Huacai Chen" <chenhuacai@loongson.cn>,
"Uwe Kleine-König" <ukleinek@kernel.org>,
"Rob Herring" <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
"Conor Dooley" <conor+dt@kernel.org>,
"Juxin Gao" <gaojuxin@loongson.cn>,
"Huacai Chen" <chenhuacai@kernel.org>,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
"Xuerui Wang" <kernel@xen0n.name>,
loongarch@lists.linux.dev
Subject: Re: [PATCH v6 2/2] pwm: Add Loongson PWM controller support
Date: Thu, 17 Oct 2024 14:35:56 +0100 [thread overview]
Message-ID: <ZxESvFGyUdFZ1N5u@gofer.mess.org> (raw)
In-Reply-To: <CAMpQs4J4GFPkjLV0DHfQ+vti_zX3zU8ihShY2pPgfqhzjPectA@mail.gmail.com>
Hi Binbin,
On Thu, Oct 17, 2024 at 06:24:29PM +0600, Binbin Zhou wrote:
> Hi Sean:
>
> Thanks for your comment.
>
> On Mon, Oct 14, 2024 at 7:32 PM Sean Young <sean@mess.org> wrote:
> >
> > On Thu, Oct 10, 2024 at 04:30:26PM +0800, Binbin Zhou wrote:
> > > This commit adds a generic PWM framework driver for the PWM controller
> > > found on Loongson family chips.
> > >
> > > Co-developed-by: Juxin Gao <gaojuxin@loongson.cn>
> > > Signed-off-by: Juxin Gao <gaojuxin@loongson.cn>
> > > Signed-off-by: Binbin Zhou <zhoubinbin@loongson.cn>
> > > Acked-by: Huacai Chen <chenhuacai@loongson.cn>
> > > ---
> > > MAINTAINERS | 1 +
> > > drivers/pwm/Kconfig | 12 ++
> > > drivers/pwm/Makefile | 1 +
> > > drivers/pwm/pwm-loongson.c | 287 +++++++++++++++++++++++++++++++++++++
> > > 4 files changed, 301 insertions(+)
> > > create mode 100644 drivers/pwm/pwm-loongson.c
> > >
> > > diff --git a/MAINTAINERS b/MAINTAINERS
> > > index 18d2c65c744f..9d033799c6ec 100644
> > > --- a/MAINTAINERS
> > > +++ b/MAINTAINERS
> > > @@ -13388,6 +13388,7 @@ M: Binbin Zhou <zhoubinbin@loongson.cn>
> > > L: linux-pwm@vger.kernel.org
> > > S: Maintained
> > > F: Documentation/devicetree/bindings/pwm/loongson,ls7a-pwm.yaml
> > > +F: drivers/pwm/pwm-loongson.c
> > >
> > > LOONGSON-2 SOC SERIES CLOCK DRIVER
> > > M: Yinbo Zhu <zhuyinbo@loongson.cn>
> > > diff --git a/drivers/pwm/Kconfig b/drivers/pwm/Kconfig
> > > index 0915c1e7df16..ef02a44d83a7 100644
> > > --- a/drivers/pwm/Kconfig
> > > +++ b/drivers/pwm/Kconfig
> > > @@ -351,6 +351,18 @@ config PWM_KEEMBAY
> > > To compile this driver as a module, choose M here: the module
> > > will be called pwm-keembay.
> > >
> > > +config PWM_LOONGSON
> > > + tristate "Loongson PWM support"
> > > + depends on MACH_LOONGSON64 || COMPILE_TEST
> > > + depends on COMMON_CLK
> > > + help
> > > + Generic PWM framework driver for Loongson family.
> > > + It can be found on Loongson-2K series cpus and Loongson LS7A
> > > + bridge chips.
> > > +
> > > + To compile this driver as a module, choose M here: the module
> > > + will be called pwm-loongson.
> > > +
> > > config PWM_LP3943
> > > tristate "TI/National Semiconductor LP3943 PWM support"
> > > depends on MFD_LP3943
> > > diff --git a/drivers/pwm/Makefile b/drivers/pwm/Makefile
> > > index 9081e0c0e9e0..7c18c9be419f 100644
> > > --- a/drivers/pwm/Makefile
> > > +++ b/drivers/pwm/Makefile
> > > @@ -30,6 +30,7 @@ obj-$(CONFIG_PWM_INTEL_LGM) += pwm-intel-lgm.o
> > > obj-$(CONFIG_PWM_IQS620A) += pwm-iqs620a.o
> > > obj-$(CONFIG_PWM_JZ4740) += pwm-jz4740.o
> > > obj-$(CONFIG_PWM_KEEMBAY) += pwm-keembay.o
> > > +obj-$(CONFIG_PWM_LOONGSON) += pwm-loongson.o
> > > obj-$(CONFIG_PWM_LP3943) += pwm-lp3943.o
> > > obj-$(CONFIG_PWM_LPC18XX_SCT) += pwm-lpc18xx-sct.o
> > > obj-$(CONFIG_PWM_LPC32XX) += pwm-lpc32xx.o
> > > diff --git a/drivers/pwm/pwm-loongson.c b/drivers/pwm/pwm-loongson.c
> > > new file mode 100644
> > > index 000000000000..cdd320ed3060
> > > --- /dev/null
> > > +++ b/drivers/pwm/pwm-loongson.c
> > > @@ -0,0 +1,287 @@
> > > +// SPDX-License-Identifier: GPL-2.0-only
> > > +/*
> > > + * Copyright (C) 2017-2024 Loongson Technology Corporation Limited.
> > > + *
> > > + * Loongson PWM driver
> > > + *
> > > + * For Loongson's PWM IP block documentation please refer Chapter 11 of
> > > + * Reference Manual: https://loongson.github.io/LoongArch-Documentation/Loongson-7A1000-usermanual-EN.pdf
> > > + *
> > > + * Author: Juxin Gao <gaojuxin@loongson.cn>
> > > + * Further cleanup and restructuring by:
> > > + * Binbin Zhou <zhoubinbin@loongson.cn>
> > > + *
> > > + * Limitations:
> > > + * - The buffer register value should be written before the CTRL register.
> > > + * - When disabled the output is driven to 0 independent of the configured
> > > + * polarity.
> > > + */
> > > +
> > > +#include <linux/acpi.h>
> > > +#include <linux/clk.h>
> > > +#include <linux/device.h>
> > > +#include <linux/init.h>
> > > +#include <linux/io.h>
> > > +#include <linux/kernel.h>
> > > +#include <linux/module.h>
> > > +#include <linux/platform_device.h>
> > > +#include <linux/pwm.h>
> > > +#include <linux/units.h>
> > > +
> > > +/* Loongson PWM registers */
> > > +#define LOONGSON_PWM_REG_DUTY 0x4 /* Low Pulse Buffer Register */
> > > +#define LOONGSON_PWM_REG_PERIOD 0x8 /* Pulse Period Buffer Register */
> > > +#define LOONGSON_PWM_REG_CTRL 0xc /* Control Register */
> > > +
> > > +/* Control register bits */
> > > +#define LOONGSON_PWM_CTRL_EN BIT(0) /* Counter Enable Bit */
> > > +#define LOONGSON_PWM_CTRL_OE BIT(3) /* Pulse Output Enable Control Bit, Valid Low */
> > > +#define LOONGSON_PWM_CTRL_SINGLE BIT(4) /* Single Pulse Control Bit */
> > > +#define LOONGSON_PWM_CTRL_INTE BIT(5) /* Interrupt Enable Bit */
> > > +#define LOONGSON_PWM_CTRL_INT BIT(6) /* Interrupt Bit */
> > > +#define LOONGSON_PWM_CTRL_RST BIT(7) /* Counter Reset Bit */
> > > +#define LOONGSON_PWM_CTRL_CAPTE BIT(8) /* Measurement Pulse Enable Bit */
> > > +#define LOONGSON_PWM_CTRL_INVERT BIT(9) /* Output flip-flop Enable Bit */
> > > +#define LOONGSON_PWM_CTRL_DZONE BIT(10) /* Anti-dead Zone Enable Bit */
> > > +
> > > +#define LOONGSON_PWM_FREQ_STD (50 * HZ_PER_KHZ)
> > > +
> > > +struct pwm_loongson_suspend_store {
> > > + u32 ctrl;
> > > + u32 duty;
> > > + u32 period;
> > > +};
> > > +
> > > +struct pwm_loongson_ddata {
> > > + struct clk *clk;
> > > + void __iomem *base;
> > > + u64 clk_rate;
> > > + struct pwm_loongson_suspend_store lss;
> > > +};
> > > +
> > > +static inline struct pwm_loongson_ddata *to_pwm_loongson_ddata(struct pwm_chip *chip)
> > > +{
> > > + return pwmchip_get_drvdata(chip);
> > > +}
> > > +
> > > +static inline u32 pwm_loongson_readl(struct pwm_loongson_ddata *ddata, u32 offset)
> > > +{
> > > + return readl(ddata->base + offset);
> > > +}
> > > +
> > > +static inline void pwm_loongson_writel(struct pwm_loongson_ddata *ddata,
> > > + u32 val, u32 offset)
> > > +{
> > > + writel(val, ddata->base + offset);
> > > +}
> > > +
> > > +static int pwm_loongson_set_polarity(struct pwm_chip *chip, struct pwm_device *pwm,
> > > + enum pwm_polarity polarity)
> > > +{
> > > + u16 val;
> > > + struct pwm_loongson_ddata *ddata = to_pwm_loongson_ddata(chip);
> > > +
> > > + val = pwm_loongson_readl(ddata, LOONGSON_PWM_REG_CTRL);
> > > +
> > > + if (polarity == PWM_POLARITY_INVERSED)
> > > + /* Duty cycle defines LOW period of PWM */
> > > + val |= LOONGSON_PWM_CTRL_INVERT;
> > > + else
> > > + /* Duty cycle defines HIGH period of PWM */
> > > + val &= ~LOONGSON_PWM_CTRL_INVERT;
> > > +
> > > + pwm_loongson_writel(ddata, val, LOONGSON_PWM_REG_CTRL);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static void pwm_loongson_disable(struct pwm_chip *chip, struct pwm_device *pwm)
> > > +{
> > > + u32 val;
> > > + struct pwm_loongson_ddata *ddata = to_pwm_loongson_ddata(chip);
> > > +
> > > + val = pwm_loongson_readl(ddata, LOONGSON_PWM_REG_CTRL);
> > > + val &= ~LOONGSON_PWM_CTRL_EN;
> > > + pwm_loongson_writel(ddata, val, LOONGSON_PWM_REG_CTRL);
> > > +}
> > > +
> > > +static int pwm_loongson_enable(struct pwm_chip *chip, struct pwm_device *pwm)
> > > +{
> > > + u32 val;
> > > + struct pwm_loongson_ddata *ddata = to_pwm_loongson_ddata(chip);
> > > +
> > > + val = pwm_loongson_readl(ddata, LOONGSON_PWM_REG_CTRL);
> > > + val |= LOONGSON_PWM_CTRL_EN;
> > > + pwm_loongson_writel(ddata, val, LOONGSON_PWM_REG_CTRL);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static int pwm_loongson_config(struct pwm_chip *chip, struct pwm_device *pwm,
> > > + u64 duty_ns, u64 period_ns)
> > > +{
> > > + u32 duty, period;
> > > + struct pwm_loongson_ddata *ddata = to_pwm_loongson_ddata(chip);
> > > +
> > > + /* duty = duty_ns * ddata->clk_rate / NSEC_PER_SEC */
> > > + duty = mul_u64_u64_div_u64(duty_ns, ddata->clk_rate, NSEC_PER_SEC);
> > > + pwm_loongson_writel(ddata, duty, LOONGSON_PWM_REG_DUTY);
> > > +
> > > + /* period = period_ns * ddata->clk_rate / NSEC_PER_SEC */
> > > + period = mul_u64_u64_div_u64(period_ns, ddata->clk_rate, NSEC_PER_SEC);
> > > + pwm_loongson_writel(ddata, period, LOONGSON_PWM_REG_PERIOD);
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static int pwm_loongson_apply(struct pwm_chip *chip, struct pwm_device *pwm,
> > > + const struct pwm_state *state)
> > > +{
> > > + int ret;
> > > + u64 period, duty_cycle;
> > > + bool enabled = pwm->state.enabled;
> > > +
> > > + if (!state->enabled) {
> > > + if (enabled)
> > > + pwm_loongson_disable(chip, pwm);
> > > + return 0;
> > > + }
> > > +
> > > + ret = pwm_loongson_set_polarity(chip, pwm, state->polarity);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + period = min(state->period, NANOHZ_PER_HZ);
> > > + duty_cycle = min(state->duty_cycle, NANOHZ_PER_HZ);
> > > +
> > > + ret = pwm_loongson_config(chip, pwm, duty_cycle, period);
> > > + if (ret)
> > > + return ret;
> > > +
> > > + if (!enabled && state->enabled)
> > > + ret = pwm_loongson_enable(chip, pwm);
> > > +
> > > + return ret;
> > > +}
> > > +
> > > +static int pwm_loongson_get_state(struct pwm_chip *chip, struct pwm_device *pwm,
> > > + struct pwm_state *state)
> > > +{
> > > + u32 duty, period, ctrl;
> > > + struct pwm_loongson_ddata *ddata = to_pwm_loongson_ddata(chip);
> > > +
> > > + duty = pwm_loongson_readl(ddata, LOONGSON_PWM_REG_DUTY);
> > > + period = pwm_loongson_readl(ddata, LOONGSON_PWM_REG_PERIOD);
> > > + ctrl = pwm_loongson_readl(ddata, LOONGSON_PWM_REG_CTRL);
> > > +
> > > + /* duty & period have a max of 2^32, so we can't overflow */
> > > + state->duty_cycle = DIV64_U64_ROUND_UP((u64)duty * NSEC_PER_SEC, ddata->clk_rate);
> > > + state->period = DIV64_U64_ROUND_UP((u64)period * NSEC_PER_SEC, ddata->clk_rate);
> > > + state->polarity = (ctrl & LOONGSON_PWM_CTRL_INVERT) ? PWM_POLARITY_INVERSED :
> > > + PWM_POLARITY_NORMAL;
> > > + state->enabled = (ctrl & LOONGSON_PWM_CTRL_EN) ? true : false;
> > > +
> > > + return 0;
> > > +}
> > > +
> > > +static const struct pwm_ops pwm_loongson_ops = {
> > > + .apply = pwm_loongson_apply,
> > > + .get_state = pwm_loongson_get_state,
> > > +};
> > > +
> > > +static int pwm_loongson_probe(struct platform_device *pdev)
> > > +{
> > > + int ret;
> > > + struct pwm_chip *chip;
> > > + struct pwm_loongson_ddata *ddata;
> > > + struct device *dev = &pdev->dev;
> > > +
> > > + chip = devm_pwmchip_alloc(dev, 1, sizeof(*ddata));
> > > + if (IS_ERR(chip))
> > > + return PTR_ERR(chip);
> > > + ddata = to_pwm_loongson_ddata(chip);
> > > +
> > > + ddata->base = devm_platform_ioremap_resource(pdev, 0);
> > > + if (IS_ERR(ddata->base))
> > > + return PTR_ERR(ddata->base);
> > > +
> > > + if (!has_acpi_companion(dev)) {
> > > + ddata->clk = devm_clk_get_enabled(dev, NULL);
> > > + if (IS_ERR(ddata->clk))
> > > + return dev_err_probe(dev, PTR_ERR(ddata->clk),
> > > + "failed to get pwm clock\n");
> > > + ddata->clk_rate = clk_get_rate(ddata->clk);
> > > + } else {
> > > + ddata->clk_rate = LOONGSON_PWM_FREQ_STD;
> > > + }
> > > +
> > > + chip->ops = &pwm_loongson_ops;
> >
> > I think you can add here:
> >
> > chip->atomic = true;
> >
> > As far as I can see, the driver does not do any sleeping operations
> > in pwm_loongson_apply(). This probably should be tested with
> > CONFIG_PWM_DEBUG and CONFIG_DEBUG_ATOMIC_SLEEP just to be sure.
>
> I'm a bit confused.
>
> With CONFIG_PWM_DEBUG and CONFIG_DEBUG_ATOMIC_SLEEP, I did some
> suspend/resume tests, but there is no relevant error output, including
> something like "BUG: sleeping function called from invalid context...
> ".
That's great, that means everything is working as expected in atomic
context.
> Does chip->atomic still need to be set?
Yes, it does. This means that the function pwm_apply_atomic() can be used
with the pwm. Otherwise, this function will fail.
Thank you
Sean
prev parent reply other threads:[~2024-10-17 13:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-10 8:30 [PATCH v6 0/2] pwm: Introduce pwm driver for the Loongson family chips Binbin Zhou
2024-10-10 8:30 ` [PATCH v6 1/2] dt-bindings: pwm: Add Loongson PWM controller Binbin Zhou
2024-10-10 8:30 ` [PATCH v6 2/2] pwm: Add Loongson PWM controller support Binbin Zhou
2024-10-14 13:32 ` Sean Young
2024-10-17 12:24 ` Binbin Zhou
2024-10-17 13:35 ` Sean Young [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ZxESvFGyUdFZ1N5u@gofer.mess.org \
--to=sean@mess.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gaojuxin@loongson.cn \
--cc=kernel@xen0n.name \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-pwm@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=robh+dt@kernel.org \
--cc=ukleinek@kernel.org \
--cc=zhoubb.aaron@gmail.com \
--cc=zhoubinbin@loongson.cn \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox