-
Notifications
You must be signed in to change notification settings - Fork 349
DRC code refactor #8593
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
DRC code refactor #8593
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,7 +6,6 @@ | |
|
|
||
| #include <sof/audio/module_adapter/module/generic.h> | ||
| #include <sof/audio/crossover/crossover_algorithm.h> | ||
| #include <sof/audio/drc/drc_algorithm.h> | ||
| #include <sof/audio/buffer.h> | ||
| #include <sof/audio/format.h> | ||
| #include <sof/audio/ipc-config.h> | ||
|
|
@@ -32,6 +31,8 @@ | |
| #include <errno.h> | ||
| #include <stddef.h> | ||
| #include <stdint.h> | ||
|
|
||
| #include "../drc/drc_algorithm.h" | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. as @marc-hb also has pointed out elsewhere[*], such includes aren't very pretty, would be better to keep shared between modules headers in an "include" directory [*]
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. This isn't a fully clearcut case either. Here multiband_drc is directly building on top of drc (and also uses crossover). I think we should also ensure this type of cross-module resuse is easy to do and code stays maintainable. @lgirdwood Any input, should we keep such reused headers (like drc_algorithm.h) in common code? I think I'd personally still code with the approach in this PR. The modules are deeply dependent on each other, so having a "../drc/drc_algorithm.h" makes sense. Having alone drc_algorithm.h in sof/audio/ seems harder to understand ("why is this header here but not others?").
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I don't have a huge problem with this approach, just looking for the best one. As alternatives we could either
I think I'd find (2) preferable
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Seppo suggested move the common part to math folder in a separate PR, I will do it once those PRs get approval and merged.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
I measured how frequent are these "dot-dot" includes across all the default
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. how about non-zephyr cases? i.e: CONFIG_ZEPHYR_NATIVE_DRIVERS is not defined, will other build also support zephyr syntax? |
||
| #include "multiband_drc.h" | ||
|
|
||
| LOG_MODULE_REGISTER(multiband_drc, CONFIG_SOF_LOG_LEVEL); | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.