-
Notifications
You must be signed in to change notification settings - Fork 8k
samples: i2s_codec: Refine i2s_codec sample #96976
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
Open
ZhaoxiangJin
wants to merge
1
commit into
zephyrproject-rtos:main
Choose a base branch
from
nxp-upstream:refine-i2s-codec-example
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+33
−16
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
const is probably not necessary here. See the reported issue: when cast to (void *) in main.c, const is lost.
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.
Hello @TomasBarakNXP, currently, both
__16kHz16bit_stereo_sine_pcm
and__16kHz16bit_stereo_sine_pcm_len
are modified with const. I'm not sure what the "reported issue" you're referring to is. However, I understand that it's worth keeping the const declarations in both places.Why is it worth keeping the const declaration for
__16kHz16bit_stereo_sine_pcm
?__16kHz16bit_stereo_sine_pcm
is used here:The prototype of
i2s_buf_write
is:int i2s_buf_write(const struct device *dev, void *buf, size_t size)
, and the implementation only memcpy data frombuf
to the driver-allocated TXslab
and then transmits it via DMA,buf
is not modified (see drivers/i2s/i2s_common.c: memcpy(mem_block, (void *)buf, size)).The code
mem_block = (void)&__16kHz16bit_stereo_sine_pcm;
simply casts the parameter to "lose const" to accommodate the void parameter ofi2s_buf_write
. Since the function only reads it, this is safe; the only drawback is that it's not perfectly const-correct. In other words, the lack of const API parameters is due to historical reasons/interface design issues, the actual source buffer is read-only.Why is it worth keeping the const for
__16kHz16bit_stereo_sine_pcm_len
?