[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YHBINhLa3pCZjoxO@orome.fritz.box>
Date: Fri, 9 Apr 2021 14:27:34 +0200
From: Thierry Reding <thierry.reding@...il.com>
To: Uwe Kleine-König <u.kleine-koenig@...gutronix.de>
Cc: Clemens Gruber <clemens.gruber@...ruber.com>,
linux-pwm@...r.kernel.org, Sven Van Asbroeck <TheSven73@...il.com>,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
Rob Herring <robh+dt@...nel.org>
Subject: Re: [PATCH v7 4/8] dt-bindings: pwm: Support new
PWM_STAGGERING_ALLOWED flag
On Wed, Apr 07, 2021 at 07:33:57AM +0200, Uwe Kleine-König wrote:
> On Tue, Apr 06, 2021 at 06:41:36PM +0200, Clemens Gruber wrote:
> > Add the flag and corresponding documentation for the new PWM staggering
> > mode feature.
> >
> > Cc: Rob Herring <robh+dt@...nel.org>
> > Signed-off-by: Clemens Gruber <clemens.gruber@...ruber.com>
>
> For the record, I don't like this and still prefer to make this
> staggering explicit for the consumer by expanding struct pwm_state with
> an .offset member to shift the active phase in the period.
How are consumers supposed to know which offset to choose? And worse:
how should consumers even know that the driver supports phase shifts?
Thierry
Download attachment "signature.asc" of type "application/pgp-signature" (834 bytes)
Powered by blists - more mailing lists