-
Notifications
You must be signed in to change notification settings - Fork 12
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
Add start of frame notification for lpcip3511 #5
base: main
Are you sure you want to change the base?
Add start of frame notification for lpcip3511 #5
Conversation
cc @mcuxsusan , can you help get some reviews for this PR. |
05ef2a0
to
29e52b7
Compare
@jzipperer-fb Great work! Thanks for this! Could you reference the issue #7 in the PR summary? Hopefully that'll tie things together and the issue will get closed when this merges. |
29e52b7
to
a422b77
Compare
Done! Anything else needed to get this PR merged? Thanks! |
Let's ask @mcuxcc and @mcuxsusan to take a look 🙏 |
a422b77
to
c2fcea8
Compare
This enables the start of frame interrupt. When a start of frame interrupt occurs, a message is created and sent via USB_DeviceNotificationTrigger. Notifications are gated by the define USB_DEVICE_CONFIG_SOF_NOTIFICATIONS. Some upper layers that use this middleware need start of frame notifications for doing isochronous transfers. This fixes the following issue: nxp-mcuxpresso#7 Signed-off-by: James Zipperer <[email protected]>
c2fcea8
to
a3883c4
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.
Perfect! 🤞 for merge soon!
#This enables the start of frame interrupt. When a start of frame interrupt occurs, a message is created and sent via USB_DeviceNotificationTrigger.
Notifications are gated by the define USB_DEVICE_CONFIG_SOF_NOTIFICATIONS. Some upper layers that use this middleware need start of frame notifications for doing isochronous transfers.
This fixes the following issue:
#7