28 Apr
2004
28 Apr
'04
8:50 p.m.
Hi all,
I'm trying to reset the latency_timer on my on-board nforce2 sound
to 32 instead of 0, but it doesn't seem to work. I issue the command
"setpci -v -s 00:06.0 latency_timer=20 as root, but lspci still shows
the latency as being 0. Any ideas?
00:06.0 Multimedia audio controller: nVidia Corporation nForce2 AC97
Audio Controler (MCP) (rev a1)
Subsystem: Asustek Computer, Inc.: Unknown device 8095
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr-
Stepping- SERR- FastB2B-
Status: Cap+ 66Mhz+ UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort-
<TAbort- <MAbort- >SERR- <PERR-
Latency: 0 (500ns min, 1250ns max)
Interrupt: pin A routed to IRQ 10
Region 0: I/O ports at e800 [size=256]
Region 1: I/O ports at e000 [size=128]
Region 2: Memory at e6083000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [44] Power Management version 2
Flags: PMEClk- DSI- D1+ D2+ AuxCurrent=0mA
PME(D0-,D1-,D2-,D3hot-,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
TIA
Rick B
28 Apr
28 Apr
9:27 p.m.
rix wrote:
Hi all,
I'm trying to reset the latency_timer on my on-board nforce2 sound to
32 instead of 0, but it doesn't seem to work. I issue the command
"setpci -v -s 00:06.0 latency_timer=20 as root, but lspci still shows
the latency as being 0. Any ideas?
Since your device reports it is a PCI Bus Master is is possible that it
is wrteable, but not guaranteed so.
The PCI spec does not require the latency timer be a writeable register.
You may have a device that has a hard coded value.
1) The latency timer register only needs to be writeable if the PCI
device is a Bus Master and capable of bursting more than two data
phases. If the device bursts two or fewer data phases then the
read-only value must be less than 16. (0 is less than 16 so this fits
the rule.)
2) If the device is capable of bursting more than two data phases then
it's reset value should be 0, which you are seeing, and hence your
command is not correctly writing it. This could be that you ae writing
to the wrong device or that setpci is doing something wrong. Unlikely,
but to check this you might try writing a different register like
possibly Base Address or some other register known to be writable. (If
you do use Base Address then reboot after testing.
I suspect that #1 is the real cause.
Cheers,
Mark
7547
days inactive
7547
days old
linux-audio-user@lists.linuxaudio.org
1 comments
2 participants
participants (2)
-
Mark Knecht -
rix