PM Debug about Interrupts Counts Reduction on MX6DL

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

PM Debug about Interrupts Counts Reduction on MX6DL

1,157 Views
tony_l_cai
Contributor III

Dear all,

     I have read the article i.MX Android Debug Tips for Power Management .

And from the article,I want to know how to reduce the the interrupt count?

And from our customize board,we can find the interrupts info below, what can I set about dong ? Could you give me some steps in details? Thanks~

cat /proc/interrupts

           CPU0       CPU1

34:          1          0       GIC  sdma

35:          0          0       GIC  VPU_JPG_IRQ

37:          2          0       GIC  imx-ipuv3

38:        724          0       GIC  imx-ipuv3

41:        580          0       GIC

42:        386          0       GIC

44:          0          0       GIC  VPU_CODEC_IRQ

50:          0          0       GIC  vdoa

54:          0          0       GIC  mmc2

55:      74117          0       GIC  mmc1

56:      19665          0       GIC  mmc0

58:          2          0       GIC  IMX-uart

62:       2102          0       GIC  IMX-uart

68:        302          0       GIC  imx-i2c

69:        403          0       GIC  imx-i2c

70:          0          0       GIC  imx-i2c

72:        157          0       GIC  usb_wakeup, fsl ehci pre interrupt, ehci_hcd:usb2

75:        389          0       GIC  usb_wakeup, fsl-usb2-otg, fsl ehci pre interrupt, ehci_hcd:usb1, fsl-usb2-udc

81:          0          0       GIC  THERMAL_ALARM_IRQ

82:          0          0       GIC  asrc

87:     770306          0       GIC  i.MX Timer Tick

112:          0          0       GIC  imx2-wdt

121:          0          0       GIC  dvfs

139:          0          0       GIC  mmdc_1

144:          0          0       GIC  mmdc_1

150:      58469          0       GIC  enet

256:          0          0      GPIO  micphone detect

258:          0          0      GPIO  mmc2

293:       6982          0      GPIO  bcmsdh_sdmmc

299:          0          0      GPIO  wm831x

331:          0          0      GPIO  btn keyotg

349:          0          0      GPIO  btn pwrbtn

386:          0          0      GPIO  USB_wake_up

399:          8          0      GPIO  bt_host_wake_irq_handler

646:          0          0    wm831x  RTC period

647:          0          0    wm831x  RTC alarm

659:          0          0    wm831x  auxadc

680:          0          0    wm831x  DCDC3

681:          0          0    wm831x  DCDC4

IPI0:          0     550654  Timer broadcast interrupts

IPI1:     107498     189315  Rescheduling interrupts

IPI2:          0          0  Function call interrupts

IPI3:        562        570  Single function call interrupts

IPI4:          0          0  CPU stop interrupts

IPI5:          0          0  CPU backtrace

LOC:     672329      62604  Local timer interrupts

Labels (3)
0 Kudos
Reply
1 Reply

974 Views
igorpadykov
NXP Employee
NXP Employee

Hi tony

link which you referenced explains:

"consider..whether we have some chances to reduce the interrupt count. "

so module activity (and its interrupt count) is controlled by Android higher layers.

Most simple way is to disable some functionality or put it on suspend (inactive) mode,

remove rarely used apps from memory.

Best regards

igor

-----------------------------------------------------------------------------------------------------------------------

Note: If this post answers your question, please click the Correct Answer button. Thank you!

-----------------------------------------------------------------------------------------------------------------------

0 Kudos
Reply