From: Takashi Iwai <tiwai@suse.de>
To: Daniel Dadap <ddadap@nvidia.com>
Cc: alsa-devel@alsa-project.org, linux-sound@vger.kernel.org
Subject: Re: [PATCH v2] ALSA: hda - Add new driver for HDA controllers listed via ACPI
Date: Fri, 16 May 2025 09:56:13 +0200 [thread overview]
Message-ID: <87zffdvvj6.wl-tiwai@suse.de> (raw)
In-Reply-To: <aCYMjYrfFIPjN9Fi@ddadap-lakeline.nvidia.com>
On Thu, 15 May 2025 17:47:25 +0200,
Daniel Dadap wrote:
>
> Some systems expose HD-Audio controllers via objects in the ACPI tables
> which encapsulate the controller's interrupt and the base address for the
> HDA registers in an ACPI _CRS object, for example, as listed in this ACPI
> table dump excerpt:
>
> Device (HDA0)
> {
> Name (_HID, "NVDA2014") // _HID: Hardware ID
> ...
> Name (_CRS, ResourceTemplate () // _CRS: Current Resource Settings
> {
> Memory32Fixed (ReadWrite,
> 0x36078000, // Address Base
> 0x00008000, // Address Length
> )
> Interrupt (ResourceConsumer, Level, ActiveHigh, Exclusive, ,, )
> {
> 0x0000021E,
> }
> })
> }
>
> Add support for HDA controllers discovered through ACPI, including support
> for some platforms which expose such HDA controllers on NVIDIA SoCs. This
> is done with a new driver which uses existing infrastructure for extracting
> resource information from _CRS objects and plumbs the parsed resource
> information through to the existing HDA infrastructure to enable HD-Audio
> functionality on such devices.
>
> Although this driver is in the sound/pci/hda/ directory, it targets devices
> which are not actually enumerated on the PCI bus. This is because it depends
> upon the Intel "Azalia" infrastructure which has traditionally been used for
> PCI-based devices.
>
> Signed-off-by: Daniel Dadap <ddadap@nvidia.com>
Thanks. Now I checked with checkpatch, and it complained a few
things:
WARNING: Block comments use a trailing */ on a separate line
#168: FILE: sound/pci/hda/hda_acpi.c:79:
+ * devm_platform_get_and_ioremap_resource() */
ERROR: code indent should use tabs where possible
#182: FILE: sound/pci/hda/hda_acpi.c:93:
+^I IRQF_SHARED, KBUILD_MODNAME, azx);$
ERROR: code indent should use tabs where possible
#308: FILE: sound/pci/hda/hda_acpi.c:219:
+^I THIS_MODULE, 0, &hda->card);$
WARNING: Prefer "GPL" over "GPL v2" - see commit bf7fbeeae6db ("module: Cure th)
#405: FILE: sound/pci/hda/hda_acpi.c:316:
+MODULE_LICENSE("GPL v2");
Care to address those and resubmit?
thanks,
Takashi
next prev parent reply other threads:[~2025-05-16 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-15 13:31 [PATCH] ALSA: hda - Add new driver for HDA controllers listed via ACPI Daniel Dadap
2025-05-15 14:45 ` Takashi Iwai
2025-05-15 14:54 ` Takashi Iwai
2025-05-15 15:49 ` Daniel Dadap
2025-05-15 15:51 ` Daniel Dadap
2025-05-15 15:45 ` Daniel Dadap
2025-05-15 15:49 ` Takashi Iwai
2025-05-15 15:47 ` [PATCH v2] " Daniel Dadap
2025-05-15 15:50 ` [PATCH v3] " Daniel Dadap
2025-05-16 7:56 ` Takashi Iwai [this message]
2025-05-16 11:37 ` [PATCH v2] " Daniel Dadap
2025-05-21 14:46 ` Daniel Dadap
2025-05-16 11:43 ` [PATCH v4] " Daniel Dadap
2025-05-21 14:35 ` [PATCH v5] " Daniel Dadap
2025-05-21 20:17 ` Takashi Iwai
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=87zffdvvj6.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=ddadap@nvidia.com \
--cc=linux-sound@vger.kernel.org \
/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