From: Boris Brezillon <boris.brezillon@free-electrons.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 02/24] pwm: use pwm_get_xxx() helpers where appropriate
Date: Mon, 16 Nov 2015 18:06:46 +0000 [thread overview]
Message-ID: <20151116190646.1d5ba16e@bbrezillon> (raw)
In-Reply-To: <CAGhQ9VwEuwazF5Kdw=9R60EovVoiwen6fXiVjL+=EddXPYVGAg@mail.gmail.com>
Hi Joachim,
On Mon, 16 Nov 2015 18:46:44 +0100
Joachim Eastwood <manabian@gmail.com> wrote:
> Hi Boris
>
> (Adding Ariel for pwm-lpc18xx-sct)
>
> On 16 November 2015 at 09:56, Boris Brezillon
> <boris.brezillon@free-electrons.com> wrote:
> > Use pwm_get_xxx() helpers instead of directly accessing the pwm->xxx field.
> > Doing that will ease adaptation of the PWM framework to support atomic
> > update.
> >
> > Signed-off-by: Boris Brezillon <boris.brezillon@free-electrons.com>
> > ---
> > Patch generated with the following coccinelle script:
> >
> > --->8---
> > virtual patch
> >
> > @@
> > struct pwm_device *p;
> > expression e;
> > @@
> > (
> > -(p)->polarity = e;
> > +pwm_set_polarity((p), e);
> > |
> > -(p)->polarity
> > +pwm_get_polarity((p))
> > |
> > -(p)->period = e;
> > +pwm_set_period((p), e);
> > |
> > -(p)->period
> > +pwm_get_period((p))
> > |
> > -(p)->duty_cycle = e;
> > +pwm_set_duty_cycle((p), e);
> > |
> > -(p)->duty_cycle
> > +pwm_get_duty_cycle((p))
> > )
> > --->8---
> > ---
> > drivers/pwm/pwm-crc.c | 2 +-
> > drivers/pwm/pwm-lpc18xx-sct.c | 2 +-
> > 2 files changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/pwm/pwm-crc.c b/drivers/pwm/pwm-crc.c
> > index 7101c70..2f88543 100644
> > --- a/drivers/pwm/pwm-crc.c
> > +++ b/drivers/pwm/pwm-crc.c
> > @@ -75,7 +75,7 @@ static int crc_pwm_config(struct pwm_chip *c, struct pwm_device *pwm,
> > return -EINVAL;
> > }
> >
> > - if (pwm->period != period_ns) {
> > + if (pwm_get_period((pwm)) != period_ns) {
> > int clk_div;
> >
> > /* changing the clk divisor, need to disable fisrt */
> > diff --git a/drivers/pwm/pwm-lpc18xx-sct.c b/drivers/pwm/pwm-lpc18xx-sct.c
> > index 9163085..091fa13 100644
> > --- a/drivers/pwm/pwm-lpc18xx-sct.c
> > +++ b/drivers/pwm/pwm-lpc18xx-sct.c
> > @@ -249,7 +249,7 @@ static int lpc18xx_pwm_enable(struct pwm_chip *chip, struct pwm_device *pwm)
> > LPC18XX_PWM_EVSTATEMSK(lpc18xx_data->duty_event),
> > LPC18XX_PWM_EVSTATEMSK_ALL);
> >
> > - if (pwm->polarity = PWM_POLARITY_NORMAL) {
> > + if (pwm_get_polarity((pwm)) = PWM_POLARITY_NORMAL) {
>
> What is the deal with the double parentheses?
>
> Think I saw that in some of the other patches as well.
It comes from a typo in my coccinelle script. I already fixed it and
regenerated the faulty patches, so please ignore this aspect while
reviewing (this will be addressed in the next version).
Thanks,
Boris
--
Boris Brezillon, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-11-16 18:06 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-16 8:56 [PATCH v4 00/24] pwm: add support for atomic update Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 01/24] pwm: rcar: make use of pwm_is_enabled() Boris Brezillon
2016-03-16 14:30 ` Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 02/24] pwm: use pwm_get_xxx() helpers where appropriate Boris Brezillon
2015-11-16 17:46 ` Joachim Eastwood
2015-11-16 18:06 ` Boris Brezillon [this message]
2015-11-16 8:56 ` [PATCH v4 03/24] clk: " Boris Brezillon
2015-12-30 21:03 ` Michael Turquette
2015-11-16 8:56 ` [PATCH v4 04/24] hwmon: pwm-fan: " Boris Brezillon
2015-11-16 15:59 ` Guenter Roeck
2015-11-16 16:53 ` Boris Brezillon
2015-11-16 17:00 ` Guenter Roeck
2015-11-16 8:56 ` [PATCH v4 05/24] misc: max77693-haptic: " Boris Brezillon
2015-11-16 13:10 ` Krzysztof Kozlowski
2015-11-16 13:55 ` Boris Brezillon
2015-11-16 15:55 ` Guenter Roeck
2015-11-16 16:00 ` Boris Brezillon
2015-11-17 17:32 ` Dmitry Torokhov
2015-11-16 8:56 ` [PATCH v4 06/24] pwm: introduce default period and polarity concepts Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 07/24] pwm: use pwm_get/set_default_xxx() helpers where appropriate Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 08/24] leds: " Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 09/24] regulator: " Boris Brezillon
2015-11-16 10:55 ` Mark Brown
2015-11-16 12:23 ` Boris Brezillon
2015-11-16 18:42 ` Mark Brown
2015-11-16 19:28 ` Boris Brezillon
2015-12-02 10:37 ` Boris Brezillon
2015-12-30 11:01 ` Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 10/24] backlight: " Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 11/24] fbdev: " Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 12/24] misc: max77693: " Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 13/24] hwmon: pwm-fan: " Boris Brezillon
2015-11-16 16:00 ` Guenter Roeck
2015-11-16 8:56 ` [PATCH v4 14/24] clk: pwm: " Boris Brezillon
2015-12-30 21:05 ` Michael Turquette
2015-11-16 8:56 ` [PATCH v4 15/24] pwm: define a new pwm_state struct Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 16/24] pwm: move the enabled/disabled info to " Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 17/24] backlight: pwm_bl: remove useless call to pwm_set_period Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 18/24] pwm: declare a default PWM state Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 19/24] pwm: add the PWM initial state retrieval infra Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 20/24] pwm: add the core infrastructure to allow atomic update Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 21/24] pwm: add information about polarity, duty cycle and period to debugfs Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 22/24] pwm: rockchip: add initial state retrieval Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 23/24] pwm: rockchip: add support for atomic update Boris Brezillon
2015-11-16 8:56 ` [PATCH v4 24/24] regulator: pwm: properly initialize the ->state field Boris Brezillon
2015-11-16 14:45 ` [PATCH v4 00/24] pwm: add support for atomic update Heiko Stübner
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=20151116190646.1d5ba16e@bbrezillon \
--to=boris.brezillon@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
/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;
as well as URLs for NNTP newsgroup(s).