summaryrefslogtreecommitdiff
path: root/drivers/scsi
diff options
context:
space:
mode:
authorKursad Oney <kursad.oney@broadcom.com>2019-08-14 15:18:35 +0200
committerTom Rini <trini@konsulko.com>2019-10-11 10:09:16 -0400
commitb47f4891e5dded550f1eaee7daaac55b8c0bd76e (patch)
treed8987a4bdc38cb8693b9a923b1fac4c2e139a58a /drivers/scsi
parent3ae64e8f256c864c546913730f82e2ffbcadc06e (diff)
spi: bcm63xx_hsspi: Continue init when using no reset and fixed-clock.
The Broadcom ARM implementations do not yet have a clock framework so one can use a fixed clock as the root clock of the hsspi block. The fixed clock does not have an "enable" routine, since it's always enabled. So when we hit this issue, getting an ENOSYS return, do not bail but continue initialization. Similarly the block might already have been out of reset, say, when we are booting from a SPI device. So if the reset signal is not configured in the device tree, do not bail out and instead skip deasserting the reset. Signed-off-by: Kursad Oney <kursad.oney@broadcom.com> Reviewed-by: Philippe Reynes <philippe.reynes@softathome.com>
Diffstat (limited to 'drivers/scsi')
0 files changed, 0 insertions, 0 deletions