On Mon, Dec 02, 2024 at 12:59:22PM +0000, Mark Brown wrote: > On Mon, Dec 02, 2024 at 01:06:09PM +0100, Maxime Ripard wrote: > > 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 > > > 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. > > It's just what it says, it's a flag saying the device doesn't support > muting the capture side. Right, but then HDMI is output only, so it still doesn't really make sense to me why we'd want to mute the capture side? 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
- Re: [PATCH v5 2/9] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata
- From: Maxime Ripard
- Re: [PATCH v5 2/9] ASoC: hdmi-codec: move no_capture_mute to struct hdmi_codec_pdata
- From: Mark Brown
- [PATCH v5 0/9] drm: add DRM HDMI Codec framework
- Prev by Date: [PATCH v1 RESEND] slimbus: messaging: Free transaction ID in delayed interrupt scenario
- Next by Date: Re: [PATCH v3] ASoC: Intel: avs: da7219: Remove suspend_pre() and resume_post()
- Previous by thread: Re: [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):