ALSA: pcsp: Fix initialization with nopcm=1
authorTakashi Iwai <tiwai@suse.de>
Tue, 29 Oct 2013 14:15:20 +0000 (15:15 +0100)
committerTakashi Iwai <tiwai@suse.de>
Tue, 29 Oct 2013 14:15:20 +0000 (15:15 +0100)
When nopcm=1 is set, some initializations based on hrtimer resolution
might be bogus because the driver checks the resolution only when
nopcm=0.  Simply get the resolution always at first for fixing the
bug.

Spotted by coverity CID 139740.

Signed-off-by: Takashi Iwai <tiwai@suse.de>

No differences found