Re: Maestro 2E vs. Power mgmt

[Patrick Mochel]

On Thu, 15 Nov 2001, Faux Pas III wrote:

> On Thu, Nov 15, 2001 at 09:29:27AM -0800, Patrick Mochel wrote:
>
> > Could you do a lspci -vv as root on that device both with AC and without?

Sorry, I meant something like 'lspci -vv -s 00:0c.0' :)

>
> On AC:
>
> frabjous:~# lspci -vv
	...
> 00:0c.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
>         Subsystem: Toshiba America Info Systems ES1978 Maestro-2E Audiodrive
>         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (500ns min, 6000ns max)
>         Interrupt: pin A routed to IRQ 11
>         Region 0: I/O ports at ee00 [size=256]
>         Capabilities: [c0] Power Management version 2
>                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
>                 Status: D2 PME-Enable- DSel=0 DScale=0 PME-
                         ^^^^
>
> frabjous:~#
>
> And on battery:
>
> frabjous:~# lspci -vv
	...
> 00:0c.0 Multimedia audio controller: ESS Technology ES1978 Maestro 2E (rev 10)
>         Subsystem: Toshiba America Info Systems ES1978 Maestro-2E Audiodrive
>         Control: I/O+ Mem- BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 64 (500ns min, 6000ns max)
>         Interrupt: pin A routed to IRQ 11
>         Region 0: I/O ports at ee00 [size=256]
>         Capabilities: [c0] Power Management version 2
>                 Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA PME(D0-,D1+,D2+,D3hot+,D3cold-)
>                 Status: D2 PME-Enable- DSel=0 DScale=0 PME-
                         ^^^^

It says in both cases that the device is in D2; ah yes, the device is not
open and the driver cuts the power on ess_release().

Are you noticing any performance degradation for any other devices?

(On a side note, it looks like the driver is manually touching a lot of
PCI config space rather than using the pci_ wrappers...)

	-pat