mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	 Peter Ujfalusi <peter.ujfalusi@linux.intel.com>,
	 Bard Liao <yung-chuan.liao@linux.intel.com>,
	 Ranjani Sridharan <ranjani.sridharan@linux.intel.com>,
	 Daniel Baluta <daniel.baluta@nxp.com>,
	 Kai Vehmanen <kai.vehmanen@linux.intel.com>,
	 Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	 Chen-Yu Tsai <wenst@chromium.org>
Cc: sound-open-firmware@alsa-project.org,
	linux-sound@vger.kernel.org,  linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoc: SOF: topology: Clear SOF link platform name upon unload
Date: Wed, 28 Aug 2024 17:30:15 +0100	[thread overview]
Message-ID: <172486261586.92851.5753757974025267172.b4-ty@kernel.org> (raw)
In-Reply-To: <20240821041006.2618855-1-wenst@chromium.org>

On Wed, 21 Aug 2024 12:10:04 +0800, Chen-Yu Tsai wrote:
> The SOF topology loading function sets the device name for the platform
> component link. This should be unset when unloading the topology,
> otherwise a machine driver unbind/bind or reprobe would complain about
> an invalid component as having both its component name and of_node set:
> 
>     mt8186_mt6366 sound: ASoC: Both Component name/of_node are set for AFE_SOF_DL1
>     mt8186_mt6366 sound: error -EINVAL: Cannot register card
>     mt8186_mt6366 sound: probe with driver mt8186_mt6366 failed with error -22
> 
> [...]

Applied to

   https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next

Thanks!

[1/1] ASoc: SOF: topology: Clear SOF link platform name upon unload
      commit: e0be875c5bf03a9676a6bfed9e0f1766922a7dbd

All being well this means that it will be integrated into the linux-next
tree (usually sometime in the next 24 hours) and sent to Linus during
the next merge window (or sooner if it is a bug fix), however if
problems are discovered then the patch may be dropped or reverted.

You may get further e-mails resulting from automated or manual testing
and review of the tree, please engage with people reporting problems and
send followup patches addressing any issues that are reported if needed.

If any updates are required or you are submitting further changes they
should be sent as incremental updates against current git, existing
patches will not be replaced.

Please add any relevant lists and maintainers to the CCs when replying
to this mail.

Thanks,
Mark


      reply	other threads:[~2024-08-28 16:30 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-21  4:10 Chen-Yu Tsai
2024-08-28 16:30 ` Mark Brown [this message]

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=172486261586.92851.5753757974025267172.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=daniel.baluta@nxp.com \
    --cc=kai.vehmanen@linux.intel.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter.ujfalusi@linux.intel.com \
    --cc=pierre-louis.bossart@linux.intel.com \
    --cc=ranjani.sridharan@linux.intel.com \
    --cc=sound-open-firmware@alsa-project.org \
    --cc=tiwai@suse.com \
    --cc=wenst@chromium.org \
    --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

all inboxes | Powered by JetHome®