alxPwm_McuStm32 - add frequency & resolution to Ctor.. now we have "svinjak" with prescaler & period uint32..

The goal: 1) Understand everything about the problem

what are parameters that we must set before calculation
what parameters we must get before calculation 2) Prepare Ctor, and algorithm logic for validation, then TV check 3) Implementation & testing of algorithm

AlxPwm_Ctor(..., float desiredFreq_Hz, uint32_t desiredMinRes, bool isFreqPriority, float freqTolerance_pct...)

maybe we will need in ctor which to gave priority in calculation (freq or resolution)?
maybe we will need in ctor what is acceptable tolerance of freq
maybe we will need in ctor what is minimum acceptable resolution (max resolutin we don't need because the larger resolution the better)

float desiredFreq_Hz --> what frequency we want PWM signal to be

uint32_t desiredResolution --> what resolution we want, meaning how many steps will there be in one period of PWM signal

example if resolution = 100, this means that we have 100 steps in one period, meaning we can set duty cycle to 1% "natančno"

Parameters that we need for calculations:

timer frequency --> what time unit is one Tick.. how fast timer counts..
- to know this we must know what clock source is input to Timer periphery (this will be const)
- we must also know what presacler is set (this one we control)
Is 16-bit, 32-bit timer --> so to which number can it count, and then overflows and starts from beggining

We also what that after calculations, all "dejanske" values are saved in module struct, so that can you see what algorithm calculated in Debugger

PWM signal resolution:

auralix / alx-202-af-10-1-auralix-c-lib