stm32cube: stm32fx: remove phy init and config #300
stm32cube: stm32fx: remove phy init and config #300erwango merged 2 commits intozephyrproject-rtos:mainfrom
Conversation
erwango
left a comment
There was a problem hiding this comment.
There are 2 options coming to HAL usage. Either using it untouched, either not using it. I'm not keen on opening the door to this kind of modification.
|
unfortunately There are already other patches in the hal and this one would be pretty easy to reapply, as it is just removing a big block from one function. |
I'll take some time to think about it and specially how to do it while not opening a can of worms by letting think anyone can patch HAL whenever this is the easiest solution. |
|
@maass-hamburg I did not forget about this one, I'll provide a feedback soon. |
|
@erwango How is it going? |
erwango
left a comment
There was a problem hiding this comment.
Thanks for reminding me about this.
As this is quite specific to these 2 pieces of HW, I'm fine doing the change.
Though, please use #ifndef ZEPHYR directive.
This will make rebase easier if this piece of "upstream" code gets updates.
exclude phy init and config as that is already done in zephyr before and we don't want it to be overwritten Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
exclude phy init and config as that is already done in zephyr before and we don't want it to be overwritten Signed-off-by: Fin Maaß <f.maass@vogl-electronic.com>
1819c77 to
36ffb04
Compare
juickar
left a comment
There was a problem hiding this comment.
These changes look good to me
Tested on stm32f207zg with the dhcpv4 client sample
remove phy init and config from the legacy ethernet hal,
as that is already done in zephyr before and we don't want it to
be overwritten