- 
                Notifications
    
You must be signed in to change notification settings  - Fork 720
 
[nrf noup] mbox: Temporary workaround for SCFW not capturing some ic-… #2531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
| 
               | 
          ||
| nrfy_vpr_task_trigger(config->vpr, nrfy_vpr_trigger_task_get(id)); | ||
| 
               | 
          ||
| k_busy_wait(VEVIF_RETRIGGER_DELAY); | 
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
#include <zephyr/kernel.h> missing for k_busy wait
2413282    to
    bc6a722      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
why is this a noup?
          
 Don't know what it should be - for the moment this is a workaround so that we can make a SDSC release. We are still investigating and we hope to find the root cause - so that we can elimate this workaround.  | 
    
bc6a722    to
    392c2f4      
    Compare
  
    392c2f4    to
    733703d      
    Compare
  
    There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, assuming a noup is acceptable until the root cause of HM-25973 is found
8784712    to
    2fa8450      
    Compare
  
    When a LD sends an ic-msg to SCFW - it happens that sometimes that SCFW does not handle the request. For the moment the problem is solved by sending a second vevif event shortly after the initial request. Upstream PR #: 86455 Signed-off-by: Maciej Meijer <[email protected]>
2fa8450    to
    27f863e      
    Compare
  
    
Woraround that sends a second vevif SW trigger. It seems that SCFW does not always catches each vevif IRQ - therefore a second time the vevif task will be triggered as a temporary workaround.