mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: Kevin Cernekee <cernekee@chromium.org>,
	 Liam Girdwood <lgirdwood@gmail.com>,
	Jaroslav Kysela <perex@perex.cz>,  Takashi Iwai <tiwai@suse.com>,
	 Bram Vlerick <bram.vlerick@openpixelsystems.org>
Cc: linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org,
	 peter@korsgaard.com
Subject: Re: [PATCH] ASoC: tas571x: add separate tas5733 controls
Date: Tue, 27 May 2025 17:32:45 +0100	[thread overview]
Message-ID: <174836356579.104699.8312897041646074055.b4-ty@kernel.org> (raw)
In-Reply-To: <20250527-tas5733-biquad-fix-v1-1-0d3d941700bb@openpixelsystems.org>

On Tue, 27 May 2025 13:08:49 +0200, Bram Vlerick wrote:
> The controls between the tas5717 and tas5733 should not be shared since
> the biquad and register setup is not identical. For example, writing to
> 0x5c on the tas5717 modifies ch2_bq[10] while on the tas5733 this is
> ch1_cross_bq[3].
> 
> see https://www.ti.com/lit/ds/symlink/tas5733l.pdf and
> https://www.ti.com/lit/ds/symlink/tas5717.pdf for more details on the
> register maps.
> 
> [...]

Applied to

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

Thanks!

[1/1] ASoC: tas571x: add separate tas5733 controls
      commit: e3de7984e45155888eebbca5a32c1cc5f29fa859

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:[~2025-05-27 16:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-27 11:08 Bram Vlerick
2025-05-27 11:46 ` Bram Vlerick
2025-05-27 16:32 ` 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=174836356579.104699.8312897041646074055.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=bram.vlerick@openpixelsystems.org \
    --cc=cernekee@chromium.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=peter@korsgaard.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

all inboxes | Powered by JetHome®