From: Thierry Reding <thierry.reding@gmail.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-pwm@vger.kernel.org, linux-sh@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/2] pwm: Add support for R-Car PWM Timer
Date: Wed, 19 Aug 2015 12:07:33 +0200 [thread overview]
Message-ID: <20150819100732.GC26627@ulmo> (raw)
In-Reply-To: <1439957639-4816-3-git-send-email-yoshihiro.shimoda.uh@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 3624 bytes --]
On Wed, Aug 19, 2015 at 01:13:59PM +0900, Yoshihiro Shimoda wrote:
> This patch adds support for R-Car SoCs PWM Timer. The PWM timer of
> R-Car H2 has 7 channels. So, we can use the channels if we describe
> device tree nodes.
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> drivers/pwm/Kconfig | 11 ++
> drivers/pwm/Makefile | 1 +
> drivers/pwm/pwm-rcar.c | 265 +++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 277 insertions(+)
> create mode 100644 drivers/pwm/pwm-rcar.c
Found a couple more things. No need to respin for any of these, I can
make the changes when applying, but I'd like confirmation on a couple
of things below.
[...]
> diff --git a/drivers/pwm/pwm-rcar.c b/drivers/pwm/pwm-rcar.c
[...]
> +static int rcar_pwm_set_counter(struct rcar_pwm_chip *rp, int div, int duty_ns,
> + int period_ns)
> +{
> + unsigned long long one_cycle, tmp; /* 0.01 nanoseconds */
I'm not quite sure why you need the extra multiplication and division by
100 here. Is this for extra accuracy?
> + unsigned long clk_rate = clk_get_rate(rp->clk);
> + u32 cyc, ph;
> +
> + one_cycle = (unsigned long long)NSEC_PER_SEC * 100ULL * (1 << div);
> + do_div(one_cycle, clk_rate);
> +
> + tmp = period_ns * 100ULL;
> + do_div(tmp, one_cycle);
> + cyc = (tmp << RCAR_PWMCNT_CYC0_SHIFT) & RCAR_PWMCNT_CYC0_MASK;
> +
> + tmp = duty_ns * 100ULL;
> + do_div(tmp, one_cycle);
> + ph = tmp & RCAR_PWMCNT_PH0_MASK;
> +
> + /* Avoid prohibited setting */
> + if (cyc != 0 && ph != 0) {
> + rcar_pwm_write(rp, cyc | ph, RCAR_PWMCNT);
> + return 0;
> + } else {
> + return -EINVAL;
> + }
I think the ordering here is unintuitive, better would be:
if (cyc == 0 || ph == 0)
return -EINVAL;
rcar_pwm_write(rp, cyc | ph, RCAR_PWMCNT);
return 0;
> +static int rcar_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
> + int duty_ns, int period_ns)
> +{
> + struct rcar_pwm_chip *rp = to_rcar_pwm_chip(chip);
> + int div = rcar_pwm_get_clock_division(rp, period_ns);
> + int ret;
> +
> + if (div < 0)
> + return div;
> +
> + /* Let the core driver set pwm->period if disabled and duty_ns == 0 */
> + if (!test_bit(PWMF_ENABLED, &pwm->flags) && !duty_ns)
> + return 0;
> +
> + rcar_pwm_bit_modify(rp, RCAR_PWMCR_SYNC, RCAR_PWMCR_SYNC, RCAR_PWMCR);
> + ret = rcar_pwm_set_counter(rp, div, duty_ns, period_ns);
> + rcar_pwm_set_clock_control(rp, div);
> + rcar_pwm_bit_modify(rp, RCAR_PWMCR_SYNC, 0, RCAR_PWMCR);
Just making sure: is it correct to execute the above two lines even if
ret < 0?
> +static int rcar_pwm_probe(struct platform_device *pdev)
> +{
> + struct rcar_pwm_chip *rcar_pwm;
> + struct resource *res;
> + int ret;
> +
> + rcar_pwm = devm_kzalloc(&pdev->dev, sizeof(*rcar_pwm), GFP_KERNEL);
> + if (rcar_pwm == NULL)
> + return -ENOMEM;
> +
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + rcar_pwm->base = devm_ioremap_resource(&pdev->dev, res);
> + if (IS_ERR(rcar_pwm->base))
> + return PTR_ERR(rcar_pwm->base);
> +
> + rcar_pwm->clk = devm_clk_get(&pdev->dev, NULL);
> + if (IS_ERR(rcar_pwm->clk)) {
> + dev_err(&pdev->dev, "cannot get clock\n");
> + return PTR_ERR(rcar_pwm->clk);
> + }
> +
> + platform_set_drvdata(pdev, rcar_pwm);
> +
> + rcar_pwm->chip.dev = &pdev->dev;
> + rcar_pwm->chip.ops = &rcar_pwm_ops;
> + rcar_pwm->chip.of_xlate = of_pwm_xlate_with_flags;
This seems to be missing a:
rcar_pwm->chip.of_pwm_n_cells = 3;
?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux-pwm@vger.kernel.org, linux-sh@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 2/2] pwm: Add support for R-Car PWM Timer
Date: Wed, 19 Aug 2015 10:07:33 +0000 [thread overview]
Message-ID: <20150819100732.GC26627@ulmo> (raw)
In-Reply-To: <1439957639-4816-3-git-send-email-yoshihiro.shimoda.uh@renesas.com>
[-- Attachment #1: Type: text/plain, Size: 3624 bytes --]
On Wed, Aug 19, 2015 at 01:13:59PM +0900, Yoshihiro Shimoda wrote:
> This patch adds support for R-Car SoCs PWM Timer. The PWM timer of
> R-Car H2 has 7 channels. So, we can use the channels if we describe
> device tree nodes.
>
> Signed-off-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
> Reviewed-by: Simon Horman <horms+renesas@verge.net.au>
> ---
> drivers/pwm/Kconfig | 11 ++
> drivers/pwm/Makefile | 1 +
> drivers/pwm/pwm-rcar.c | 265 +++++++++++++++++++++++++++++++++++++++++++++++++
> 3 files changed, 277 insertions(+)
> create mode 100644 drivers/pwm/pwm-rcar.c
Found a couple more things. No need to respin for any of these, I can
make the changes when applying, but I'd like confirmation on a couple
of things below.
[...]
> diff --git a/drivers/pwm/pwm-rcar.c b/drivers/pwm/pwm-rcar.c
[...]
> +static int rcar_pwm_set_counter(struct rcar_pwm_chip *rp, int div, int duty_ns,
> + int period_ns)
> +{
> + unsigned long long one_cycle, tmp; /* 0.01 nanoseconds */
I'm not quite sure why you need the extra multiplication and division by
100 here. Is this for extra accuracy?
> + unsigned long clk_rate = clk_get_rate(rp->clk);
> + u32 cyc, ph;
> +
> + one_cycle = (unsigned long long)NSEC_PER_SEC * 100ULL * (1 << div);
> + do_div(one_cycle, clk_rate);
> +
> + tmp = period_ns * 100ULL;
> + do_div(tmp, one_cycle);
> + cyc = (tmp << RCAR_PWMCNT_CYC0_SHIFT) & RCAR_PWMCNT_CYC0_MASK;
> +
> + tmp = duty_ns * 100ULL;
> + do_div(tmp, one_cycle);
> + ph = tmp & RCAR_PWMCNT_PH0_MASK;
> +
> + /* Avoid prohibited setting */
> + if (cyc != 0 && ph != 0) {
> + rcar_pwm_write(rp, cyc | ph, RCAR_PWMCNT);
> + return 0;
> + } else {
> + return -EINVAL;
> + }
I think the ordering here is unintuitive, better would be:
if (cyc == 0 || ph == 0)
return -EINVAL;
rcar_pwm_write(rp, cyc | ph, RCAR_PWMCNT);
return 0;
> +static int rcar_pwm_config(struct pwm_chip *chip, struct pwm_device *pwm,
> + int duty_ns, int period_ns)
> +{
> + struct rcar_pwm_chip *rp = to_rcar_pwm_chip(chip);
> + int div = rcar_pwm_get_clock_division(rp, period_ns);
> + int ret;
> +
> + if (div < 0)
> + return div;
> +
> + /* Let the core driver set pwm->period if disabled and duty_ns == 0 */
> + if (!test_bit(PWMF_ENABLED, &pwm->flags) && !duty_ns)
> + return 0;
> +
> + rcar_pwm_bit_modify(rp, RCAR_PWMCR_SYNC, RCAR_PWMCR_SYNC, RCAR_PWMCR);
> + ret = rcar_pwm_set_counter(rp, div, duty_ns, period_ns);
> + rcar_pwm_set_clock_control(rp, div);
> + rcar_pwm_bit_modify(rp, RCAR_PWMCR_SYNC, 0, RCAR_PWMCR);
Just making sure: is it correct to execute the above two lines even if
ret < 0?
> +static int rcar_pwm_probe(struct platform_device *pdev)
> +{
> + struct rcar_pwm_chip *rcar_pwm;
> + struct resource *res;
> + int ret;
> +
> + rcar_pwm = devm_kzalloc(&pdev->dev, sizeof(*rcar_pwm), GFP_KERNEL);
> + if (rcar_pwm == NULL)
> + return -ENOMEM;
> +
> + res = platform_get_resource(pdev, IORESOURCE_MEM, 0);
> + rcar_pwm->base = devm_ioremap_resource(&pdev->dev, res);
> + if (IS_ERR(rcar_pwm->base))
> + return PTR_ERR(rcar_pwm->base);
> +
> + rcar_pwm->clk = devm_clk_get(&pdev->dev, NULL);
> + if (IS_ERR(rcar_pwm->clk)) {
> + dev_err(&pdev->dev, "cannot get clock\n");
> + return PTR_ERR(rcar_pwm->clk);
> + }
> +
> + platform_set_drvdata(pdev, rcar_pwm);
> +
> + rcar_pwm->chip.dev = &pdev->dev;
> + rcar_pwm->chip.ops = &rcar_pwm_ops;
> + rcar_pwm->chip.of_xlate = of_pwm_xlate_with_flags;
This seems to be missing a:
rcar_pwm->chip.of_pwm_n_cells = 3;
?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-08-19 10:08 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-19 4:13 [PATCH v6 0/2] pwm: Add support for R-Car PWM Timer Yoshihiro Shimoda
2015-08-19 4:13 ` Yoshihiro Shimoda
2015-08-19 4:13 ` [PATCH v6 1/2] pwm: Add device tree binding document " Yoshihiro Shimoda
2015-08-19 4:13 ` Yoshihiro Shimoda
2015-08-19 4:13 ` [PATCH v6 2/2] pwm: Add support " Yoshihiro Shimoda
2015-08-19 4:13 ` Yoshihiro Shimoda
2015-08-19 10:07 ` Thierry Reding [this message]
2015-08-19 10:07 ` Thierry Reding
2015-08-19 11:00 ` Yoshihiro Shimoda
2015-08-19 11:00 ` Yoshihiro Shimoda
2015-09-15 10:00 ` Yoshihiro Shimoda
2015-09-30 8:49 ` Yoshihiro Shimoda
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=20150819100732.GC26627@ulmo \
--to=thierry.reding@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.