From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Olof Johansson <olof@lixom.net>
Cc: Arnd Bergmann <arnd@arndb.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Thierry Reding <thierry.reding@gmail.com>,
linux-pwm@vger.kernel.org, "arm@kernel.org" <arm@kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: PWM...
Date: Sun, 19 Jan 2014 19:30:26 +0000 [thread overview]
Message-ID: <20140119193026.GS15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <CAOesGMi7g=PHjzhkuObkeu+P_c6kUz5uFcND7euafUW56CvsnQ@mail.gmail.com>
On Sun, Jan 19, 2014 at 11:11:41AM -0800, Olof Johansson wrote:
> On Sun, Jan 19, 2014 at 11:08 AM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Sunday 19 January 2014 11:03:24 Olof Johansson wrote:
> >> >
> >> > Yes, because iMX6 specifies #pwm-cells as 2, there's no flags able to
> >> > be specified in the pwms declaration in pwmleds. So that doesn't work.
> >> > There's no property to tell pwmleds that it should use inverted sense
> >> > either.
> >>
> >> Adding a property for active-low to the pwm-leds binding would be
> >> easy, and backwards compatible. I'm surprised the original binding
> >> didn't specify it. The leds-pwm driver already seems to support it for
> >> C-configured instances.
> >>
> >> I'm also surprised that the imx pwm driver even has a #pwm-cells of
> >> two, since the driver only supports one output. It'd be nice if they
> >> had allocated the extra cell for flags, but it's hard to change now,
> >> unless you do a new binding/compatible value and deprecate the old one.
> >
> > Actually I think it's not that hard to change: The binding can specify
> > that either #pwm-cells=<2> or #pwm-cells=<3> is supported, and the
> > driver extended to handle both cases. This would maintain backwards
> > compatibility for old dtb files, though no forward compatibility for
> > new dtb files with old kernels.
>
> Ah, yes, if you add a cell that can be done. There'll still be the
> "dead" first cell that will always be 0, but that's alright.
Does it not mean that PWM specifications of:
<&pwm1 0 n> <&pwm2 0 n>
would need to be converted to:
<&pwm1 0 n 0> <&pwm2 0 n 0>
in every DT file referring to these PWMs - because isn't this just
treated in DT as one single array of values? (If DT knew how many
were in each specification, we wouldn't need the #foo-cells...)
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-19 19:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-19 16:49 PWM Russell King - ARM Linux
2014-01-19 19:03 ` PWM Olof Johansson
2014-01-19 19:08 ` PWM Arnd Bergmann
2014-01-19 19:11 ` PWM Olof Johansson
2014-01-19 19:30 ` Russell King - ARM Linux [this message]
2014-01-19 20:26 ` PWM Arnd Bergmann
2014-01-19 23:33 ` PWM Olof Johansson
2014-01-20 0:14 ` PWM Simon Horman
2014-01-20 7:24 ` PWM Sascha Hauer
2014-01-20 16:11 ` PWM Mark Brown
2014-01-21 0:39 ` PWM Simon Horman
2014-01-20 7:21 ` PWM Sascha Hauer
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=20140119193026.GS15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=olof@lixom.net \
--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).