From: Jisheng Zhang <jszhang@marvell.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: sebastian.hesselbarth@gmail.com,
antoine.tenart@free-electrons.com, linux-pwm@vger.kernel.org,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pwm: berlin: Add PM support
Date: Thu, 26 Nov 2015 15:41:09 +0800 [thread overview]
Message-ID: <20151126154109.6257b0bd@xhacker> (raw)
In-Reply-To: <20151125151627.GB31492@ulmo.nvidia.com>
On Wed, 25 Nov 2015 16:16:27 +0100
Thierry Reding wrote:
> On Wed, Nov 25, 2015 at 04:30:19PM +0800, Jisheng Zhang wrote:
> > On Tue, 24 Nov 2015 17:23:06 +0100 Thierry Reding wrote:
> > > On Tue, Nov 24, 2015 at 01:43:05PM +0800, Jisheng Zhang wrote:
> > > > This patch adds S2R support for berlin pwm driver.
> > > >
> > > > Signed-off-by: Jisheng Zhang <jszhang@marvell.com>
> > > > ---
> > > > drivers/pwm/pwm-berlin.c | 57 +++++++++++++++++++++++++++++++++++++++++++++++-
> > > > 1 file changed, 56 insertions(+), 1 deletion(-)
> [...]
> > > > + for (i = 0; i < pwm->chip.npwm; i++) {
> > > > + struct berlin_pwm_context *ctx = &pwm->ctx[i];
> > > > +
> > > > + berlin_pwm_writel(pwm, i, ctx->ctrl, BERLIN_PWM_CONTROL);
> > > > + berlin_pwm_writel(pwm, i, ctx->duty, BERLIN_PWM_DUTY);
> > > > + berlin_pwm_writel(pwm, i, ctx->tcnt, BERLIN_PWM_TCNT);
> > > > + berlin_pwm_writel(pwm, i, ctx->enable, BERLIN_PWM_ENABLE);
> > > > + }
> > > > +
> > > > + return 0;
> > > > +}
> > > > +
> > > > +static SIMPLE_DEV_PM_OPS(berlin_pwm_pm_ops, berlin_pwm_suspend,
> > > > + berlin_pwm_resume);
> > > > +#define BERLIN_PWM_PM_OPS (&berlin_pwm_pm_ops)
> > > > +#else
> > > > +#define BERLIN_PWM_PM_OPS NULL
> > > > +#endif
> > >
> > > This is a weird way of writing this. I think a more typical way would be
> > > to have the #ifdef contain only the implementation and then define the
> > > dev_pm_ops variable unconditonally, so you don't need a separate macro
> > > for it.
> > >
> >
> > The reason why I introduced one more macro is: struct dev_pm_ops contains
> > 23 pointers now, if there's no BERLIN_PWM_PM_OPS macro, there will be always a
> > dev_pm_ops even if PM_SLEEP isn't enabled. I dunno whether there's any
> > elegant solution for this case.
>
> I wouldn't bother. PM_SLEEP is in almost all cases going to be enabled.
> If it isn't enabled it's likely going to be in test builds, at which
> point nobody will care about the extra 23 pointers.
>
> > How about define SIMPLE_DEV_PM_OPS as NULL if PM_SLEEP isn't enabled?
>
> That won't work, "static NULL;" wouldn't be valid syntax. Like I said,
> if you go through the trouble of implementing suspend/resume, you're
> almost certainly going to want to enable it, so just define it
> unconditionally.
>
Thanks for detailed explanation. In yesterday's v2, the BERLIN_PWM_PM_OPS
was removed.
Thanks for review,
Jisheng
prev parent reply other threads:[~2015-11-26 7:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-24 5:43 [PATCH] pwm: berlin: Add PM support Jisheng Zhang
2015-11-24 16:23 ` Thierry Reding
2015-11-25 8:30 ` Jisheng Zhang
2015-11-25 15:16 ` Thierry Reding
2015-11-26 7:41 ` Jisheng Zhang [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=20151126154109.6257b0bd@xhacker \
--to=jszhang@marvell.com \
--cc=antoine.tenart@free-electrons.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=thierry.reding@gmail.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 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).