[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHp75Ve=v=50UmpOyi1guY3NVuk41U0Ma+_P__5NK7_dNr6gZg@mail.gmail.com>
Date: Sun, 28 May 2017 01:28:45 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Claudiu Beznea <claudiu.beznea@...rochip.com>
Cc: Thierry Reding <thierry.reding@...il.com>,
Jonathan Corbet <corbet@....net>,
Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
Boris Brezillon <boris.brezillon@...e-electrons.com>,
linux-pwm@...r.kernel.org,
Linux Documentation List <linux-doc@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-arm Mailing List <linux-arm-kernel@...ts.infradead.org>,
nicolas.ferre@...rochip.com
Subject: Re: [PATCH v2 1/2] drivers: pwm: core: implement pwm dead-times
On Tue, May 9, 2017 at 11:19 AM, Claudiu Beznea
<claudiu.beznea@...rochip.com> wrote:
> Extends PWM framework to support PWM dead-times.
> The notions introduced are rising edge dead-time
> and falling edge dead-time. These are useful for
> PWM controllers with channels that have more than
> one outputs.
> The implementation add sysfs interface for
> configuration. It extends the pwm_state structure
> with two new members which keeps the values for
> dead-times.
> There were no additions in device tree for PWM channels
> initialized by device tree.
AFAIU it's effectively called phase of the signal.
It looks to me much simpler if you allow to have linked / virtual
channels instead of creating a lot of (duplicated) properties.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists