<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Implementing Power Notification Callbacks in Intel Integrated Sensor Solution FDK IDE in Embedded Intel® Core™ Processors</title>
    <link>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1377311#M4175</link>
    <description>&lt;P&gt;Hi there, I want to ask about Intel Integrated Sensor Solution FDK IDE and some contradicting ideas from its guide:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1)&amp;nbsp;&amp;nbsp;&lt;SPAN class="resultofText"&gt;Auto&lt;/SPAN&gt;&lt;SPAN&gt;matically Maintained &lt;/SPAN&gt;&lt;SPAN class="resultofText"&gt;Code&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN class="resultofText"&gt;The built-in user guide suggests to never "&lt;/SPAN&gt;&lt;SPAN&gt;manually edit the files in the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN class="resultofText"&gt;auto&lt;/SPAN&gt;&lt;SPAN&gt;_&lt;/SPAN&gt;&lt;SPAN class="resultofText"&gt;generated&lt;/SPAN&gt;&lt;SPAN&gt;_&lt;/SPAN&gt;&lt;SPAN class="resultofText"&gt;code&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; folder. Any changes you introduce will at best be overwritten, and at worst render your sensor permanently unusable."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;2) Getting event notifications from CS state change (i.e. enter/exit ModernStandby)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;The built-in user guide shows steps how to do this for a virtual driver:&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;◦In its init callback, add notification mask SC_NOTIFY_HOST_OS_STATE_CHANGE_CS to algo_create_sensor function’s forth parameter.&lt;BR /&gt;◦In its init callback, call algo_register_notify_event_callback(context, &amp;amp;xxx_notify_handler) to register your notification handler.&lt;BR /&gt;◦In xxx_notify_handler, handle host CS state change as below: &lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;    sc_status xxx_notify_handler(INOUT algo_context *context,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                                 INOUT void *private_data,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                                 IN sc_event_notification_event_id event_id,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                                 IN sc_event_info event_info)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;   {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        if (event_id == SC_NOTIFY_HOST_OS_STATE_CHANGE_CS)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            if (event_info.sc_notify_sensor_sys_state.system_state_statuses &amp;amp; SYS_STATE_CONNECTED_STANDBY)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                // Enter connected standby, add your code&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                ……..&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            }&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            else&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                //Exit connected standby&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                ………&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            }&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        }&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        return SC_STATUS_SUCCESS;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;    }&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;Problem: The functions &lt;STRONG&gt;algo_create_sensor &lt;/STRONG&gt;and&amp;nbsp;&lt;STRONG&gt;algo_register_notify_event_callback&amp;nbsp;&lt;/STRONG&gt;are already used in the auto generated code portion of the project, attempting to change this auto_generated code violates Guide #1 Premise, and attempting to do first and second bullet of Guide #2 consequently will require modification in auto_generated code. This poses a dilemma because we want to implement notification of CS State Change, but we do not want to modify any part of the auto generated codes.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to hear your suggestions that would best resolve this issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you and regards,&lt;/P&gt;
&lt;DIV class="PageDoc"&gt;
&lt;DIV class="contents"&gt;
&lt;DIV class="textblock"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
    <pubDate>Fri, 15 Apr 2022 03:04:55 GMT</pubDate>
    <dc:creator>jer_one</dc:creator>
    <dc:date>2022-04-15T03:04:55Z</dc:date>
    <item>
      <title>Implementing Power Notification Callbacks in Intel Integrated Sensor Solution FDK IDE</title>
      <link>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1377311#M4175</link>
      <description>&lt;P&gt;Hi there, I want to ask about Intel Integrated Sensor Solution FDK IDE and some contradicting ideas from its guide:&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;1)&amp;nbsp;&amp;nbsp;&lt;SPAN class="resultofText"&gt;Auto&lt;/SPAN&gt;&lt;SPAN&gt;matically Maintained &lt;/SPAN&gt;&lt;SPAN class="resultofText"&gt;Code&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN class="resultofText"&gt;The built-in user guide suggests to never "&lt;/SPAN&gt;&lt;SPAN&gt;manually edit the files in the &lt;/SPAN&gt;&lt;STRONG&gt;&lt;SPAN class="resultofText"&gt;auto&lt;/SPAN&gt;&lt;SPAN&gt;_&lt;/SPAN&gt;&lt;SPAN class="resultofText"&gt;generated&lt;/SPAN&gt;&lt;SPAN&gt;_&lt;/SPAN&gt;&lt;SPAN class="resultofText"&gt;code&lt;/SPAN&gt;&lt;/STRONG&gt;&lt;SPAN&gt; folder. Any changes you introduce will at best be overwritten, and at worst render your sensor permanently unusable."&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&lt;SPAN&gt;2) Getting event notifications from CS state change (i.e. enter/exit ModernStandby)&lt;/SPAN&gt;&lt;/P&gt;
&lt;P class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;The built-in user guide shows steps how to do this for a virtual driver:&lt;/SPAN&gt;&lt;/P&gt;
&lt;PRE class="lia-indent-padding-left-30px"&gt;&lt;SPAN&gt;◦In its init callback, add notification mask SC_NOTIFY_HOST_OS_STATE_CHANGE_CS to algo_create_sensor function’s forth parameter.&lt;BR /&gt;◦In its init callback, call algo_register_notify_event_callback(context, &amp;amp;xxx_notify_handler) to register your notification handler.&lt;BR /&gt;◦In xxx_notify_handler, handle host CS state change as below: &lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;    sc_status xxx_notify_handler(INOUT algo_context *context,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                                 INOUT void *private_data,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                                 IN sc_event_notification_event_id event_id,&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                                 IN sc_event_info event_info)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;   {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        if (event_id == SC_NOTIFY_HOST_OS_STATE_CHANGE_CS)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            if (event_info.sc_notify_sensor_sys_state.system_state_statuses &amp;amp; SYS_STATE_CONNECTED_STANDBY)&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                // Enter connected standby, add your code&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                ……..&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            }&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            else&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            {&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                //Exit connected standby&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;                ………&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;            }&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        }&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;        return SC_STATUS_SUCCESS;&lt;/FONT&gt;&lt;BR /&gt;&lt;FONT face="courier new,courier" size="2"&gt;    }&lt;/FONT&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/PRE&gt;
&lt;P&gt;Problem: The functions &lt;STRONG&gt;algo_create_sensor &lt;/STRONG&gt;and&amp;nbsp;&lt;STRONG&gt;algo_register_notify_event_callback&amp;nbsp;&lt;/STRONG&gt;are already used in the auto generated code portion of the project, attempting to change this auto_generated code violates Guide #1 Premise, and attempting to do first and second bullet of Guide #2 consequently will require modification in auto_generated code. This poses a dilemma because we want to implement notification of CS State Change, but we do not want to modify any part of the auto generated codes.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;We would like to hear your suggestions that would best resolve this issue.&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Thank you and regards,&lt;/P&gt;
&lt;DIV class="PageDoc"&gt;
&lt;DIV class="contents"&gt;
&lt;DIV class="textblock"&gt;&amp;nbsp;&lt;/DIV&gt;
&lt;/DIV&gt;
&lt;/DIV&gt;</description>
      <pubDate>Fri, 15 Apr 2022 03:04:55 GMT</pubDate>
      <guid>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1377311#M4175</guid>
      <dc:creator>jer_one</dc:creator>
      <dc:date>2022-04-15T03:04:55Z</dc:date>
    </item>
    <item>
      <title>Re: Implementing Power Notification Callbacks in Intel Integrated Sensor Solution FDK IDE</title>
      <link>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1377404#M4176</link>
      <description>&lt;P&gt;Hello,&amp;nbsp;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/231647"&gt;@jer_one&lt;/a&gt;:&lt;/P&gt;
&lt;P&gt;Thank you for contacting Intel Embedded Community.&lt;/P&gt;
&lt;P&gt;We want to address the following questions:&lt;/P&gt;
&lt;P&gt;Could you please let us know the part number of the processors related to this situation?&lt;/P&gt;
&lt;P&gt;What is the procedure that you have followed to obtain the software related to this situation? Please mention its version.&lt;/P&gt;
&lt;P&gt;Best regards,&lt;/P&gt;
&lt;P&gt;&lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/114"&gt;@CarlosAM_INTEL&lt;/a&gt;.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 15 Apr 2022 13:33:40 GMT</pubDate>
      <guid>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1377404#M4176</guid>
      <dc:creator>CarlosAM_INTEL</dc:creator>
      <dc:date>2022-04-15T13:33:40Z</dc:date>
    </item>
    <item>
      <title>Re: Implementing Power Notification Callbacks in Intel Integrated Sensor Solution FDK IDE</title>
      <link>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1378117#M4177</link>
      <description>&lt;P&gt;Hi &lt;a href="https://community.intel.com/t5/user/viewprofilepage/user-id/114"&gt;@CarlosAM_INTEL&lt;/a&gt;&amp;nbsp;,&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;It appears we have a way to raise this concern to Intel internally, and I have been advised to take it there instead of discussing the matter in public. Sorry for the inconvenience, but thank you for your prompt response.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;Regards,&lt;/P&gt;</description>
      <pubDate>Tue, 19 Apr 2022 12:25:30 GMT</pubDate>
      <guid>https://community.intel.com/t5/Embedded-Intel-Core-Processors/Implementing-Power-Notification-Callbacks-in-Intel-Integrated/m-p/1378117#M4177</guid>
      <dc:creator>jer_one</dc:creator>
      <dc:date>2022-04-19T12:25:30Z</dc:date>
    </item>
  </channel>
</rss>

