From: "Mukunda,Vijendar" <vijendar.mukunda@amd.com>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org, Alexander.Deucher@amd.com,
Sunil-kumar.Dommati@amd.com, David.Rhodes@cirrus.com,
wtli@nuvoton.com, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] ASoc: amd: create platform device for VG machine driver
Date: Mon, 11 Oct 2021 11:48:40 +0530 [thread overview]
Message-ID: <57f313fe-fb8e-8b4b-8839-d9d8653880d1@amd.com> (raw)
In-Reply-To: <YWR5QH1lYqiT1cX+@sirena.org.uk>
On 10/11/21 11:19 PM, Mark Brown wrote:
> On Tue, Oct 12, 2021 at 12:17:01AM +0530, Vijendar Mukunda wrote:
>
>> pdevinfo[2].res = &adata->res[2];
>>
>> + pdevinfo[3].name = "acp5x_nu8821_cs35l41_mach";
>> + pdevinfo[3].id = 0;
>> + pdevinfo[3].parent = &pci->dev;
>
> This appears to unconditionally assume that any machine with this
> hardware is going to have exactly the same CODEC/amp combination - that
> seems like it's going to go badly at some point. Shouldn't there be
> some other check that we're instantiating the right machine driver?
>
we will make the platform device as generic one something like "acp5x_mach".
Currently we have only one target platform with above codec combinations
for this APU series.
When we get new codecs combinations to support, we will address it in
machine driver by adding DMI checks for distinguishing codec combinations.
> BTW your clock appears to be set quite a way into the future (possibly
> about 24 hours?) which is confusing things.
>
Will fix the system time settings.
next prev parent reply other threads:[~2021-10-11 18:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-11 18:47 Vijendar Mukunda
2021-10-11 17:49 ` Mark Brown
2021-10-11 6:18 ` Mukunda,Vijendar [this message]
2021-10-11 18:29 ` Mark Brown
2021-10-11 6:43 ` Mukunda,Vijendar
2021-10-11 18:47 ` [PATCH 2/3] ASoC: amd: add vangogh " Vijendar Mukunda
2021-10-11 18:47 ` [PATCH 3/3] ASoC: amd: enable Vangogh platform machine driver build Vijendar Mukunda
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=57f313fe-fb8e-8b4b-8839-d9d8653880d1@amd.com \
--to=vijendar.mukunda@amd.com \
--cc=Alexander.Deucher@amd.com \
--cc=David.Rhodes@cirrus.com \
--cc=Sunil-kumar.Dommati@amd.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=perex@perex.cz \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.com \
--cc=wtli@nuvoton.com \
/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®