ledc.c: Fix frequency calculation. (IDFGH-10569)

[IhorNehrutsa]

Round int instead of truncate.
ledc_get_freq() returns value 2Hz when the actual 3Hz was setted (Tested with oscilloscope).

Add ledc_calc_duty_resolution() -
Helper function to calculate the maximum possible LEDC duty resolution in bits for ledc_timer_config()

[CLAassistant]

All committers have signed the CLA.

[IhorNehrutsa]

The same rounding technique can see in

esp-idf/components/driver/ledc/ledc.c

Lines 334 to 338 in cf7e743

	* NOTE: We are also going to round up the value when necessary, thanks to:
	* (freq_hz * precision) / 2
	*/
	return ( ( (uint64_t) src_clk_freq << LEDC_LL_FRACTIONAL_BITS ) + ((freq_hz * precision) / 2 ) )
	/ (freq_hz * precision);

[IhorNehrutsa]

sha=9caa55a368a38199f4ab188a5a490ac90a31b4ab

What does it mean? I can't find this sha.

[IhorNehrutsa]

It look like we need to merge into v5.0-beta1

[suda-morris]

sha=9caa55a368a38199f4ab188a5a490ac90a31b4ab

What does it mean? I can't find this sha.

By this, we're asking the bot to sync the PR int our internal Gitlab server. We will merge this PR to the master first and later will backport to 5.1 and 5.0

[IhorNehrutsa]

@suda-morris
Is any restrictions?
May you guide me on the time of approving?
Thanks

[songruo]

@IhorNehrutsa The fix has been merged into master (it might take a while to sync to Github). Backports to release/v5.1 and release/v5.0 will be done soon.

[IhorNehrutsa]

@suda-morris, @songruo
Will the second commit of this PR be merged?
Or one PR = one commit?
Thanks.

[IhorNehrutsa]

Hi, @songruo, @suda-morris.
Is this PR ready? I can't understand its status.
Thanks.

[suda-morris]

hi @IhorNehrutsa Sorry for the late response. It's merged in 9ced546

[IhorNehrutsa]

By this, we're asking the bot to sync the PR int our internal Gitlab server. We will merge this PR to the master first and later will backport to 5.1 and 5.0

The fix has been merged into master (it might take a while to sync to Github). Backports to release/v5.1 and release/v5.0 will be done soon.

Still absent in the release/v5.1 and release/v5.0
We can not use the release/v5.2 and master branches because they don't have stable tags.

[IhorNehrutsa]

Are there any chances of getting this PR in release/v5.1 and release/v5.0 branches?

[songruo]

@IhorNehrutsa release/v5.2 will come out very soon! I would expect it to be there in one month (here is the beta branch). Then would you be able to use release/v5.2 branch?

[IhorNehrutsa]

@songruo Thanks for the fast answer.
release/v5.2 looks like still unstable. MicroPython maintainers prefer to use stable versions.
MicroPython port to the ESP32
esp32/PWM: Reduce inconsistencies between ports. #10854 is waiting for this PR one year. :(

Please apply it to release/v5.1 and make a new tag v5.1.3
Thank you.