From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC PATCH 11/15] pwm: add the core infrastructure to allow atomic update
Date: Mon, 20 Jul 2015 12:04:51 +0200 [thread overview]
Message-ID: <20150720100451.GW29614@ulmo> (raw)
In-Reply-To: <20150720114827.2e5d52a5@bbrezillon>
On Mon, Jul 20, 2015 at 11:48:27AM +0200, Boris Brezillon wrote:
> On Mon, 20 Jul 2015 10:59:40 +0200 Thierry Reding <thierry.reding@gmail.com> wrote:
> > On Wed, Jul 01, 2015 at 10:21:57AM +0200, Boris Brezillon wrote:
[...]
> > > +int pwm_apply_state(struct pwm_device *pwm, const struct pwm_state *state)
> > > +{
> > > + int err = 0;
> > > +
> > > + if (!pwm)
> > > + return -EINVAL;
> > > +
> > > + if (!memcmp(state, &pwm->state, sizeof(*state)))
> > > + return 0;
> > > +
> > > + if (pwm->chip->ops->apply) {
> > > + err = pwm->chip->ops->apply(pwm->chip, pwm, state);
> > > + if (!err)
> > > + pwm->state = *state;
> >
> > Maybe we want pwm_set_state() for this?
>
> I'm not opposed to the addition of the pwm_set_state() function as long
> as it's a private one: I don't want to let PMW drivers or users mess up
> with the current PWM state.
Yeah, it could be a static function in core.c. What I want to avoid is
having to change a bunch of code if ever state assignment becomes
something other than merely copying a structure.
[...]
> > > diff --git a/include/linux/pwm.h b/include/linux/pwm.h
> > > index b47244a..7e99679 100644
> > > --- a/include/linux/pwm.h
> > > +++ b/include/linux/pwm.h
> > > @@ -151,6 +151,29 @@ static inline enum pwm_polarity pwm_get_polarity(const struct pwm_device *pwm)
> > > return pwm ? pwm->state.polarity : PWM_POLARITY_NORMAL;
> > > }
> > >
> > > +/*
> > > + * pwm_apply_state - apply a new state to the PWM device
> > > + */
> > > +int pwm_apply_state(struct pwm_device *pwm, const struct pwm_state *state);
> >
> > If you add kerneldoc, please add it properly. It should start with /**
> > and you need to list at least the parameters and return value.
>
> Yes, I'll fix that.
> BTW, I remember that you were expecting another name for this function
> (pwm_update IIRC).
I don't mind the pwm_apply_state() name very much. It's pretty accurate
with regards to what it does.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150720/ebd802e9/attachment.sig>
WARNING: multiple messages have this Message-ID (diff)
From: Thierry Reding <thierry.reding@gmail.com>
To: Boris Brezillon <boris.brezillon@free-electrons.com>
Cc: linux-pwm@vger.kernel.org, Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>,
Bryan Wu <cooloney@gmail.com>, Richard Purdie <rpurdie@rpsys.net>,
Jacek Anaszewski <j.anaszewski@samsung.com>,
linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Jean-Christophe Plagniol-Villard <plagnioj@jcrosoft.com>,
Tomi Valkeinen <tomi.valkeinen@ti.com>,
linux-fbdev@vger.kernel.org,
Stephen Warren <swarren@wwwdotorg.org>,
Alexandre Courbot <gnurou@gmail.com>,
linux-tegra@vger.kernel.org,
Maxime Ripard <maxime.ripard@free-electrons.com>,
Jingoo Han <jingoohan1@gmail.com>,
Lee Jones <lee.jones@linaro.org>,
Doug Anderson <dianders@google.com>
Subject: Re: [RFC PATCH 11/15] pwm: add the core infrastructure to allow atomic update
Date: Mon, 20 Jul 2015 12:04:51 +0200 [thread overview]
Message-ID: <20150720100451.GW29614@ulmo> (raw)
In-Reply-To: <20150720114827.2e5d52a5@bbrezillon>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
On Mon, Jul 20, 2015 at 11:48:27AM +0200, Boris Brezillon wrote:
> On Mon, 20 Jul 2015 10:59:40 +0200 Thierry Reding <thierry.reding@gmail.com> wrote:
> > On Wed, Jul 01, 2015 at 10:21:57AM +0200, Boris Brezillon wrote:
[...]
> > > +int pwm_apply_state(struct pwm_device *pwm, const struct pwm_state *state)
> > > +{
> > > + int err = 0;
> > > +
> > > + if (!pwm)
> > > + return -EINVAL;
> > > +
> > > + if (!memcmp(state, &pwm->state, sizeof(*state)))
> > > + return 0;
> > > +
> > > + if (pwm->chip->ops->apply) {
> > > + err = pwm->chip->ops->apply(pwm->chip, pwm, state);
> > > + if (!err)
> > > + pwm->state = *state;
> >
> > Maybe we want pwm_set_state() for this?
>
> I'm not opposed to the addition of the pwm_set_state() function as long
> as it's a private one: I don't want to let PMW drivers or users mess up
> with the current PWM state.
Yeah, it could be a static function in core.c. What I want to avoid is
having to change a bunch of code if ever state assignment becomes
something other than merely copying a structure.
[...]
> > > diff --git a/include/linux/pwm.h b/include/linux/pwm.h
> > > index b47244a..7e99679 100644
> > > --- a/include/linux/pwm.h
> > > +++ b/include/linux/pwm.h
> > > @@ -151,6 +151,29 @@ static inline enum pwm_polarity pwm_get_polarity(const struct pwm_device *pwm)
> > > return pwm ? pwm->state.polarity : PWM_POLARITY_NORMAL;
> > > }
> > >
> > > +/*
> > > + * pwm_apply_state - apply a new state to the PWM device
> > > + */
> > > +int pwm_apply_state(struct pwm_device *pwm, const struct pwm_state *state);
> >
> > If you add kerneldoc, please add it properly. It should start with /**
> > and you need to list at least the parameters and return value.
>
> Yes, I'll fix that.
> BTW, I remember that you were expecting another name for this function
> (pwm_update IIRC).
I don't mind the pwm_apply_state() name very much. It's pretty accurate
with regards to what it does.
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: linux-arm-kernel@lists.infradead.org
Subject: Re: [RFC PATCH 11/15] pwm: add the core infrastructure to allow atomic update
Date: Mon, 20 Jul 2015 10:04:51 +0000 [thread overview]
Message-ID: <20150720100451.GW29614@ulmo> (raw)
In-Reply-To: <20150720114827.2e5d52a5@bbrezillon>
[-- Attachment #1: Type: text/plain, Size: 2001 bytes --]
On Mon, Jul 20, 2015 at 11:48:27AM +0200, Boris Brezillon wrote:
> On Mon, 20 Jul 2015 10:59:40 +0200 Thierry Reding <thierry.reding@gmail.com> wrote:
> > On Wed, Jul 01, 2015 at 10:21:57AM +0200, Boris Brezillon wrote:
[...]
> > > +int pwm_apply_state(struct pwm_device *pwm, const struct pwm_state *state)
> > > +{
> > > + int err = 0;
> > > +
> > > + if (!pwm)
> > > + return -EINVAL;
> > > +
> > > + if (!memcmp(state, &pwm->state, sizeof(*state)))
> > > + return 0;
> > > +
> > > + if (pwm->chip->ops->apply) {
> > > + err = pwm->chip->ops->apply(pwm->chip, pwm, state);
> > > + if (!err)
> > > + pwm->state = *state;
> >
> > Maybe we want pwm_set_state() for this?
>
> I'm not opposed to the addition of the pwm_set_state() function as long
> as it's a private one: I don't want to let PMW drivers or users mess up
> with the current PWM state.
Yeah, it could be a static function in core.c. What I want to avoid is
having to change a bunch of code if ever state assignment becomes
something other than merely copying a structure.
[...]
> > > diff --git a/include/linux/pwm.h b/include/linux/pwm.h
> > > index b47244a..7e99679 100644
> > > --- a/include/linux/pwm.h
> > > +++ b/include/linux/pwm.h
> > > @@ -151,6 +151,29 @@ static inline enum pwm_polarity pwm_get_polarity(const struct pwm_device *pwm)
> > > return pwm ? pwm->state.polarity : PWM_POLARITY_NORMAL;
> > > }
> > >
> > > +/*
> > > + * pwm_apply_state - apply a new state to the PWM device
> > > + */
> > > +int pwm_apply_state(struct pwm_device *pwm, const struct pwm_state *state);
> >
> > If you add kerneldoc, please add it properly. It should start with /**
> > and you need to list at least the parameters and return value.
>
> Yes, I'll fix that.
> BTW, I remember that you were expecting another name for this function
> (pwm_update IIRC).
I don't mind the pwm_apply_state() name very much. It's pretty accurate
with regards to what it does.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2015-07-20 10:04 UTC|newest]
Thread overview: 204+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 8:21 [RFC PATCH 00/15] pwm: add support for atomic update Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` [RFC PATCH 01/15] pwm: add the pwm_is_enabled() helper Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 7:47 ` Thierry Reding
2015-07-20 7:47 ` Thierry Reding
2015-07-20 7:47 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 02/15] pwm: fix pwm_get_period and pwm_get_duty_cycle prototypes Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 7:50 ` Thierry Reding
2015-07-20 7:50 ` Thierry Reding
2015-07-20 7:50 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 03/15] pwm: add pwm_get_polarity helper function Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 7:52 ` Thierry Reding
2015-07-20 7:52 ` Thierry Reding
2015-07-20 7:52 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 04/15] pwm: make use of pwm_get_xxx helpers where appropriate Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 8:00 ` Thierry Reding
2015-07-20 8:00 ` Thierry Reding
2015-07-20 8:00 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 05/15] pwm: introduce default period and polarity concepts Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-02 6:44 ` Uwe Kleine-König
2015-07-02 6:44 ` Uwe Kleine-König
2015-07-02 6:44 ` Uwe Kleine-König
2015-07-02 7:49 ` Boris Brezillon
2015-07-02 7:49 ` Boris Brezillon
2015-07-02 7:49 ` Boris Brezillon
2015-07-20 8:03 ` Thierry Reding
2015-07-20 8:03 ` Thierry Reding
2015-07-20 8:03 ` Thierry Reding
2015-07-20 8:14 ` Boris Brezillon
2015-07-20 8:14 ` Boris Brezillon
2015-07-20 8:14 ` Boris Brezillon
2015-07-20 8:22 ` Thierry Reding
2015-07-20 8:22 ` Thierry Reding
2015-07-20 8:22 ` Thierry Reding
2015-07-20 8:32 ` Boris Brezillon
2015-07-20 8:32 ` Boris Brezillon
2015-07-20 8:32 ` Boris Brezillon
2015-07-01 8:21 ` [RFC PATCH 06/15] pwm: define a new pwm_state struct Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 8:04 ` Thierry Reding
2015-07-20 8:04 ` Thierry Reding
2015-07-20 8:04 ` Thierry Reding
2015-07-20 10:01 ` Boris Brezillon
2015-07-20 10:01 ` Boris Brezillon
2015-07-20 10:01 ` Boris Brezillon
2015-07-20 10:09 ` Thierry Reding
2015-07-20 10:09 ` Thierry Reding
2015-07-20 10:09 ` Thierry Reding
2015-07-20 10:12 ` Boris Brezillon
2015-07-20 10:12 ` Boris Brezillon
2015-07-20 10:12 ` Boris Brezillon
2015-07-01 8:21 ` [RFC PATCH 07/15] pwm: move the enabled/disabled info to " Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 8:11 ` Thierry Reding
2015-07-20 8:11 ` Thierry Reding
2015-07-20 8:11 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 08/15] backlight: pwm_bl: remove useless call to pwm_set_period Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 8:16 ` Thierry Reding
2015-07-20 8:16 ` Thierry Reding
2015-07-20 8:16 ` Thierry Reding
2015-07-20 8:21 ` Boris Brezillon
2015-07-20 8:21 ` Boris Brezillon
2015-07-20 8:21 ` Boris Brezillon
2015-07-20 8:36 ` Thierry Reding
2015-07-20 8:36 ` Thierry Reding
2015-07-20 8:36 ` Thierry Reding
2015-07-20 8:50 ` Boris Brezillon
2015-07-20 8:50 ` Boris Brezillon
2015-07-20 8:50 ` Boris Brezillon
2015-07-20 9:10 ` Thierry Reding
2015-07-20 9:10 ` Thierry Reding
2015-07-20 9:10 ` Thierry Reding
2015-07-20 9:57 ` Boris Brezillon
2015-07-20 9:57 ` Boris Brezillon
2015-07-20 9:57 ` Boris Brezillon
2015-07-20 10:01 ` Thierry Reding
2015-07-20 10:01 ` Thierry Reding
2015-07-20 10:01 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 09/15] pwm: declare a default PWM state Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` [RFC PATCH 10/15] pwm: add the PWM initial state retrieval infra Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 9:01 ` Thierry Reding
2015-07-20 9:01 ` Thierry Reding
2015-07-20 9:01 ` Thierry Reding
2015-07-20 9:42 ` Boris Brezillon
2015-07-20 9:42 ` Boris Brezillon
2015-07-20 9:42 ` Boris Brezillon
2015-07-01 8:21 ` [RFC PATCH 11/15] pwm: add the core infrastructure to allow atomic update Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-20 8:59 ` Thierry Reding
2015-07-20 8:59 ` Thierry Reding
2015-07-20 8:59 ` Thierry Reding
2015-07-20 9:48 ` Boris Brezillon
2015-07-20 9:48 ` Boris Brezillon
2015-07-20 9:48 ` Boris Brezillon
2015-07-20 10:04 ` Thierry Reding [this message]
2015-07-20 10:04 ` Thierry Reding
2015-07-20 10:04 ` Thierry Reding
2015-07-01 8:21 ` [RFC PATCH 12/15] pwm: rockchip: add initial state retrieval Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 21:44 ` Heiko Stübner
2015-07-01 21:44 ` Heiko Stübner
2015-07-01 21:44 ` Heiko Stübner
2015-07-02 7:46 ` Boris Brezillon
2015-07-02 7:46 ` Boris Brezillon
2015-07-02 7:46 ` Boris Brezillon
2015-07-01 8:21 ` [RFC PATCH 13/15] pwm: rockchip: add support for atomic update Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 8:21 ` Boris Brezillon
2015-07-01 21:48 ` Heiko Stübner
2015-07-01 21:48 ` Heiko Stübner
2015-07-01 21:48 ` Heiko Stübner
2015-07-02 7:43 ` Boris Brezillon
2015-07-02 7:43 ` Boris Brezillon
2015-07-02 7:43 ` Boris Brezillon
2015-07-01 8:22 ` [RFC PATCH 14/15] regulator: pwm: implement ->enable(), ->disable() and ->is_enabled methods Boris Brezillon
2015-07-01 8:22 ` Boris Brezillon
2015-07-01 8:22 ` Boris Brezillon
2015-07-01 11:58 ` Heiko Stübner
2015-07-01 11:58 ` Heiko Stübner
2015-07-01 11:58 ` Heiko Stübner
2015-07-01 12:05 ` Boris Brezillon
2015-07-01 12:05 ` Boris Brezillon
2015-07-01 12:05 ` Boris Brezillon
2015-07-01 12:08 ` Heiko Stübner
2015-07-01 12:08 ` Heiko Stübner
2015-07-01 12:08 ` Heiko Stübner
2015-07-01 12:19 ` Boris Brezillon
2015-07-01 12:19 ` Boris Brezillon
2015-07-01 12:19 ` Boris Brezillon
2015-07-14 10:50 ` Mark Brown
2015-07-14 10:50 ` Mark Brown
2015-07-14 10:50 ` Mark Brown
2015-07-14 11:02 ` Boris Brezillon
2015-07-14 11:02 ` Boris Brezillon
2015-07-14 11:02 ` Boris Brezillon
2015-07-14 11:08 ` Mark Brown
2015-07-14 11:08 ` Mark Brown
2015-07-14 11:08 ` Mark Brown
2015-07-14 11:16 ` Boris Brezillon
2015-07-14 11:16 ` Boris Brezillon
2015-07-14 11:16 ` Boris Brezillon
2015-07-01 8:22 ` [RFC PATCH 15/15] regulator: pwm: properly initialize the ->state field Boris Brezillon
2015-07-01 8:22 ` Boris Brezillon
2015-07-01 8:22 ` Boris Brezillon
2015-07-14 10:51 ` Mark Brown
2015-07-14 10:51 ` Mark Brown
2015-07-14 10:51 ` Mark Brown
2015-07-14 11:03 ` Boris Brezillon
2015-07-14 11:03 ` Boris Brezillon
2015-07-14 11:03 ` Boris Brezillon
2015-07-01 21:50 ` [RFC PATCH 16/15] pwm: add informations about polarity, duty cycle and period to debugfs Heiko Stübner
2015-07-01 21:50 ` Heiko Stübner
2015-07-01 21:50 ` Heiko Stübner
2015-07-02 13:01 ` Boris Brezillon
2015-07-02 13:01 ` Boris Brezillon
2015-07-02 13:01 ` Boris Brezillon
2015-07-03 8:43 ` [PATCH] " Heiko Stübner
2015-07-03 8:43 ` Heiko Stübner
2015-07-03 8:43 ` Heiko Stübner
2015-07-01 21:57 ` [RFC PATCH 00/15] pwm: add support for atomic update Heiko Stübner
2015-07-01 21:57 ` Heiko Stübner
2015-07-01 21:57 ` Heiko Stübner
2015-07-02 7:55 ` Boris Brezillon
2015-07-02 7:55 ` Boris Brezillon
2015-07-02 7:55 ` Boris Brezillon
2015-07-02 7:03 ` Uwe Kleine-König
2015-07-02 7:03 ` Uwe Kleine-König
2015-07-02 7:03 ` Uwe Kleine-König
2015-07-02 7:17 ` Tomi Valkeinen
2015-07-02 7:17 ` Tomi Valkeinen
2015-07-02 7:17 ` Tomi Valkeinen
2015-07-02 7:42 ` Uwe Kleine-König
2015-07-02 7:42 ` Uwe Kleine-König
2015-07-02 7:42 ` Uwe Kleine-König
2015-07-02 7:30 ` Boris Brezillon
2015-07-02 7:30 ` Boris Brezillon
2015-07-02 7:30 ` Boris Brezillon
2015-07-20 7:16 ` Boris Brezillon
2015-07-20 7:16 ` Boris Brezillon
2015-07-20 7:16 ` Boris Brezillon
2015-07-20 7:43 ` Thierry Reding
2015-07-20 7:43 ` Thierry Reding
2015-07-20 7:43 ` Thierry Reding
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=20150720100451.GW29614@ulmo \
--to=thierry.reding@gmail.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 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.