STM32 ETH : remove TX RX locking interrupt perforation

[jeromecoutant]

Description

See #6610 for detailed analysis

@pauluap
I have updated F7 file, as I think you miss some LOCK and UNLOCK ?

Pull request type

[X] Fix
[ ] Refactor
[ ] New target
[ ] Feature
[ ] Breaking change

[pauluap]

@jeromecoutant, my intention was only to resolve the perforation issue. I didn't touch the other HAL locks because I didn't really understand their purpose. HAL locking seems to be a fundamental part of the STMCube design.

It seems that you have determined that HAL locking isn't necessary for the MAC HAL module. That's cool, good information to know.

I have no information that suggests that this will (or will not for that matter) be an issue. For mbed at least, I don't project any problems since the mac configuration is done from a single thread, the phy register read, rx and tx seem to be just fine running in different threads.

[pauluap]

@jeromecoutant Oops, I stand corrected. Yes, you're right, I missed the updating the non-_IT versions in F7 because my code wasn't using those. I'm glad that you caught the one at the end of GetReceivedFrame_IT, in removing one perforation, I introduced another!

My apologizes

[jeromecoutant]

@bcostm @kjbracey-arm

Any comment ? Thx

[0xc0170]

/morph build

[0xc0170]

/morph build

[mbed-ci]

Build : SUCCESS

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

Triggering tests

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

[cmonr]

Pausing CI until 5.9 RC3 completes CI. Will restart jobs when able.

[0xc0170]

/morph test
/morph export-build

[mbed-ci]

Test : SUCCESS

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

[mbed-ci]

Exporter Build : SUCCESS

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