Hi, On Sun, Dec 01, 2024 at 02:44:06AM +0200, Dmitry Baryshkov wrote: > The no_capture_mute flag might differ from platform to platform, > especially in the case of the wrapping implementations, like the > upcoming DRM HDMI Codec framework. Move the flag next to all other flags > in struct hdmi_codec_pdata. > > Acked-by: Mark Brown <broonie@xxxxxxxxxx> > Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@xxxxxxxxxx> I appreciate it might be a dumb question, but I never really understood what no_capture_mute was all about. And in that context, why some drivers would need / use it, and some won't. Maxime
Attachment:
signature.asc
Description: PGP signature
- Follow-Ups:
- References:
- [PATCH v5 0/9] drm: add DRM HDMI Codec framework
- From: Dmitry Baryshkov
- [PATCH v5 2/9] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata
- From: Dmitry Baryshkov
- [PATCH v5 0/9] drm: add DRM HDMI Codec framework
- Prev by Date: Support for Creative Soundblaster AE-9 ?
- Next by Date: Re: [bug report] ALSA: usb-audio: Add quirk to enable Avid Mbox 3 support
- Previous by thread: [PATCH v5 2/9] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata
- Next by thread: Re: [PATCH v5 2/9] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata
- Index(es):