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 alsa0.perex.cz (alsa0.perex.cz [77.48.224.243]) (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 D10A0CEFCE2 for ; Tue, 6 Jan 2026 18:23:56 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [45.14.194.44]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id 91037601F9; Tue, 6 Jan 2026 19:23:41 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz 91037601F9 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1767723831; bh=fCx3/W5B6Rfg8l80grpONf9L2fW8Rd8ZlazuzbUtFko=; h=From:To:In-Reply-To:References:Subject:Date:List-Id:List-Archive: List-Help:List-Owner:List-Post:List-Subscribe:List-Unsubscribe: From; b=S++8qz5krVnvI3UWoMqRRbCgD5jUpGk4pfyyncfjtauhoBJP7SEpT8X64OjOyl8ve eXS2g1F1mcB3YX8MHr0nqXNjJ8/fc1INu8Lm/bC6BxLF3HyQ029LTnNMSaJRc1c2P0 XF+GvPAUV8/waWoKSqUZrTHYAgrz0RyyaZt9D21g= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 63497F805E2; Tue, 6 Jan 2026 19:23:17 +0100 (CET) Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id CF7FAF805E4; Tue, 6 Jan 2026 19:23:16 +0100 (CET) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 34CBDF804F3; Tue, 6 Jan 2026 19:23:04 +0100 (CET) Received: from webhooks-bot.alsa-project.org (vmi2259423.contaboserver.net [45.14.194.44]) by alsa1.perex.cz (Postfix) with ESMTP id 395F1F80088 for ; Tue, 6 Jan 2026 19:22:57 +0100 (CET) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 395F1F80088 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit From: GitHub pull_request - opened To: alsa-devel@alsa-project.org Message-Id: <18883768f532d700-webhooks-bot@alsa-project.org> In-Reply-To: References: Subject: USB-Audio: Add support for the SSL 2 MK II Date: Tue, 6 Jan 2026 19:23:04 +0100 (CET) Message-ID-Hash: LTB5SBR2NWUMEUOC46IZOM2PCQZYGA6D X-Message-ID-Hash: LTB5SBR2NWUMEUOC46IZOM2PCQZYGA6D X-MailFrom: github@alsa-project.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; header-match-alsa-devel.alsa-project.org-0; header-match-alsa-devel.alsa-project.org-1; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.9 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: alsa-project/alsa-ucm-conf pull request #681 was opened from MTRNord: This adds support for https://solidstatelogic.com/products/ssl-2-mkii and the https://solidstatelogic.com/products/ssl-2-plus-mkii and solves #555 The MK II shows up the same way as the SSL2, but as a different USB Device. I only own the SSL2 MK2, but not the SSL2+ MK2. So I can only verify it for the SSL2 MK2. However, I am fairly certain that the + version likely is also behaving identically. There are no visible spec changes between the v1 and MK2 of these devices, from all I was able to tell based on the internet. So, likely only the USB ID changed (at least for the things alsa-ucm is concerened about) Request URL : https://github.com/alsa-project/alsa-ucm-conf/pull/681 Patch URL : https://github.com/alsa-project/alsa-ucm-conf/pull/681.patch Repository URL: https://github.com/alsa-project/alsa-ucm-conf