Fix EFM32 pwmout hal function pwmout_period

[MikeDK]

Description

In pwmout_period() of the EFM32 pwmout_api.c is a check for changed values, which is not working correctly because of a wrongly used bitmask. This has been fixed.

With the wrong bitmask, it was not possible to do things like...:

pwmout_init(PB11);
pwmout_period_us(100);
--- use of pwm channel ---
pwm_free();
--- we want to use another pin now ---
pwmout_init(PB12);
pwmout_period_us(100);

The Problem occurs on the second call of pwmout_period_us() ... the check for changed values would evaluate to TRUE, and the frequency would not be changed to 10kHz ... instead the standard frequency of 50Hz would be effective.

Pull request type

[x] Fix
[ ] Refactor
[ ] Target update
[ ] Functionality change
[ ] Breaking change

[stevew817]

lgtm 👍

[MikeDK]

quick question: when will the ci tests be scheduled? ;)

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

Build number : 3083
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/7993/

Triggering tests

/morph test
/morph export-build
/morph mbed2-build

[mbed-ci]

Test : SUCCESS

Build number : 2871
Test logs :http://mbed-os-logs.s3-website-us-west-1.amazonaws.com/?prefix=logs/7993/2871

[mbed-ci]

Exporter Build : FAILURE

Build number : 2693
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7993/

[0xc0170]

We will retrigger exporter later

/morph mbed2-build

[0xc0170]

/morph export-build

[mbed-ci]

Exporter Build : SUCCESS

Build number : 2723
Build artifacts/logs : http://mbed-os.s3-website-eu-west-1.amazonaws.com/?prefix=builds/exporter/7993/

[cmonr]

quick question: when will the ci tests be scheduled? ;)

@MikeDK Right now!

[cmonr]

(The delay has been caused by the 5.10 release)