terry0012 opened a new pull request, #22031:
URL: https://github.com/apache/nuttx/pull/22031

   ## Summary
   
   This series updates framebuffer synchronization in four commits:
   
   1. Revert the character-device mutex introduced by
      249df8c1d9f4942b7105344ccd01d051bd7b3957. This mutex only
      serializes selected character-device operations; it does not
      synchronize direct mmap writes or display scanout. 
      User should sync the framebuffer in the render application.
   2. Replace global critical sections with a per-framebuffer spinlock
      to protect shared driver state, including pan queues and open-file
      state. Use the nopreempt variants when notifying waiters.
   3. Preserve semaphore notifications when the pan queue becomes writable
      before a thread starts waiting, and reset stale semaphore counts
      when the queue becomes full again.
   4. Prevent preemption while holding the framebuffer spinlock in
      fb_sem_reset(), avoiding the associated SMP deadlock.
   
   ## Impact
   
   - Changes are limited to drivers/video/fb.c.
   - No public ioctl or Kconfig interfaces are changed.
   - Existing non-contiguous framebuffer support is preserved.
   - The revert removes the previous character-device operation
     serialization. Applications remain responsible for coordinating
     framebuffer access and rendering.
   - This series does not introduce a buffer-ownership protocol or
     guarantee tear-free presentation for mmap users.
   
   ## Testing
   
   Static validation completed:
   
   - Passed checkpatch.sh commit-message checks for all four commits.
   - Passed checkpatch.sh -f drivers/video/fb.c.
   - Passed git diff --check for the complete series.
   - Compared the ported patches against their source changes, accounting
     for the semaphore API adaptation and formatting adjustments.
   
   Firmware build, hardware testing and SMP runtime validation have not
   been performed as part of this validation.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to