From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/4] pwm: rockchip: Allow polarity invert on rk3288
Date: Wed, 20 Aug 2014 08:09:04 +0200 [thread overview]
Message-ID: <20140820060903.GE13793@ulmo> (raw)
In-Reply-To: <CAD=FV=Uvx3PMJRdnm4FKWWx4h3sN0Mn1yG6v245HnKur_3vgqQ@mail.gmail.com>
On Tue, Aug 19, 2014 at 09:05:20AM -0700, Doug Anderson wrote:
> On Tue, Aug 19, 2014 at 12:18 AM, Thierry Reding <thierry.reding@gmail.com> wrote:
> > On Mon, Aug 18, 2014 at 10:09:07AM -0700, Doug Anderson wrote:
[...]
> >> @@ -74,10 +78,14 @@ static void rockchip_pwm_set_enable_v2(struct pwm_chip *chip, bool enable)
> >> {
> >> struct rockchip_pwm_chip *pc = to_rockchip_pwm_chip(chip);
> >> u32 enable_conf = PWM_OUTPUT_LEFT | PWM_LP_DISABLE | PWM_ENABLE |
> >> - PWM_CONTINUOUS | PWM_DUTY_POSITIVE |
> >> - PWM_INACTIVE_NEGATIVE;
> >> + PWM_CONTINUOUS;
> >> u32 val;
> >>
> >> + if (pc->polarity == PWM_POLARITY_INVERSED)
> >> + enable_conf |= PWM_DUTY_NEGATIVE | PWM_INACTIVE_POSITIVE;
> >> + else
> >> + enable_conf |= PWM_DUTY_POSITIVE | PWM_INACTIVE_NEGATIVE;
> >
> > I have a feeling you're going to answer the above question with: "Because
> > it's needed here". If so, my reply would be: "Then this function should
> > take a struct pwm_device instead of struct pwm_chip."
>
> OK. I've chosen to have it take a pwm_device AND a pwm_chip. It is a
> little redundant because a pwm_device has a pointer to its pwm_chip,
> but it follows the lead of all of the callbacks in "struct pwm_ops".
> If you'd like me to spin it to take only a pwm_device I'm happy to.
No, that's fine.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140820/387c5e48/attachment.sig>
next prev parent reply other threads:[~2014-08-20 6:09 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-18 17:09 [PATCH 0/4] PWM changes for rk3288-evb Doug Anderson
2014-08-18 17:09 ` [PATCH 1/4] ARM: rockchip: rk3288: Switch to use the proper PWM IP Doug Anderson
2014-08-18 17:11 ` Sonny Rao
2014-08-18 17:19 ` Doug Anderson
2014-08-19 7:10 ` Thierry Reding
2014-08-19 15:18 ` Doug Anderson
2014-08-20 6:08 ` Thierry Reding
2014-08-20 15:20 ` Doug Anderson
2014-08-20 15:38 ` Thierry Reding
2014-08-20 15:55 ` Doug Anderson
2014-08-20 16:20 ` Heiko Stübner
2014-08-20 16:27 ` Doug Anderson
2014-08-20 18:03 ` Heiko Stübner
2014-08-20 20:49 ` Doug Anderson
2014-08-21 6:36 ` Thierry Reding
2014-08-21 15:38 ` Doug Anderson
2014-08-21 15:49 ` Tomasz Figa
2014-08-21 16:49 ` Thierry Reding
2014-08-21 16:47 ` Thierry Reding
2014-08-25 23:40 ` Doug Anderson
2014-08-26 7:31 ` Thierry Reding
2014-08-21 6:24 ` Thierry Reding
2014-08-21 15:39 ` Doug Anderson
2014-08-21 15:53 ` Heiko Stübner
2014-08-18 17:09 ` [PATCH 2/4] pwm: rockchip: Allow polarity invert on rk3288 Doug Anderson
2014-08-19 7:18 ` Thierry Reding
2014-08-19 16:05 ` Doug Anderson
2014-08-20 6:09 ` Thierry Reding [this message]
2014-08-18 17:09 ` [PATCH 3/4] ARM: dts: Add main PWM info to rk3288 Doug Anderson
2014-08-18 17:09 ` [PATCH 4/4] ARM: dts: Enable pwm backlight on rk3288-EVB Doug Anderson
2014-08-19 7:22 ` Thierry Reding
2014-08-19 16:05 ` Doug Anderson
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=20140820060903.GE13793@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 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).