<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"> <head> <meta http-equiv="Content-Type" content="text/html; charset=us-ascii"> <meta name="Generator" content="Microsoft Word 15 (filtered medium)"> <style></style> </head> <body lang="EN-US" link="#0563C1" vlink="#954F72"> <div class="WordSection1"> Hi,<o:p></o:p> I’ll be working on implementing Dynamic Voltage Frequency Scaling in i915, whose rough proposal is provided below. Please go through the options and provide your feedback.<o:p></o:p> <o:p> </o:p> What is DVFS ?<o:p></o:p> Any SKU is capable of running at more than one display CD clock value but is configured to a default value during boot and is left untouched afterwards. Lowering this Display CD clock will result in better power savings while raising this will result in capability to support larger resolution displays. So the best scenario is to always detect the attached displays and adjust the CD Clock to the minimum required by the displays. DVFS is the process of dynamically changing the display CD clock based on attached displays. <o:p></o:p> <o:p> </o:p> Usecases: ( considers low resolution LFP is used with 4K HDMI panel)<o:p></o:p> <![if !supportLists]>Ø <![endif]>EDP (19x10) LFP panel alone is present at boot and can be driven with lower CD clock, thus saving power.<o:p></o:p> <![if !supportLists]>Ø <![endif]>EDP (19x10) LFP panel was present at boot and 4K HDMI display is hot plugged in to the system. CD clock can be increased to the required value and then we can drive 4K panel. Thus save power while only LFP is in use but also provide the ability to support 4K displays.<o:p></o:p> <![if !supportLists]>Ø <![endif]>4K HDMI display is unplugged from the system, CD clock can now be lowered to the value required to drive LFP alone to save power.<o:p></o:p> <![if !supportLists]>Ø <![endif]>Boot with LFP and 4K HDMI connected, the CD clock will be programmed to the value required to drive 4K HDMI.<o:p></o:p> <o:p> </o:p> Technical Restrictions:<o:p></o:p> <![if !supportLists]>Ø <![endif]>DVFS can be performed only when all displays are turned off (pipe/port/plane,etc)<o:p></o:p> <o:p> </o:p> Ux Restrictions: <o:p></o:p> <![if !supportLists]>Ø <![endif]>Flash/flicker should be avoided as much as possible( i.e during unplug of HDMI avoid immediately lowering the CD clock after hotunplug since it will result in flicker on LFP )<o:p></o:p> <o:p> </o:p> Possible Solutions :<o:p></o:p> <![if !supportLists]>Ø <![endif]>Policy + implementation in driver <o:p></o:p> <![if !supportLists]>o <![endif]>Driver will set the cd clock during boot based on attached panels<o:p></o:p> <![if !supportLists]>o <![endif]>Post boot driver has to track each modeset for CD clock and resolution support.<o:p></o:p> <![if !supportLists]>o <![endif]>If any change in CD clock is needed, driver has to disable all displays , change the cd clock and enable back all displays<o:p></o:p> <![if !supportLists]>o <![endif]>Pros:<o:p></o:p> <![if !supportLists]>· <![endif]>Changes are contained within driver<o:p></o:p> <![if !supportLists]>o <![endif]>Cons:<o:p></o:p> <![if !supportLists]>· <![endif]>Complexity increases within driver<o:p></o:p> <![if !supportLists]>· <![endif]>User land/ HWC will be blind to internal operations<o:p></o:p> <![if !supportLists]>Ø <![endif]>Policy in HWC and implementation in driver<o:p></o:p> <![if !supportLists]>o <![endif]>Driver will set the cd clock during boot based on attached panels<o:p></o:p> <![if !supportLists]>o <![endif]>Post boot, driver will fail any modeset that cannot be supported<o:p></o:p> <![if !supportLists]>o <![endif]>HWC will be responsible for disabling all displays, issuing IOCTL to change CD clock and enabling required displays<o:p></o:p> <![if !supportLists]>o <![endif]>Pros:<o:p></o:p> <![if !supportLists]>· <![endif]>Driver implementation will be simple and clean<o:p></o:p> <![if !supportLists]>· <![endif]>User land/HWC will be aware of operations and handle any special cases such as video playback <o:p></o:p> <![if !supportLists]>o <![endif]>Cons:<o:p></o:p> <![if !supportLists]>· <![endif]>Solution requires HWC & Driver changes.<o:p></o:p> <o:p> </o:p> Our recommendation is for HWC + Driver changes considering our primary target of Android and the pros/cons mentioned there. <o:p></o:p> <o:p> </o:p> Sorry for the long mail J, Please provide your feedback or questions on this. <o:p></o:p> <o:p> </o:p> regards,<o:p></o:p> Sivakumar<o:p></o:p> <o:p> </o:p> </div> </body> </html>