Message ID | 20240529155653.3037-1-baojun.xu@ti.com (mailing list archive) |
---|---|
Headers | show
Return-Path: <alsa-devel-bounces@alsa-project.org> 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 8A4D3C27C4F for <alsa-devel@archiver.kernel.org>; Thu, 13 Jun 2024 16:01:09 +0000 (UTC) Received: from alsa1.perex.cz (alsa1.perex.cz [207.180.221.201]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa0.perex.cz (Postfix) with ESMTPS id B0466E66; Thu, 13 Jun 2024 18:00:57 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa0.perex.cz B0466E66 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alsa-project.org; s=default; t=1718294467; bh=F6cyAmkItPJMHlzbT5ed2RaRwc0dmuF+iURbDkk2joo=; h=From:To:CC:Subject:Date:List-Id:List-Archive:List-Help:List-Owner: List-Post:List-Subscribe:List-Unsubscribe:From; b=KNgPLrEFSGgrd4oNxxmQjF6WvjpkBIzDVcSt3FqwfsTV9Hv1GGGsPrcJn+HsQ5wPO XeAPvCz5UVSpj59fIQ/2PZ39o+D830Gok1pY48ut0RrsxR3USyjWtFTC4/is69dMS4 rYwZzGexlQi8yMELuAhzG84UqBRg9z1lSZIt2Deo= Received: by alsa1.perex.cz (Postfix, from userid 50401) id 8D84BF805B2; Thu, 13 Jun 2024 18:00:34 +0200 (CEST) Received: from mailman-core.alsa-project.org (mailman-core.alsa-project.org [10.254.200.10]) by alsa1.perex.cz (Postfix) with ESMTP id E42B4F805B3; Thu, 13 Jun 2024 18:00:33 +0200 (CEST) Received: by alsa1.perex.cz (Postfix, from userid 50401) id 97295F80149; Wed, 29 May 2024 17:57:41 +0200 (CEST) Received: from lelv0142.ext.ti.com (lelv0142.ext.ti.com [198.47.23.249]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by alsa1.perex.cz (Postfix) with ESMTPS id 2A56FF800BA for <alsa-devel@alsa-project.org>; Wed, 29 May 2024 17:57:31 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 alsa1.perex.cz 2A56FF800BA Authentication-Results: alsa1.perex.cz; dkim=pass (1024-bit key, unprotected) header.d=ti.com header.i=@ti.com header.a=rsa-sha256 header.s=ti-com-17Q1 header.b=Bfx7xSsO Received: from lelv0265.itg.ti.com ([10.180.67.224]) by lelv0142.ext.ti.com (8.15.2/8.15.2) with ESMTP id 44TFvQiL092772; Wed, 29 May 2024 10:57:26 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1716998246; bh=VtlZBCIrXk7KWkQBoJWGM8oCenwDZWgPBkeKsS0cLy0=; h=From:To:CC:Subject:Date; b=Bfx7xSsOlRFaxh858qh8x9RRHbVRqngv2ZLfpVerQI7m2JI6dpJ+dAvj3Z6j/nUbD gjpwBmcEM1MAz9ZGa4wS1hmbvDWr0dct7PFdIPnuIGiNvBavS3kEcA2WCy1DpVYfUi f99qS9Lu9mMDQr/j8vMAZQYKLM2gy0tT+8IaARNc= Received: from DFLE112.ent.ti.com (dfle112.ent.ti.com [10.64.6.33]) by lelv0265.itg.ti.com (8.15.2/8.15.2) with ESMTPS id 44TFvQVi032095 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=FAIL); Wed, 29 May 2024 10:57:26 -0500 Received: from DFLE105.ent.ti.com (10.64.6.26) by DFLE112.ent.ti.com (10.64.6.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23; Wed, 29 May 2024 10:57:26 -0500 Received: from lelvsmtp5.itg.ti.com (10.180.75.250) by DFLE105.ent.ti.com (10.64.6.26) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2507.23 via Frontend Transport; Wed, 29 May 2024 10:57:26 -0500 Received: from lelvsmtp5.itg.ti.com ([10.250.165.138]) by lelvsmtp5.itg.ti.com (8.15.2/8.15.2) with ESMTP id 44TFvHYp029748; Wed, 29 May 2024 10:57:18 -0500 From: Baojun Xu <baojun.xu@ti.com> To: <tiwai@suse.de> CC: <robh+dt@kernel.org>, <andriy.shevchenko@linux.intel.com>, <lgirdwood@gmail.com>, <perex@perex.cz>, <pierre-louis.bossart@linux.intel.com>, <kevin-lu@ti.com>, <shenghao-ding@ti.com>, <navada@ti.com>, <13916275206@139.com>, <v-hampiholi@ti.com>, <v-po@ti.com>, <niranjan.hy@ti.com>, <alsa-devel@alsa-project.org>, <linux-kernel@vger.kernel.org>, <liam.r.girdwood@intel.com>, <yung-chuan.liao@linux.intel.com>, <baojun.xu@ti.com>, <broonie@kernel.org>, <soyer@irl.hu> Subject: [PATCH v6 0/1] Add tas2781 driver for SPI. Date: Wed, 29 May 2024 23:56:52 +0800 Message-ID: <20240529155653.3037-1-baojun.xu@ti.com> X-Mailer: git-send-email 2.43.0.windows.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 X-MailFrom: baojun.xu@ti.com X-Mailman-Rule-Hits: nonmember-moderation 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 Message-ID-Hash: NI7E3373MK4NXGGF4LTCLAUY52NVWGVU X-Message-ID-Hash: NI7E3373MK4NXGGF4LTCLAUY52NVWGVU X-Mailman-Approved-At: Thu, 13 Jun 2024 16:00:30 +0000 X-Mailman-Version: 3.3.9 Precedence: list List-Id: "Alsa-devel mailing list for ALSA developers - http://www.alsa-project.org" <alsa-devel.alsa-project.org> Archived-At: <https://mailman.alsa-project.org/hyperkitty/list/alsa-devel@alsa-project.org/message/NI7E3373MK4NXGGF4LTCLAUY52NVWGVU/> List-Archive: <https://mailman.alsa-project.org/hyperkitty/list/alsa-devel@alsa-project.org/> List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help> List-Owner: <mailto:alsa-devel-owner@alsa-project.org> List-Post: <mailto:alsa-devel@alsa-project.org> List-Subscribe: <mailto:alsa-devel-join@alsa-project.org> List-Unsubscribe: <mailto:alsa-devel-leave@alsa-project.org> |
Series |
Add tas2781 driver for SPI.
|
expand
|
Hi Pierre, Do you know any different between windows and Ubuntu on SPI inialyze? We are testing my patch on Laptop (HP-Varcolac, SSID:103C8B92, fly-out SPI & I2S cables), no any issue with wondows, but with Linux, second speaker has no sound, it's initialyze is totally same with first AMP, and relative registers can be dumped, no problem found. Best Regards Jim
This patch was used to add TAS2781 devices on SPI support in sound/pci/hda. It use ACPI node descript about parameters of TAS2781 on SPI, it like: Scope (_SB.PC00.SPI0) { Device (GSPK) { Name (_HID, "TXNW2781") // _HID: Hardware ID Method (_CRS, 0, NotSerialized) { Name (RBUF, ResourceTemplate () { SpiSerialBusV2 (...) SpiSerialBusV2 (...) } } } } And in platform/x86/serial-multi-instantiate.c, those spi devices will be added into system as a single SPI device, so TAS2781 SPI driver will probe twice for every single SPI device. And driver will also parser mono DSP firmware binary and RCA binary for itself. Signed-off-by: Baojun Xu <baojun.xu@ti.com> Baojun Xu (1): ALSA: hda/tas2781: Add tas2781 hda driver based on SPI drivers/acpi/scan.c | 1 + .../platform/x86/serial-multi-instantiate.c | 12 + sound/pci/hda/Kconfig | 14 + sound/pci/hda/Makefile | 2 + sound/pci/hda/patch_realtek.c | 13 + sound/pci/hda/tas2781-spi.h | 148 ++ sound/pci/hda/tas2781_hda_spi.c | 1266 ++++++++++ sound/pci/hda/tas2781_spi_fwlib.c | 2101 +++++++++++++++++ 8 files changed, 3557 insertions(+) create mode 100644 sound/pci/hda/tas2781-spi.h create mode 100644 sound/pci/hda/tas2781_hda_spi.c create mode 100644 sound/pci/hda/tas2781_spi_fwlib.c