hatch_fp/board_rw: Explicitly reset FP_RST_ODL to default on RW init
hatch_fp/board_rw: Explicitly reset FP_RST_ODL to default on RW init

FP_RST_ODL pin is only defined in gpio_rw.inc, so this pin won't be
initialized to 1 by RO. Also, RW won't set this pin because sysjump to
RW is a warm reset actually and we are not setting GPIO pins to their
defaults after the warm reset to avoid undesired effects (see
gpio_pre_init() in chip/stm32/gpio.c).

As a result fpsensor_hw hardware unit test was not working, because
FPMCU was keeping sensor in reset.

Build with FP private driver is working because the driver performs
sensor reset during initialization.

BUG=b:170432597
BRANCH=none
TEST=`make BOARD=bloonchipper`

Signed-off-by: Patryk Duda <6aed17a362577cf10cb5675888c1635d522769c1@semihalf.com>
Change-Id: Ib88d1965dc1410c08c3e3a51ad4f90d27f8ea1b0
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3017987
Reviewed-by: Craig Hesling <383db090fd8ef907a606ac8a9eccd2962bc489cf@chromium.org>

coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec,coreboot/chrome-ec