From: Philipp Zabel <p.zabel@pengutronix.de>
To: Mike Turquette <mturquette@linaro.org>
Cc: "Thierry Reding" <thierry.reding@gmail.com>,
"Janusz Użycki" <j.uzycki@elproma.com.pl>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-pwm@vger.kernel.org
Subject: Re: [PATCH] clk: Add PWM clock driver
Date: Tue, 04 Nov 2014 12:55:52 +0100 [thread overview]
Message-ID: <1415102152.3701.13.camel@pengutronix.de> (raw)
In-Reply-To: <20140927200122.19023.40310@quantum>
Am Samstag, den 27.09.2014, 13:01 -0700 schrieb Mike Turquette:
> Quoting Thierry Reding (2014-09-23 01:51:31)
> > On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
> > > Hi,
> > >
> > > http://patchwork.ozlabs.org/patch/359069/
> > > https://lkml.org/lkml/2014/6/12/186
> > >
> > > Will the patch ever included to linux-next?
> >
> > I've never seen this patch before. From a quick look it doesn't seem
> > like it would work as is, but the idea is certainly interesting. If
> > somebody decides to continue work on it, please Cc me and the linux-pwm
> > mailing list.
>
> I just merged a gpio-controlled clock gate and I'm fine with a PWM clock
> output.
>
> Janusz, how are you testing the clock driver?
On the BoundaryDevices Nitrogen6X board, the master clock to the OV5640
MIPI CSI-2 sensor module has to be provided by a PWM.
regards
Philipp
next prev parent reply other threads:[~2014-11-04 11:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 20:05 [PATCH] clk: Add PWM clock driver Janusz Użycki
[not found] ` <5410AEFD.5030302-9tnw74Q4ehaHKKo6LODCOg@public.gmane.org>
2014-09-23 8:51 ` Thierry Reding
2014-09-27 20:01 ` Mike Turquette
2014-11-03 17:45 ` Janusz Użycki
2014-11-04 11:55 ` Philipp Zabel [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-06-12 10:08 Philipp Zabel
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=1415102152.3701.13.camel@pengutronix.de \
--to=p.zabel@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=j.uzycki@elproma.com.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mturquette@linaro.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).