tree c72a680a1cab166adebc43e23037e59f82a829db
parent a128f6ecd56a32e559889145003425b0c7d406e3
author Serge Semin <Sergey.Semin@baikalelectronics.ru> 1600601330 +0300
committer Mark Brown <broonie@kernel.org> 1601396543 +0100
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFHBAABCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAl9zXz8THGJyb29uaWVA
 a2VybmVsLm9yZwAKCRAk1otyXVSH0D/TB/9KYEVLFL/ZhuXrBOH3qDlx65I/Cv5k
 iK0D7bZbUkcADKDqbJw1uJYTwwK4KG4oQJzdlrZaSopm5javuuLZzUd3ZreeaYND
 R8H3kpxJRL8hicOvbS66iuswAaUvg9vcyUMNf/Hcv6s1SjnoM4t8c/xb+sxThPkB
 iIXTWOnOzkW72YBSYZMehCyt5ABrZtFab/lyd98ZcsEcj3XohNBlkmcN8S31MhQ6
 Dzs/9arqKvMIJE/VCZxOs6YpLSwLohfLlYV8iLE6YOtdaAZcjy00D2FXv9tZnJJt
 PPKaiY4NvLPmpuOkcOjO2r+4r6GjjCpf6OxugRoZJhZl2ov/eGGsRUqU
 =WedI
 -----END PGP SIGNATURE-----

spi: dw: Disable all IRQs when controller is unused

It's a good practice to disable all IRQs if a device is fully unused. In
our case it is supposed to be done before requesting the IRQ and after the
last byte of an SPI transfer is received. In the former case it's required
to prevent the IRQ handler invocation before the driver data is fully
initialized (which may happen if the IRQs status has been left uncleared
before the device is probed). So we just moved the spi_hw_init() method
invocation to the earlier stage before requesting the IRQ. In the later
case there is just no point in having any of the IRQs enabled between SPI
transfers and when there is no SPI message currently being processed.

Signed-off-by: Serge Semin <Sergey.Semin@baikalelectronics.ru>
Link: https://lore.kernel.org/r/20200920112914.26501-7-Sergey.Semin@baikalelectronics.ru
Signed-off-by: Mark Brown <broonie@kernel.org>