public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: shengjiu.wang@gmail.com, Xiubo.Lee@gmail.com, festevam@gmail.com,
	 nicoleotsuka@gmail.com, lgirdwood@gmail.com, perex@perex.cz,
	tiwai@suse.com,  linux-sound@vger.kernel.org,
	linuxppc-dev@lists.ozlabs.org,  linux-kernel@vger.kernel.org,
	Shengjiu Wang <shengjiu.wang@nxp.com>
Subject: Re: [PATCH v2 0/2] ASoC: fsl: add bitcount and timestamp controls
Date: Thu, 12 Mar 2026 17:34:37 +0000	[thread overview]
Message-ID: <177333687761.302961.14700206340087655757.b4-ty@kernel.org> (raw)
In-Reply-To: <20260212072229.3247604-1-shengjiu.wang@nxp.com>

On Thu, 12 Feb 2026 15:22:27 +0800, Shengjiu Wang wrote:
> The SAI and XCVR have the timestamp counters and bit counters, which can
> be used by software to track the progress of the transmitter and receiver.
> They can also be used to calculate the relative frequency of the bit clock
> against the bus interface clock.
> 
> Changes in v2:
> - remove arrays of enums, define transmit_tstmp_enum and receive_tstmp_enum
>   separately.
> - remove __bf_shf(), define the XXX_SHIFT macros.
> 
> [...]

Applied to

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

Thanks!

[1/2] ASoC: fsl_sai: add bitcount and timestamp controls
      commit: 8e27987a208029c39da7a787bd9f1217d42011a5
[2/2] ASoC: fsl_xcvr: add bitcount and timestamp controls
      commit: 7b3f8db159f710d432c4edc024fcefa9e62e8b4b

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:[~2026-03-12 17:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-12  7:22 [PATCH v2 0/2] ASoC: fsl: add bitcount and timestamp controls Shengjiu Wang
2026-02-12  7:22 ` [PATCH v2 1/2] ASoC: fsl_sai: " Shengjiu Wang
2026-03-03  0:24   ` Mark Brown
2026-03-04  6:56     ` Shengjiu Wang
2026-02-12  7:22 ` [PATCH v2 2/2] ASoC: fsl_xcvr: " Shengjiu Wang
2026-03-12 17:34 ` 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=177333687761.302961.14700206340087655757.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=Xiubo.Lee@gmail.com \
    --cc=festevam@gmail.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=nicoleotsuka@gmail.com \
    --cc=perex@perex.cz \
    --cc=shengjiu.wang@gmail.com \
    --cc=shengjiu.wang@nxp.com \
    --cc=tiwai@suse.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