| Message ID | 20200708211432.28612-7-hdegoede@redhat.com (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | acpi/pwm/i915: Convert pwm-crc and i915 driver's PWM code to use the atomic PWM API | expand |
On Wed, Jul 08, 2020 at 11:14:22PM +0200, Hans de Goede wrote: > The datasheet specifies that programming the base_unit part of the > ctrl register to 0 results in a contineous low signal. > > Adjust the get_state method to reflect this by setting pwm_state.period > to 1 and duty_cycle to 0. ... > + if (freq == 0) { > + /* In this case the PWM outputs a continous low signal */ > + state->period = 1; I guess this should be something like half of the range (so base unit calc will give 128). Because with period = 1 (too small) it will give too small base unit (if apply) and as a result we get high frequency pulses. > + state->duty_cycle = 0; > + } else { > state->period = NSEC_PER_SEC / (unsigned long)freq; > + on_time_div *= state->period; > + do_div(on_time_div, 255); > + state->duty_cycle = on_time_div; > + }
Hi, On 7/9/20 4:50 PM, Andy Shevchenko wrote: > On Wed, Jul 08, 2020 at 11:14:22PM +0200, Hans de Goede wrote: >> The datasheet specifies that programming the base_unit part of the >> ctrl register to 0 results in a contineous low signal. >> >> Adjust the get_state method to reflect this by setting pwm_state.period >> to 1 and duty_cycle to 0. > > ... > >> + if (freq == 0) { >> + /* In this case the PWM outputs a continous low signal */ > >> + state->period = 1; > > I guess this should be something like half of the range (so base unit calc > will give 128). Because with period = 1 (too small) it will give too small > base unit (if apply) and as a result we get high frequency pulses. You are right, that if after this the user only changes the duty-cycle things will work very poorly, we will end up with a base_unit value of e.g 65535 and then have almost no duty-cycle resolution at all. How about using a value here which results in a base_unit value of 256 (for 16 bit base-unit registers), that is the highest frequency we can do while still having full duty-cycle resolution and it also is the power-on-reset value, so using a higher period which translates to a base_unit value of 256 (the por calue) seems like a sensible thing to do. Uwe what do you think about this? Regards, Hans > >> + state->duty_cycle = 0; >> + } else { >> state->period = NSEC_PER_SEC / (unsigned long)freq; >> + on_time_div *= state->period; >> + do_div(on_time_div, 255); >> + state->duty_cycle = on_time_div; >> + } >
On Thu, Jul 09, 2020 at 05:47:59PM +0200, Hans de Goede wrote: > Hi, > > On 7/9/20 4:50 PM, Andy Shevchenko wrote: > > On Wed, Jul 08, 2020 at 11:14:22PM +0200, Hans de Goede wrote: > > > The datasheet specifies that programming the base_unit part of the > > > ctrl register to 0 results in a contineous low signal. > > > > > > Adjust the get_state method to reflect this by setting pwm_state.period > > > to 1 and duty_cycle to 0. > > > > ... > > > > > + if (freq == 0) { > > > + /* In this case the PWM outputs a continous low signal */ > > > > > + state->period = 1; > > > > I guess this should be something like half of the range (so base unit calc > > will give 128). Because with period = 1 (too small) it will give too small > > base unit (if apply) and as a result we get high frequency pulses. > > You are right, that if after this the user only changes the duty-cycle > things will work very poorly, we will end up with a base_unit value of > e.g 65535 and then have almost no duty-cycle resolution at all. Is this a problem of the consumer that we don't need to solve? Are there known consumers running into this problem? pwm_lpss_prepare() is buggy here, a request for a too low period should be refused. Best regards Uwe
Hi, On 7/11/20 8:11 AM, Uwe Kleine-König wrote: > On Thu, Jul 09, 2020 at 05:47:59PM +0200, Hans de Goede wrote: >> Hi, >> >> On 7/9/20 4:50 PM, Andy Shevchenko wrote: >>> On Wed, Jul 08, 2020 at 11:14:22PM +0200, Hans de Goede wrote: >>>> The datasheet specifies that programming the base_unit part of the >>>> ctrl register to 0 results in a contineous low signal. >>>> >>>> Adjust the get_state method to reflect this by setting pwm_state.period >>>> to 1 and duty_cycle to 0. >>> >>> ... >>> >>>> + if (freq == 0) { >>>> + /* In this case the PWM outputs a continous low signal */ >>> >>>> + state->period = 1; >>> >>> I guess this should be something like half of the range (so base unit calc >>> will give 128). Because with period = 1 (too small) it will give too small >>> base unit (if apply) and as a result we get high frequency pulses. >> >> You are right, that if after this the user only changes the duty-cycle >> things will work very poorly, we will end up with a base_unit value of >> e.g 65535 and then have almost no duty-cycle resolution at all. > > Is this a problem of the consumer that we don't need to solve? Are there > known consumers running into this problem? AFAICT we never ever actually see freq == 0 here, this is just a code-path to avoid a divide by 0 in case we somehow mysteriously do get freq == 0 here. On boot the PWM controller is either not used and then the default freq = input-clock / 256, or it is used and programmed to same sane value. > pwm_lpss_prepare() is buggy here, a request for a too low period should be > refused. So instead of clamping as is done in an earlier patch, we should return -EINVAL ? Only for too low periods, or also for too high periods ? I must say this does worry me a bit, the VBT may request 200Hz output frequency and some revisions of the PWM controller can do 283Hz as lowest output freq. ATM we just give the i915 code the 283 Hz if it request 200, that seems more sane then to give it -EINVAL, since -EINVAL would require the i915 driver to know the exact limits of each PWM controller and then to clamp the VBT value before passing it to the PWM driver, that means moving knowledge out of the PWM driver into the i915 code. I believe that without first amending the PWM API too allow a consumer to query the period min/max values, returning -EINVAL is not the right thing to do here. Regards, Hans
diff --git a/drivers/pwm/pwm-lpss.c b/drivers/pwm/pwm-lpss.c index 4f3d60ce9929..4d4de45cf99b 100644 --- a/drivers/pwm/pwm-lpss.c +++ b/drivers/pwm/pwm-lpss.c @@ -192,14 +192,16 @@ static void pwm_lpss_get_state(struct pwm_chip *chip, struct pwm_device *pwm, freq = base_unit * lpwm->info->clk_rate; do_div(freq, base_unit_range); - if (freq == 0) - state->period = NSEC_PER_SEC; - else + if (freq == 0) { + /* In this case the PWM outputs a continous low signal */ + state->period = 1; + state->duty_cycle = 0; + } else { state->period = NSEC_PER_SEC / (unsigned long)freq; - - on_time_div *= state->period; - do_div(on_time_div, 255); - state->duty_cycle = on_time_div; + on_time_div *= state->period; + do_div(on_time_div, 255); + state->duty_cycle = on_time_div; + } state->polarity = PWM_POLARITY_NORMAL; state->enabled = !!(ctrl & PWM_ENABLE);
The datasheet specifies that programming the base_unit part of the ctrl register to 0 results in a contineous low signal. Adjust the get_state method to reflect this by setting pwm_state.period to 1 and duty_cycle to 0. Suggested-by: Uwe Kleine-König <u.kleine-koenig@pengutronix.de> Signed-off-by: Hans de Goede <hdegoede@redhat.com> --- Changes in v4: - This is a new patch in v4 of this patchset --- drivers/pwm/pwm-lpss.c | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-)