summaryrefslogtreecommitdiff
path: root/drivers/media/dvb-frontends/stb0899_reg.h
diff options
context:
space:
mode:
authorMauro Carvalho Chehab <m.chehab@samsung.com>2013-12-13 17:35:03 +0400
committerMauro Carvalho Chehab <m.chehab@samsung.com>2013-12-19 14:17:43 +0400
commit5ac64ba12aca3bef18e61c866583155a3bbf81c4 (patch)
tree7154001c62fce0f307ff43d1a5c02fa3dd7958ed /drivers/media/dvb-frontends/stb0899_reg.h
parentd67350f8c4e67f5eba627e1fd111f16257ca9c95 (diff)
downloadlinux-5ac64ba12aca3bef18e61c866583155a3bbf81c4.tar.xz
[media] dib8000: make 32 bits read atomic
As the dvb-frontend kthread can be called anytime, it can race with some get status ioctl. So, it seems better to avoid one to race with the other while reading a 32 bits register. I can't see any other reason for having a mutex there at I2C, except to provide such kind of protection, as the I2C core already has a mutex to protect I2C transfers. Note: instead of this approach, it could eventually remove the dib8000 specific mutex for it, and either group the 4 ops into one xfer or to manually control the I2C mutex. The main advantage of the current approach is that the changes are smaller and more puntual. Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> Cc: stable@vger.kernel.org Signed-off-by: Mauro Carvalho Chehab <m.chehab@samsung.com> Acked-by: Patrick Boettcher <pboettcher@kernellabs.com>
Diffstat (limited to 'drivers/media/dvb-frontends/stb0899_reg.h')
0 files changed, 0 insertions, 0 deletions