From: "Hall, Christopher S" <christopher.s.hall@intel.com>
To: Linus Walleij <linus.walleij@linaro.org>,
"Shevchenko, Andriy" <andriy.shevchenko@intel.com>,
Dipen Patel <dipenp@nvidia.com>,
"N, Pandith" <pandith.n@intel.com>,
"D, Lakshmi Sowjanya" <lakshmi.sowjanya.d@intel.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"vilhelm.gray@gmail.com" <vilhelm.gray@gmail.com>,
"jic23@kernel.org" <jic23@kernel.org>,
"Sangannavar,
Mallikarjunappa" <mallikarjunappa.sangannavar@intel.com>,
"T R, Thejesh Reddy" <thejesh.reddy.t.r@intel.com>
Subject: RE: Intel Timed-IO driver in IIO/Counter subsystem
Date: Sat, 18 Jun 2022 02:01:28 +0000 [thread overview]
Message-ID: <ad7e53d1bd2448b4971af65483fe3542@intel.com> (raw)
In-Reply-To: <CACRpkdbeQ_67V3jkw_-KfTwe54TxrK_LA7N8Nwj1qEpTELN9dQ@mail.gmail.com>
Hi Linus,
Friday, June 17, 2022 4:40 AM Linus Walleij <linus.walleij@linaro.org> wrote:
> For 2. I am uncertain. Periodic events sound like PWM to me.
I do not think TGPIO periodic output is useful for PWM. There are two output
modes: edge output and pulse output. In edge mode output, where the an edge
is produced periodically based on the programmed period the duty cycle is
always 50%. In pulse mode output where a pulse is produced each output
period, the width of the pulse is two ART ticks which on current Intel
client platforms is about 50 ns. The pulse width is not adjustable.
We want to be able to output a clock from 1 Hz (1 PPS) up to 1 KHz that is
synchronized with the system clock.
It is possible to represent the periodic output function as a PWM device,
but the PWM subsystem output - without modification - is not aligned to
any clock which breaks the timing application.
> If a "single event" is something
> like pulling a GPIO line high/low at a specific (wall clock) time in the
> future, it should probably be in the GPIO subsystem, like a triggered
> GPIO event or so, that sounds a bit hard but certainly doable with some
> thinking and tinkering.
Earlier, we proposed a linereq_write() method in addition to the already
existing linereq_read().
https://lkml.org/lkml/2021/8/24/807
This is for "single shot" scheduled output only. This is fairly easy to
implement using the Timed I/O hardware because the clock used to schedule
output events is directly related to TSC and system time.
The difficult part is implementing this for devices that are not time
aware.
> Yours,
> Linus Walleij
Thanks,
Christopher
next prev parent reply other threads:[~2022-06-18 2:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-17 6:37 Intel Timed-IO driver in IIO/Counter subsystem N, Pandith
2022-06-17 7:22 ` Lars-Peter Clausen
2022-06-17 9:51 ` Shevchenko, Andriy
2022-06-17 11:39 ` Linus Walleij
2022-06-18 2:01 ` Hall, Christopher S [this message]
2022-06-23 12:21 ` Linus Walleij
2022-07-05 3:16 ` Kent Gibson
2022-07-06 5:52 ` Hall, Christopher S
2022-07-06 23:05 ` Linus Walleij
2022-07-07 3:21 ` Kent Gibson
2022-06-17 14:03 ` William Breathitt Gray
2022-06-17 17:15 ` Jonathan Cameron
2022-06-18 1:01 ` Hall, Christopher S
2022-06-21 13:58 ` William Breathitt Gray
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=ad7e53d1bd2448b4971af65483fe3542@intel.com \
--to=christopher.s.hall@intel.com \
--cc=andriy.shevchenko@intel.com \
--cc=dipenp@nvidia.com \
--cc=jic23@kernel.org \
--cc=lakshmi.sowjanya.d@intel.com \
--cc=lars@metafoo.de \
--cc=linus.walleij@linaro.org \
--cc=linux-iio@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=pandith.n@intel.com \
--cc=thejesh.reddy.t.r@intel.com \
--cc=vilhelm.gray@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