Message ID | 20210430035859.3487-1-samuel@sholland.org (mailing list archive) |
---|---|
Headers | show |
Series | PinePhone BT audio bringup | expand |
On Thu, Apr 29, 2021 at 10:58:52PM -0500, Samuel Holland wrote: > This series uses the additional DAIs added to the sun8i-codec driver to > add hardware routing for BT SCO (headset) audio on the PinePhone. > > The BT audio connection is represented by the "dummy" bt-sco codec. The > connection to the Quectel EG-25G modem via AIF2 works as well, but I do > not include it here because there is no appropriate codec driver in > tree. We have been using an out-of-tree "dummy" codec driver for the > modem similar to bt-sco, and I'm not sure if such a driver would be > desired upstream. I've applied patches 1-6 Maxime
On Thu, 29 Apr 2021 22:58:52 -0500, Samuel Holland wrote: > This series uses the additional DAIs added to the sun8i-codec driver to > add hardware routing for BT SCO (headset) audio on the PinePhone. > > The BT audio connection is represented by the "dummy" bt-sco codec. The > connection to the Quectel EG-25G modem via AIF2 works as well, but I do > not include it here because there is no appropriate codec driver in > tree. We have been using an out-of-tree "dummy" codec driver for the > modem similar to bt-sco, and I'm not sure if such a driver would be > desired upstream. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/7] ASoC: dt-bindings: sun8i-codec: Increase #sound-dai-cells commit: 880e007f15a31f446b9e1713720c6ae5a539f3f4 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