From: YingKun Meng <mengyingkun@loongson.cn>
To: Mark Brown <broonie@kernel.org>
Cc: lgirdwood@gmail.com, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, loongarch@lists.linux.dev,
loongson-kernel@lists.loongnix.cn
Subject: Re: [PATCH 2/3] ASoC: loongson: Add Loongson Generic ASoC Sound Card Support
Date: Fri, 9 Jun 2023 11:57:22 +0800 [thread overview]
Message-ID: <9854871e-2345-d82e-4e4e-d5bf492c2296@loongson.cn> (raw)
In-Reply-To: <aa8381b5-0a3b-4a64-8c92-333ad751956b@sirena.org.uk>
Hi Brown,
Thanks for your kindly work.
On 2023/6/5 20:47, Mark Brown wrote:
> On Mon, Jun 05, 2023 at 08:09:33PM +0800, YingKun Meng wrote:
>
>> The driver supports the use of ACPI table to describe device resources.
>> On loongson 7axxx platforms, the audio device is an ACPI device.
> I'm not seeing any ACPI IDs added here, this is all DT other than this:
I use the special ACPI ID "PRP0001", it provides a means to use the existing
DT-compatible device identification in ACPI.
As described in the document "ACPI Based Device Enumeration".
>> + if (has_acpi_companion(&pdev->dev)) {
>> + device_property_read_string(&pdev->dev, "codec-name",
>> + &codec_name);
>> + for (i = 0; i < card->num_links; i++)
>> + loongson_dai_links[i].codecs->name = codec_name;
>> +
>> + device_property_read_string(&pdev->dev, "codec-dai-name",
>> + &codec_dai_name);
>> + for (i = 0; i < card->num_links; i++)
>> + loongson_dai_links[i].codecs->dai_name = codec_dai_name;
>> + } else {
> which doesn't look *great* from an ACPI point of view TBH. I thought
> there were now some (semi?) standard ACPI bindings these days to support
> referencing other devices better?
Got it! I will rewrite this part.
next parent reply other threads:[~2023-06-09 3:58 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230605120934.2306548-1-mengyingkun@loongson.cn>
[not found] ` <20230605120934.2306548-2-mengyingkun@loongson.cn>
[not found] ` <aa8381b5-0a3b-4a64-8c92-333ad751956b@sirena.org.uk>
2023-06-09 3:57 ` YingKun Meng [this message]
[not found] ` <f88a4985-0dc1-4599-8656-2029c0825495@sirena.org.uk>
2023-06-12 1:44 ` [PATCH 1/3] ASoC: Add support for Loongson I2S controller Yingkun Meng
[not found] ` <20230605120934.2306548-3-mengyingkun@loongson.cn>
[not found] ` <118d13ef-a247-cf88-5084-afdebc6b7651@kernel.org>
2023-06-12 2:30 ` [PATCH 3/3] ASoC: dt-bindings: Add support for Loongson audio card Yingkun Meng
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=9854871e-2345-d82e-4e4e-d5bf492c2296@loongson.cn \
--to=mengyingkun@loongson.cn \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=loongarch@lists.linux.dev \
--cc=loongson-kernel@lists.loongnix.cn \
/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
all inboxes | Powered by JetHome®