mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Richard Fitzgerald <rf@opensource.cirrus.com>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
	 linux-kernel@vger.kernel.org, patches@opensource.cirrus.com
Subject: Re: [PATCH] ASoC: cs35l56: Must clear HALO_STATE before issuing SYSTEM_RESET
Date: Wed, 21 Feb 2024 00:51:39 +0000	[thread overview]
Message-ID: <170847669920.72316.9216524053259588241.b4-ty@kernel.org> (raw)
In-Reply-To: <20240216140535.1434933-1-rf@opensource.cirrus.com>

On Fri, 16 Feb 2024 14:05:35 +0000, Richard Fitzgerald wrote:
> The driver must write 0 to HALO_STATE before sending the SYSTEM_RESET
> command to the firmware.
> 
> HALO_STATE is in DSP memory, which is preserved across a soft reset.
> The SYSTEM_RESET command does not change the value of HALO_STATE.
> There is period of time while the CS35L56 is resetting, before the
> firmware has started to boot, where a read of HALO_STATE will return
> the value it had before the SYSTEM_RESET. If the driver does not
> clear HALO_STATE, this would return BOOT_DONE status even though the
> firmware has not booted.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: cs35l56: Must clear HALO_STATE before issuing SYSTEM_RESET
      commit: e33625c84b75e4f078d7f9bf58f01fe71ab99642

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-02-21  0:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-16 14:05 Richard Fitzgerald
2024-02-21  0:51 ` 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=170847669920.72316.9216524053259588241.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=patches@opensource.cirrus.com \
    --cc=rf@opensource.cirrus.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®