scsi: ufs: Don't skip UFS probe in emmc based bootdevice

As a part of sync-state callback feature introduced in 5.4, clocks
which are enabled by default with the hold-state mechanism during
bootloader will be automatically disabled when the clock provider’s
i.e gcc sync-state callback triggers. So clocks enabled from boot
will be cleaned up in sync-state call back.

The sync-state callback is triggered when all consumers of a given
supplier(gcc here) have successfully probed. In current implementation,
in emmc based bootdevice, we return UFS platform driver probe failure
with reason as ENODEV which will cause the GCC sync-state callback not
getting fired and hence leaving the ufs clocks in enabled state.

So for the gcc sync state to be successful so as to remove proxy vote
for all gcc consumer ,we must not bail out and let UFS platform
driver probes successfully. Later as a part of async scan, when
UFS device detection and initialisation fails, we can turn off
power/clocks as a part of hba exit.

Change-Id: Icfcc8ceb76399f6e37454d356a5f9767f30dd4b3
Signed-off-by: Nitin Rawat <nitirawa@codeaurora.org>