tree b4c33f65967ddc2979bc1d78f4b9011634d43b25
parent 457c25efc592bb5539e18161c505f7a865013fb7
author Oder Chiou <oder_chiou@realtek.com> 1510226890 +0800
committer Mark Brown <broonie@kernel.org> 1510227354 +0000
gpgsig -----BEGIN PGP SIGNATURE-----
 
 iQFHBAABCgAxFiEEreZoqmdXGLWf4p/qJNaLcl1Uh9AFAloEPZoTHGJyb29uaWVA
 a2VybmVsLm9yZwAKCRAk1otyXVSH0LElB/9T+XAH+sh3hR6VTdD3hegYT+AxuBeH
 lmZCH5miDQini77IZ/jtf5UjrRh/4oYD6i4RTkaFl1ORi2+TMI3BHpvQO0p8Ouj+
 Ev4mU4EKauZDJTvcXPiUw2fFXtXV1Q/+C2maaiIOm4hdVcg6N53I9hZjJFUUHqnX
 w5gTmmWJhsakHLWbOAWPZd4qUdChL2IMNTiA7j+7QVbSDbmS5swjdBNHU4gcMCrN
 XkpHfgyHnONssluB4+V+ZGppe4g6xYGxAdTiJTsUO0OMd0f3IjrC2ANusCAl14Eo
 lr5pdQ2wiFoXSqVqzwzYKZjQp9ZSRh24FfNwVxU+vT1zQj3pP5V20X9K
 =oqxF
 -----END PGP SIGNATURE-----

ASoC: rt5663: Delay and retry reading rt5663 ID register

In the probe, the codec may not be ready for I2C reading or there are some
glitches on the i2c line. So if the i2c reading value is incorrect, it will
read again after delay. This issue is similar the patch
https://patchwork.kernel.org/patch/9681421/. In current project, these 2
devices were connected to the same i2c line, and they met the same problem.

Signed-off-by: Oder Chiou <oder_chiou@realtek.com>
Signed-off-by: Mark Brown <broonie@kernel.org>