From: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
To: Chunxu Li <chunxu.li@mediatek.com>,
broonie@kernel.org, pierre-louis.bossart@linux.intel.com,
peter.ujfalusi@linux.intel.com, lgirdwood@gmail.com,
daniel.baluta@nxp.com
Cc: matthias.bgg@gmail.com, yc.hung@mediatek.com,
linux-kernel@vger.kernel.org, alsa-devel@alsa-project.org,
sound-open-firmware@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org,
project_global_chrome_upstream_group@mediatek.com
Subject: Re: [PATCH] ASoC: SOF: Introduce function sof_of_machine_select
Date: Mon, 5 Sep 2022 09:48:50 +0200 [thread overview]
Message-ID: <d1815aba-e11b-9014-e1d1-59425c4358df@collabora.com> (raw)
In-Reply-To: <20220903032151.13664-1-chunxu.li@mediatek.com>
Il 03/09/22 05:21, Chunxu Li ha scritto:
> From current design in sof_machine_check the SOF can only support
> ACPI type machine.
>
> In sof_machine_check if there is no ACPI machine exist, the function
> will return -ENODEV directly, that's we don't expected if we do not
> base on ACPI machine.
>
> So we add a new function named sof_of_machine_select that we can pass
> sof_machine_check and obtain info required by snd_sof_new_platform_drv.
>
> Signed-off-by: Chunxu Li <chunxu.li@mediatek.com>
Reviewed-by: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-09-05 9:41 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-03 3:21 [PATCH] ASoC: SOF: Introduce function sof_of_machine_select Chunxu Li
2022-09-05 7:48 ` AngeloGioacchino Del Regno [this message]
2022-09-05 15:38 ` Mark Brown
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=d1815aba-e11b-9014-e1d1-59425c4358df@collabora.com \
--to=angelogioacchino.delregno@collabora.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=chunxu.li@mediatek.com \
--cc=daniel.baluta@nxp.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=peter.ujfalusi@linux.intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=project_global_chrome_upstream_group@mediatek.com \
--cc=sound-open-firmware@alsa-project.org \
--cc=yc.hung@mediatek.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;
as well as URLs for NNTP newsgroup(s).