Bug 12600 – Implemented 'power failing' flag in MSP, kernel needs to shut down the headphone amp

Bug 12600 - Implemented 'power failing' flag in MSP, kernel needs to shut down the headphone amp

Summary:

Implemented 'power failing' flag in MSP, kernel needs to shut down the headph...

Status:	RESOLVED WONTFIX

Product:	SB Radio
Classification:	Unclassified
Component:	Power Management
Version:	Include FW version in comment
Platform:	PC Other

Importance:	-- normal (vote)
Target Milestone:	---
Assigned To:	Unassigned bug - please assign me!

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2009-06-30 00:11 UTC by Caleb Crome
Modified:	2019-01-25 10:38 UTC (History)
CC List:	0 users

See Also:
Category:	---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Caleb Crome 2009-06-30 00:11:38 UTC

Bit 5 of the MSP interrupt flag register is a power failing bit.

If this bit gets set this means the system is going down RIGHT NOW.  You have about 50mS to do any cleanup necessary before the power goes off.

The necessary cleanup that I know of now is that the DAC headphone amplifier needs to be shut down to prevent nasty noise on it.  This should be done in the interrupt handler if possible, not in the work thread, since you only have 50mS to get the job done.

Comment 1 Caleb Crome 2009-06-30 00:12:36 UTC

BTW, this is in revision r6214 of the msp code.

Comment 2 Chris Owens 2009-07-07 10:15:06 UTC

This bug has been identified as one that may not be required for MPQ since it now seems clear that MPQ and MP firmwares will be different.  Please comment if you disagree with this assessment.  Thanks!

Comment 3 Richard Titmuss 2009-07-08 11:37:00 UTC

*** Bug 12482 has been marked as a duplicate of this bug. ***

Comment 4 Richard Titmuss 2009-07-21 16:09:15 UTC

Caleb, you need to decide how this will work...

Comment 5 Richard Titmuss 2009-07-27 01:09:43 UTC

Reset priority before triage.

Comment 6 Chris Owens 2009-07-27 09:50:31 UTC

It seems like it may already be too late for MP.  This is unfortunate if we ship with this.

Comment 7 Caleb Crome 2009-07-27 13:49:44 UTC

This is not needed for MP -- only for 7.4.

Comment 8 Caleb Crome 2009-07-28 22:23:12 UTC

*** Bug 12768 has been marked as a duplicate of this bug. ***

Comment 9 Ben Klaas 2009-08-26 07:51:42 UTC

this is an administrative shuffle on priority fields to help make better judgment on the top end of the priority list. P4->P5, P3->P4, and P2->P3.

Comment 10 Alan Young 2011-11-06 23:23:58 UTC

Unassigned bugs cannot have a priority.