From: Thierry Reding <thierry.reding@gmail.com>
To: Arnd Bergmann <arnd@arndb.de>
Cc: monstr@monstr.eu, Bart Tanghe <bart.tanghe@thomasmore.be>,
michal.simek@xilinx.com, robh+dt@kernel.org, pawel.moll@arm.com,
mark.rutland@arm.com, ijc+devicetree@hellion.org.uk,
galak@codeaurora.org, rob@landley.net, grant.likely@linaro.org,
linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [rfc]pwm: add xilinx pwm driver
Date: Thu, 15 May 2014 22:49:42 +0200 [thread overview]
Message-ID: <20140515204941.GB7136@mithrandir> (raw)
In-Reply-To: <16896948.U7hTsgDub4@wuerfel>
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
On Thu, May 15, 2014 at 06:30:13PM +0200, Arnd Bergmann wrote:
> On Thursday 15 May 2014 15:56:03 Michal Simek wrote:
> > IP is configurable as is normal for us.
> > You can select IP with just one timer.
> > It means register locations for specific timer are fixed.
> > http://www.xilinx.com/support/documentation/ip_documentation/xps_timer.pdf
> >
> > timer0 - offset 0x0
> > timer1 - offset 0x10 (doesn't need to be synthesized)
> >
> > There is one interrupt for both timers.
> >
> > Timers can be as timers (up/down count/ reload with or without IRQs)
> > But then one options is to use both timers and generate PWM signal.
> > From full ip description in DT you can see xlnx,gen0-assert = <1>;
> > which can suggest that this IP can output PMW signal.
> > (We can also detect if PWM0 signal is connected just to be sure
> > that PWM can be enabled).
> >
> > There is also capture trigger mode where external signal start/stop
> > timer counting.
> >
> > It means there are 3 modes - timer, capture and PWM.
> > Timer (clocksource, clockevent) requires specific handling,
> > PWM has own subsystem and not sure if there is any subsystem for
> > capture mode. Is there any?
>
> I don't think so. Possibly somewhere in IIO.
I think so too. There was a patch set not so long ago that added PWM
capture support for one of the TI PWM controllers to IIO.
Thierry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-05-15 20:49 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-14 11:26 [rfc]pwm: add xilinx pwm driver Bart Tanghe
2014-05-15 7:23 ` Arnd Bergmann
2014-05-15 8:50 ` Bart Tanghe
2014-05-15 10:33 ` Michal Simek
2014-05-15 11:30 ` Bart Tanghe
2014-05-15 11:54 ` Michal Simek
2014-05-15 9:48 ` Michal Simek
[not found] ` <53748D84.5040005-pSz03upnqPeHXe+LvDLADg@public.gmane.org>
2014-05-15 12:20 ` Arnd Bergmann
2014-05-15 13:56 ` Michal Simek
2014-05-15 16:30 ` Arnd Bergmann
2014-05-15 20:49 ` Thierry Reding [this message]
2014-05-16 8:44 ` Michal Simek
2014-05-16 7:53 ` Michal Simek
2014-09-04 10:41 ` Bart Tanghe
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=20140515204941.GB7136@mithrandir \
--to=thierry.reding@gmail.com \
--cc=arnd@arndb.de \
--cc=bart.tanghe@thomasmore.be \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=monstr@monstr.eu \
--cc=pawel.moll@arm.com \
--cc=rob@landley.net \
--cc=robh+dt@kernel.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).