-
Notifications
You must be signed in to change notification settings - Fork 321
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
Tools: Topology2: Add widget class IGO NR #8450
Conversation
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.
@@ -0,0 +1,91 @@ | |||
# | |||
# | |||
# A generic IGO_NR component. All attributes defined herein are namespaced |
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.
I suggest add full name of IGO_NR in a place, let everyone know what exactly IGO_NR is.
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.
@singalsu , are you adding full name for IGO_NR?
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.
Yep, I will update this simple PR next. Don't approve yet.
} | ||
Object.Base.ops.1 { | ||
name "ctl" | ||
info "volsw" |
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.
add comment for what "volsw" is, for all abbreviation names that not so obvious to know the meanning.
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.
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.
The legal values are "volsw", "volsw_sx" and "volsw_xr_sx", and the value describes the kcontrol type of the mixer. It somehow describes how the mixer values are interpreted. The relevant functions are implemented in sound/soc/soc-ops.c, but I can not immediately say what is the relevant difference, or find any piece of documentation describing it.
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.
Thanks @jsarha I'll check if I can understand what they are and add a comment. This has not been clear to me either, I've just copied working topology examples from others.
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.
Volsw is the single (mono) or double (stereo) mixer control. The _sx version is for use where signed values can be both sides of zero. _xr_sx is some multi-register to single combine control. I'll add some comment but it's not going to be well descriptive. E.g. ALSA documentation is not describing these, only lists the operations names @jsarha mentioned above.
This patch allows to build topologies to use the IGO NR component. Signed-off-by: Seppo Ingalsuo <[email protected]>
This patch adds build of hda-generic development topologies to test IGO NR component with all s16/s24/s32 formats. Signed-off-by: Seppo Ingalsuo <[email protected]>
3826070
to
2101f88
Compare
No description provided.