From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id F2B88C02198 for ; Mon, 10 Feb 2025 18:09:48 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:Content-Transfer-Encoding: Content-Type:MIME-Version:Date:Message-Id:Subject:References:In-Reply-To:Cc: To:From:Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=i/jznGQI/pX4CDtnxW3B8Ci9Q9wIgro597CcZ6L6VaA=; b=eSf05NrgAj15Svu2FTxvzX1LIr W1cWV9GWz4mBhnDUzx36V+s4wzfSFjOebJSKCYCCv73a+Ir5X13R8Dq70mCJviwrvOnGuIvH0ArfM gmjjekZePUSeviEqzQ+cu8RkPBbpGPwifgARVG5TbJCAUTNgVwudMpyB8b4iUYusy9mNuRcgfUtnI 5o+BsJlajRQ+krcDViyCbOGGhYyJ4VDGz5Ar/32XeO/2hcNxwXxqApyfchWBo/QYQTbhGA9/ubh5u tWALF92eZP6C+Ustb+NGoBilFEO2in1dZG76MX6/0lnVkF/ejnY3legKT/j0Vh+T0IgVRIKTadbN3 CVmrnFHA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.98 #2 (Red Hat Linux)) id 1thYDw-00000000rNM-0oOm; Mon, 10 Feb 2025 18:09:36 +0000 Received: from nyc.source.kernel.org ([147.75.193.91]) by bombadil.infradead.org with esmtps (Exim 4.98 #2 (Red Hat Linux)) id 1thYBM-00000000qwy-1UzG; Mon, 10 Feb 2025 18:06:57 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by nyc.source.kernel.org (Postfix) with ESMTP id 0C672A41DE4; Mon, 10 Feb 2025 18:05:10 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 318ECC4CEE8; Mon, 10 Feb 2025 18:06:53 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1739210815; bh=9exn/4ZsF5vuvnX6J4sI+LMbw0QAxfbaUGw2qKxET7s=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=bMzbYXU7pAqM8vaN+LfTd+RHouNCUWylspD71+355yoGwmaqVxbZL12NJ5ABmgfny OjA5s/GjFxGA2nmlceA4IoJBJANqaHtJkqZGpzT9JumSEi5699kTFaOQM/bHzKd7fG 0lNRB1TTWq4JqCJZoxtwQUUIF1+CqUln35kgfB8cVaOHyPfcbugv+0zfCJ0tEZqNoM 8IHIhgwex9NPAyOyINexrKA+vVE63tPIgVS+ihcUB9tv1dMPnnZYtyac/SVZUhVFnh lHTZA6D7saT8qrqcKn/7fBQUsj71e9i4HFlwQZdMtySeYXTLZZqFbD7ugEq1pw5+MB c6+tMrgm5ydcQ== From: Mark Brown To: Liam Girdwood , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Heiko Stuebner , Alexey Charkov Cc: linux-sound@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <20250120-rk3588-spdif-v1-0-1415f5871dc7@gmail.com> References: <20250120-rk3588-spdif-v1-0-1415f5871dc7@gmail.com> Subject: Re: (subset) [PATCH 0/3] arm64: dts: rockchip: Add SPDIF on RK3588 Message-Id: <173921081291.95415.12801821205911755480.b4-ty@kernel.org> Date: Mon, 10 Feb 2025 18:06:52 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.15-dev-1b0d6 X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20250210_100656_469569_6985DB11 X-CRM114-Status: GOOD ( 15.61 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, 20 Jan 2025 13:01:26 +0400, Alexey Charkov wrote: > RK3588(s) uses a several SPDIF transmitters which are software > compatible with those found in RK3568. This series adds the required > device tree nodes in SoC .dtsi and enables the dedicated optical > SPDIF output on the H96 Max V58. > > Note that only SPDIF 0/1 are meant as externally connected outputs, > while SPDIF 2/3/4/5 are internally routed to the various display > encoders inside the SoC. Thus, using SPDIF 0/1 only requires their > device tree nodes to be enabled (provided that the signal is routed > somewhere usable on the board itself), while the rest rely on driver > support on the display connector side and are therefore not touched > here. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/sound.git for-next Thanks! [1/3] dt-bindings: ASoC: rockchip: Add compatible for RK3588 SPDIF commit: 330cbb40bb3664a18a19760bd6dc6003d6624041 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