All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: alsa-devel@alsa-project.org, Marek Vasut <marex@denx.de>
Cc: Mark Brown <broonie@kernel.org>, ch@denx.de
Subject: Re: [PATCH] ASoC: tlv320aic32x4: Fix TAS2505 volume controls
Date: Mon, 12 Jul 2021 11:46:06 +0100	[thread overview]
Message-ID: <162608623152.3192.16164490887444781260.b4-ty@kernel.org> (raw)
In-Reply-To: <20210708091255.56502-1-marex@denx.de>

On Thu, 8 Jul 2021 11:12:55 +0200, Marek Vasut wrote:
> None of the TAS2505 outputs are stereo, do not pretend they are by
> implementing them using SOC*DOUBLE* macros referencing the same
> register twice, use SOC*SINGLE* instead. Fix volume ranges and mute
> control for the codec according to datasheet.

Applied to

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

Thanks!

[1/1] ASoC: tlv320aic32x4: Fix TAS2505 volume controls
      commit: 2169d6a0f0721935410533281fc7e87e4e2322d1

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:[~2021-07-12 10:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  9:12 [PATCH] ASoC: tlv320aic32x4: Fix TAS2505 volume controls Marek Vasut
2021-07-12 10:46 ` 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=162608623152.3192.16164490887444781260.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=ch@denx.de \
    --cc=marex@denx.de \
    /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.