From: Arnd Bergmann <arnd@arndb.de>
To: Alban Bedel <alban.bedel@avionic-design.de>
Cc: Mark Rutland <mark.rutland@arm.com>,
Thierry Reding <thierry.reding@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"grant.likely@linaro.org" <grant.likely@linaro.org>,
Kumar Gala <galak@codeaurora.org>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Pawel Moll <Pawel.Moll@arm.com>, Rob Herring <robh+dt@kernel.org>,
Roland Stigge <stigge@antcom.de>
Subject: Re: [PATCH V3] pwm: lpc32xx - Add a driver for the motor PWM
Date: Wed, 10 Sep 2014 11:21:29 +0200 [thread overview]
Message-ID: <5900146.ZQPMvSzLeR@wuerfel> (raw)
In-Reply-To: <20140910104220.44558cf7@avionic-0020>
On Wednesday 10 September 2014 10:42:20 Alban Bedel wrote:
>
> > Please describe clocks in the binding. If the clock inputs are named,
> > please use clock-names.
>
> No clock is defined in the current LPC32xx DTS, what should I do in
> this case?
This is a bit tricky. I would recommend describing the clock inputs
in the binding anyway, as "optional" properties, in case we ever get
a full DT-aware clocksource driver for lpc32xx.
I've just mentioned the topic to Roland yesterday, I would really
like to see such a clocksource driver done for other reasons
(multiplatform support), but introducing one with full DT support
is hard to do without breaking existing dtb files.
Arnd
prev parent reply other threads:[~2014-09-10 9:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 15:42 [PATCH V3] pwm: lpc32xx - Add a driver for the motor PWM Alban Bedel
2014-09-09 15:47 ` Arnd Bergmann
2014-09-09 16:05 ` Alban Bedel
2014-09-09 18:19 ` Arnd Bergmann
2014-09-09 16:05 ` Mark Rutland
2014-09-10 8:42 ` Alban Bedel
2014-09-10 9:21 ` Arnd Bergmann [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=5900146.ZQPMvSzLeR@wuerfel \
--to=arnd@arndb.de \
--cc=Pawel.Moll@arm.com \
--cc=alban.bedel@avionic-design.de \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stigge@antcom.de \
--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).