Linux Sound subsystem development
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, linux-sound@vger.kernel.org,
	kai.vehmanen@linux.intel.com, ranjani.sridharan@linux.intel.com,
	yung-chuan.liao@linux.intel.com, pierre-louis.bossart@linux.dev,
	liam.r.girdwood@intel.com
Subject: Re: [PATCH 5/8] ASoC: SOF: ipc4: Add support for Intel HW managed mic privacy messaging
Date: Thu, 6 Mar 2025 17:37:12 +0200	[thread overview]
Message-ID: <97847fb3-3659-489c-a6a5-3a76cb048523@linux.intel.com> (raw)
In-Reply-To: <07d7106e-97fe-4895-a471-db09f7a169e9@sirena.org.uk>



On 06/03/2025 15:42, Mark Brown wrote:
> On Thu, Mar 06, 2025 at 03:35:24PM +0200, Peter Ujfalusi wrote:
> 
>> Platform code can call sof_ipc4_mic_privacy_state_change() to send the IPC
>> message to the firmware on state change.
> 
> What's the plan for that plaform code - is it expected to be the machine
> driver, or something else?

By platform code I mean here sound/soc/sof/intel.

This feature is only available for Intel hardware, but I wanted to keep
the APIs as open as possible for other vendors.

The reason for the implementation is that the interrupt about the change
in mic privacy is delivered via IP interrupt (piggy-backing on them).
The interrupt is delivered to the owner of the IP:
DMIC is owned by DSP, so firmware can handle it
SNDW is owned by host, so Linux is handling it.
The firmware needs to be notified of a change to do a nice fade out/in,
the software cannot block or do anything else, the incoming stream mute
is done by the hardware.

No plan to integrate it to machine drivers, this is outside of the scope
of SW. The feedback is also handled by hardware internally.

-- 
Péter


  reply	other threads:[~2025-03-06 15:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-06 13:35 [PATCH 0/8] ASoC: SOF: Intel: Add support for ACE3+ mic privacy Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 1/8] ASoC: SOF: Intel: mtl: Split up dsp_ops setup code Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 2/8] ASoC: SOF: Intel: lnl/ptl: Only set dsp_ops which differs from MTL Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 3/8] ASoC: SOF: Intel: mtl: Stop exporting dsp_ops callback functions Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 4/8] ASoC: SOF: Intel: Create ptl.c as placeholder for Panther Lake features Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 5/8] ASoC: SOF: ipc4: Add support for Intel HW managed mic privacy messaging Peter Ujfalusi
2025-03-06 13:42   ` Mark Brown
2025-03-06 15:37     ` Péter Ujfalusi [this message]
2025-03-06 13:35 ` [PATCH 6/8] ASoC: SOF: Intel: hda-mlink: Add support for mic privacy in VS SHIM registers Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 7/8] ASoC: SOF: hda/shim: Add callbacks to handle mic privacy change for sdw Peter Ujfalusi
2025-03-06 13:35 ` [PATCH 8/8] ASoC: SOF: Intel: ptl: Add support for mic privacy Peter Ujfalusi
2025-03-06 14:05   ` Amadeusz Sławiński
2025-03-06 15:40     ` Péter Ujfalusi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=97847fb3-3659-489c-a6a5-3a76cb048523@linux.intel.com \
    --to=peter.ujfalusi@linux.intel.com \
    --cc=broonie@kernel.org \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=liam.r.girdwood@intel.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=pierre-louis.bossart@linux.dev \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=yung-chuan.liao@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox