Lines Matching full:apply
191 if (!ops->apply) in pwm_ops_check()
373 dev_warn(chip->dev, ".apply ignored .polarity\n"); in pwm_apply_debug()
380 … ".apply didn't pick the best available period (requested: %llu, applied: %llu, possible: %llu)\n", in pwm_apply_debug()
385 ".apply is supposed to round down period (requested: %llu, applied: %llu)\n", in pwm_apply_debug()
394 …".apply didn't pick the best available duty cycle (requested: %llu/%llu, applied: %llu/%llu, possi… in pwm_apply_debug()
401 ".apply is supposed to round down duty_cycle (requested: %llu/%llu, applied: %llu/%llu)\n", in pwm_apply_debug()
410 err = chip->ops->apply(chip, pwm, &s1); in pwm_apply_debug()
430 ".apply is not idempotent (ena=%d pol=%d %llu/%llu) -> (ena=%d pol=%d %llu/%llu)\n", in pwm_apply_debug()
438 * __pwm_apply() - atomically apply a new state to a PWM device
440 * @state: new state to apply
460 err = chip->ops->apply(chip, pwm, state); in __pwm_apply()
477 * pwm_apply_might_sleep() - atomically apply a new state to a PWM device
480 * @state: new state to apply
487 * Some lowlevel driver's implementations of .apply() make use of in pwm_apply_might_sleep()
512 * pwm_apply_atomic() - apply a new state to a PWM device from atomic context
515 * @state: new state to apply