mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mark Brown <broonie@kernel.org>
To: konradybcio@kernel.org, andersson@kernel.org,
	 srinivas.kandagatla@linaro.org,
	Alexey Klimov <alexey.klimov@linaro.org>
Cc: tiwai@suse.com, lgirdwood@gmail.com, perex@perex.cz,
	robh@kernel.org,  krzk+dt@kernel.org, conor+dt@kernel.org,
	dmitry.baryshkov@linaro.org,  linux-sound@vger.kernel.org,
	linux-arm-msm@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: (subset) [PATCH v1 0/3] db845c/rb3: add i2s playback support
Date: Tue, 17 Dec 2024 13:27:24 +0000	[thread overview]
Message-ID: <173444204405.31585.10764828283359007380.b4-ty@kernel.org> (raw)
In-Reply-To: <20241205023344.2232529-1-alexey.klimov@linaro.org>

On Thu, 05 Dec 2024 02:33:41 +0000, Alexey Klimov wrote:
> There are i2s signals provided in low-speed connector on such boards
> as required by 96boards spec. Looks like it is possible to actually
> playback something via these pins after adding missing parts here
> and there.
> 
> I tested simple widely available cheap DACs like UDA1334 and PCM5102A
> and they works just fine without need for mclk. I guess any DAC that
> can handle 48 kHz and 16bit will do.
> 
> [...]

Applied to

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

Thanks!

[2/3] ASoC: qcom: sdm845: add handling of secondary MI2S clock
      commit: 8bfb66c75cdace542dabe87841152614fd5b8d91

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:[~2024-12-17 13:27 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-05  2:33 Alexey Klimov
2024-12-05  2:33 ` [PATCH v1 1/3] ASoC: qcom: common: set codecless link to be a backend Alexey Klimov
2024-12-16 21:48   ` Mark Brown
2024-12-05  2:33 ` [PATCH v1 2/3] ASoC: qcom: sdm845: add handling of secondary MI2S clock Alexey Klimov
2024-12-05  2:33 ` [PATCH v1 3/3] arm64: dts: qcom: sdm845-db845c: add i2s playback support via LS1 connector Alexey Klimov
2024-12-13 13:07   ` Konrad Dybcio
2024-12-05 12:08 ` [PATCH v1 0/3] db845c/rb3: add i2s playback support Mark Brown
2024-12-17 13:27 ` 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=173444204405.31585.10764828283359007380.b4-ty@kernel.org \
    --to=broonie@kernel.org \
    --cc=alexey.klimov@linaro.org \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=srinivas.kandagatla@linaro.org \
    --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®