> -----Original Message----- > From: Peter 'p2' De Schrijver [mailto:peter.de-schrijver@xxxxxxxxx] > Sent: Monday, May 17, 2010 4:29 PM > To: ext Lesly Arackal Manuel > Cc: linux-omap@xxxxxxxxxxxxxxx; 'Lesly A M'; 'Nishanth Menon'; 'David > Derrick'; 'Samuel Ortiz' > Subject: Re: [PATCH v5 3/5] omap3: pm: Generic TRITON power > scriptsforOMAP3 based boards > > Hi, > > > > > Hi Peter, > > > > The RES_TYPE field is same for all messages. > > > > The resource which can go to low-power mode with clk_req sig de- > asserting is > > configured as RES_TYPE2 = '2'. And the resource which can go to low- > power > > mode with sys_off sig de-asserting is configured as RES_TYPE2 = '1'. > > > > The RES_TYPE2 is '2' for P3 wakeup and the msg will applicable for > Resource > > which have their TYPE2 field configured '2' (RES_VINTANA1, RES_VINTANA2, > > RES_VINTDIG, VIO, RES_CLKEN, RES_HFCLKOUT). > > > > RES_TYPE2 = '1' for P1_P2 wakeup. > > (Applicable for res: RES_VPLL1, RES_VDD1, RES_VDD2, RES_REGEN, > > RES_NRES_PWRON, RES_SYSEN) > > > > Ok. But why not just assign the resources to the appropriate groups ? > Eg. assign VIO to P3 and assign VPLL1 to P1_P2 ? Then you only need one > message type. Also, why are you using RES_TYPE2 instead of RES_TYPE ? > Hi Peter, This sequence is recommended by the Hardware team. Because some resource have non-zero reset values for RES_TYPE, and may be used in some other seq (eg: power_up). Regards, Lesly A M -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
