From: Michael Turquette <mturquette@linaro.org>
To: Philipp Zabel <p.zabel@pengutronix.de>,
Thierry Reding <thierry.reding@gmail.com>
Cc: "Janusz Użycki" <j.uzycki@elproma.com.pl>,
"Rob Herring" <robh+dt@kernel.org>,
"Pawel Moll" <pawel.moll@arm.com>,
"Mark Rutland" <mark.rutland@arm.com>,
"Ian Campbell" <ijc+devicetree@hellion.org.uk>,
"Kumar Gala" <galak@codeaurora.org>,
"Stephen Boyd" <sboyd@codeaurora.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH v5] clk: Add PWM clock driver
Date: Fri, 10 Apr 2015 14:45:05 -0700 [thread overview]
Message-ID: <20150410214505.14369.98377@quantum> (raw)
In-Reply-To: <1426154657.14455.13.camel@pengutronix.de>
Quoting Philipp Zabel (2015-03-12 03:04:17)
> Am Freitag, den 13.02.2015, 20:18 +0100 schrieb Philipp Zabel:
> > Some board designers, when running out of clock output pads, decide to
> > (mis)use PWM output pads to provide a clock to external components.
> > This driver supports this practice by providing an adapter between the
> > PWM and clock bindings in the device tree. As the PWM bindings specify
> > the period in the device tree, this is a fixed clock.
> >
> > Tested-by: Janusz Uzycki <j.uzycki@elproma.com.pl>
> > Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> > ---
> > Changes since v4:
> > - Added missing static keywords, as pointed out by Stephen Boyd
> > - Turned to_clk_pwm into an inline function,
> > - added MODULE_AUTHOR/DESCRIPTION/LICENSE,
> > - and fixed PWM spelling issues, as pointed out by Thierry Reding
>
> Are there any further changes you'd like me to make to this patch?
Applied.
Thanks,
Mike
>
> regards
> Philipp
>
prev parent reply other threads:[~2015-04-10 21:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-13 19:18 [PATCH v5] clk: Add PWM clock driver Philipp Zabel
[not found] ` <1423855132-20939-1-git-send-email-p.zabel-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2015-03-12 10:04 ` Philipp Zabel
2015-04-10 21:45 ` Michael Turquette [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=20150410214505.14369.98377@quantum \
--to=mturquette@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=j.uzycki@elproma.com.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=p.zabel@pengutronix.de \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--cc=sboyd@codeaurora.org \
--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).