summaryrefslogtreecommitdiffstats
path: root/drivers/xen
diff options
context:
space:
mode:
authorFabrice Gasnier <fabrice.gasnier@st.com>2019-10-01 10:51:09 +0200
committerWolfram Sang <wsa@the-dreams.de>2019-10-24 20:52:17 +0200
commit6d6b0d0d5afc8c4c84b08261260ba11dfa5206f2 (patch)
tree83718c6f89b3dce44c0357ef3025e46a6aa04c19 /drivers/xen
parent02e64276c6dbcc4c5f39844f33d18180832a58f3 (diff)
downloadlinux-stable-6d6b0d0d5afc8c4c84b08261260ba11dfa5206f2.tar.gz
linux-stable-6d6b0d0d5afc8c4c84b08261260ba11dfa5206f2.tar.bz2
linux-stable-6d6b0d0d5afc8c4c84b08261260ba11dfa5206f2.zip
i2c: stm32f7: fix a race in slave mode with arbitration loss irq
When in slave mode, an arbitration loss (ARLO) may be detected before the slave had a chance to detect the stop condition (STOPF in ISR). This is seen when two master + slave adapters switch their roles. It provokes the i2c bus to be stuck, busy as SCL line is stretched. - the I2C_SLAVE_STOP event is never generated due to STOPF flag is set but don't generate an irq (race with ARLO irq, STOPIE is masked). STOPF flag remains set until next master xfer (e.g. when STOPIE irq get unmasked). In this case, completion is generated too early: immediately upon new transfer request (then it doesn't send all data). - Some data get stuck in TXDR register. As a consequence, the controller stretches the SCL line: the bus gets busy until a future master transfer triggers the bus busy / recovery mechanism (this can take time... and may never happen at all) So choice is to let the STOPF being detected by the slave isr handler, to properly handle this stop condition. E.g. don't mask IRQs in error handler, when the slave is running. Fixes: 60d609f30de2 ("i2c: i2c-stm32f7: Add slave support") Signed-off-by: Fabrice Gasnier <fabrice.gasnier@st.com> Reviewed-by: Pierre-Yves MORDRET <pierre-yves.mordret@st.com> Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Diffstat (limited to 'drivers/xen')
0 files changed, 0 insertions, 0 deletions