aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/net_dropmonitor.py
diff options
context:
space:
mode:
authorTakashi Iwai <[email protected]>2018-09-04 17:58:30 +0200
committerGreg Kroah-Hartman <[email protected]>2018-09-10 11:14:58 +0200
commitda85d3b1a8d4a9f70d4d48b7629f3f215ef9ec40 (patch)
tree8d6cc3247ecca8f94fe784dc5d17bdde3c23ce83 /tools/perf/scripts/python/net_dropmonitor.py
parent7e33f3850c53e10704990f21a160705474f72f43 (diff)
staging: bcm2835-audio: Clean up mutex locks
snd-bcm2835 driver takes the lock with mutex_lock_interruptible() in all places, which don't make sense. Replace them with the simple mutex_lock(). Also taking a mutex lock right after creating it for each PCM object is nonsense, too. It cannot be racy at that point. We can get rid of it. Last but not least, initializing chip->audio_mutex at each place is error-prone. Initialize properly at creating the chip object in snd_bcm2835_create() instead. Signed-off-by: Takashi Iwai <[email protected]> Tested-by: Stefan Wahren <[email protected]> Signed-off-by: Greg Kroah-Hartman <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions