All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Tzung-Bi Shih <tzungbi@google.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: [PATCH v3 0/2] ASoC: rt1015p: delay 300ms for waiting calibration
Date: Fri, 11 Dec 2020 17:49:41 +0000	[thread overview]
Message-ID: <160770898112.26354.6573689046730156511.b4-ty@kernel.org> (raw)
In-Reply-To: <20201211051224.2307349-1-tzungbi@google.com>

On Fri, 11 Dec 2020 13:12:22 +0800, Tzung-Bi Shih wrote:
> The 1st patch moves SDB control from DAI ops trigger to DAPM event
> (per review comments in v1).
> 
> The 2nd patch adds the 300ms delay for waiting calibration.
> 
> Changes from v2:
> - Use gpiod_set_value_cansleep() instead of gpiod_set_value().
> (https://patchwork.kernel.org/project/alsa-devel/patch/20201210033617.79300-2-tzungbi@google.com/)
> - Assuming the calibration state gets lost after system suspend.
> (https://patchwork.kernel.org/project/alsa-devel/patch/20201210033617.79300-3-tzungbi@google.com/)
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: rt1015p: move SDB control from trigger to DAPM
      commit: 4ab9301710760b99b4229d608eb5599040b2e07e
[2/2] ASoC: rt1015p: delay 300ms after SDB pulling high for calibration
      commit: f102d0d173982be3fc096d0293c1c0245e988ba6

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

      parent reply	other threads:[~2020-12-11 17:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-11  5:12 [PATCH v3 0/2] ASoC: rt1015p: delay 300ms for waiting calibration Tzung-Bi Shih
2020-12-11  5:12 ` [PATCH v3 1/2] ASoC: rt1015p: move SDB control from trigger to DAPM Tzung-Bi Shih
2020-12-11  5:12 ` [PATCH v3 2/2] ASoC: rt1015p: delay 300ms after SDB pulling high for calibration Tzung-Bi Shih
2020-12-11 17:49 ` 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=160770898112.26354.6573689046730156511.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=tzungbi@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.