From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 2/5] pwm: kona: Introduce Kona PWM controller support
Date: Thu, 20 Mar 2014 15:48:38 +0100 [thread overview]
Message-ID: <20140320144833.GA25092@ulmo> (raw)
In-Reply-To: <CAAYSxhpW-N7UdpsGE7JHvOJxQcvURRPdAOhiVkK=4EHc7E03gQ@mail.gmail.com>
On Tue, Mar 18, 2014 at 06:06:03PM -0700, Tim Kryger wrote:
> On Tue, Mar 18, 2014 at 4:47 PM, Tim Kryger <tim.kryger@linaro.org> wrote:
> > On Tue, Mar 18, 2014 at 2:52 PM, Thierry Reding <thierry.reding@gmail.com> wrote:
> >> On Wed, Mar 12, 2014 at 01:15:43PM -0700, Tim Kryger wrote:
[...]
> >>> +static int kona_pwmc_set_polarity(struct pwm_chip *chip, struct pwm_device *pwm,
> >>> + enum pwm_polarity polarity)
> >>> +{
> >>> + /*
> >>> + * The framework only allows the polarity to be changed when a PWM is
> >>> + * disabled so no immediate action is required here. When a channel is
> >>> + * enabled, the polarity gets handled as part of the re-config step.
> >>> + */
> >>> +
> >>> + return 0;
> >>> +}
> >>
> >> See above. If you don't want to implement the hardware support for
> >> inversed polarity, then simply don't implement this.
> >
> > I had originally planned to omit polarity support but because it
> > affects the binding (which is treated as ABI), it wouldn't be possible
> > to add it in later without defining a new compatible string.
>
> I would like to get this right but it occurred to me that there may be
> a way to defer the implementation of this feature without disrupting
> the binding.
>
> Would it be acceptable to continue using #pwm-cells = <3> and
> of_pwm_xlate_with_flags but return -EINVAL from kona_pwmc_set_polarity
> if PWM_POLARITY_INVERSED is specified?
This was recently discussed for the pwm-imx driver. And you can easily
support #pwm-cells = <2> and #pwm-cells = <3> with the same binding. So
you could start with #pwm-cells = <2>, leaving out .set_polarity() and
implement it later on, extending the binding in a backwards-compatible
way to support the polarity flag.
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20140320/9250062e/attachment.sig>
next prev parent reply other threads:[~2014-03-20 14:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-12 20:15 [PATCH v3 0/5] Add Broadcom Kona PWM Support Tim Kryger
2014-03-12 20:15 ` [PATCH v3 1/5] Documentation: dt: Add Kona PWM binding Tim Kryger
2014-03-18 21:18 ` Thierry Reding
2014-03-18 21:47 ` Tim Kryger
2014-03-12 20:15 ` [PATCH v3 2/5] pwm: kona: Introduce Kona PWM controller support Tim Kryger
2014-03-18 21:52 ` Thierry Reding
2014-03-18 23:47 ` Tim Kryger
2014-03-19 1:06 ` Tim Kryger
2014-03-20 14:48 ` Thierry Reding [this message]
2014-03-20 15:57 ` Thierry Reding
2014-03-20 17:12 ` Tim Kryger
2014-03-20 19:54 ` Tim Kryger
2014-03-12 20:15 ` [PATCH v3 3/5] ARM: dts: Declare the PWM for bcm11351 (bcm281xx) Tim Kryger
2014-03-12 20:15 ` [PATCH v3 4/5] ARM: dts: Enable the PWM for bcm28155 AP board Tim Kryger
2014-03-12 20:15 ` [PATCH v3 5/5] ARM: bcm_defconfig: Enable PWM and Backlight Tim Kryger
2014-03-14 13:43 ` [PATCH v3 0/5] Add Broadcom Kona PWM Support Matt Porter
2014-03-18 21:53 ` 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=20140320144833.GA25092@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).