On Tue, Sep 13, 2011 at 3:25 PM, Enrico <ebut...@users.berlios.de> wrote: > On Tue, Sep 13, 2011 at 12:29 PM, Tero Kristo <t-kri...@ti.com> wrote: >> Powerdomain is automatically on if there are any clocks enabled on it. >> If you make sure that ISP has some activity ongoing, then it should be >> on. You can check the state of the camera powerdomain >> from /sys/kernel/debug/pm_debug/count file, if you have mounted debugfs. > > And in fact something seems wrong (this is on a patched 3.0.4 kernel): > > usbhost_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 > sgx_pwrdm (OFF),OFF:1,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 > per_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 > dss_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 > cam_pwrdm (RET),OFF:0,RET:9,INA:0,ON:9,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 > core_pwrdm > (ON),OFF:0,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0 > neon_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0 > mpu_pwrdm (ON),OFF:0,RET:0,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 > iva2_pwrdm > (RET),OFF:0,RET:1,INA:0,ON:1,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0,RET-MEMBANK2-OFF:0,RET-MEMBANK3-OFF:0,RET-MEMBANK4-OFF:0 > per_clkdm->per_pwrdm (20) > usbhost_clkdm->usbhost_pwrdm (3) > cam_clkdm->cam_pwrdm (0) > dss_clkdm->dss_pwrdm (1) > core_l4_clkdm->core_pwrdm (23) > core_l3_clkdm->core_pwrdm (4) > d2d_clkdm->core_pwrdm (0) > sgx_clkdm->sgx_pwrdm (0) > iva2_clkdm->iva2_pwrdm (0) > neon_clkdm->neon_pwrdm (0) > mpu_clkdm->mpu_pwrdm (0) > prm_clkdm->wkup_pwrdm (0) > cm_clkdm->core_pwrdm (0) > > > I think the line "cam_clkdm->cam_pwrdm (0)" means that it was never > enabled, but i grabbed some frames with yavta before that.
Forget that, i was wrong. While yavta is running (or better to say: hanged waiting for frames) i have this: cam_pwrdm (ON),OFF:0,RET:6,INA:0,ON:7,RET-LOGIC-OFF:0,RET-MEMBANK1-OFF:0 cam_clkdm->cam_pwrdm (3) So it seems that clocks/power domains are "acquired" correctly but ignored. And from /proc/interrupts i can see the isp counter increasing (while yavta is hanged waiting for frames). Is it possibile this happens only because some pm_runtime_enable/disable/get/put are missing in omap3isp? Thanks, Enrico -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
