[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Yjf4KjXpVJaNnvb8@google.com>
Date: Mon, 21 Mar 2022 11:59:38 +0800
From: Tzung-Bi Shih <tzungbi@...nel.org>
To: Jiaxin Yu <jiaxin.yu@...iatek.com>
Cc: broonie@...nel.org, robh+dt@...nel.org, devicetree@...r.kernel.org,
linmq006@...il.com, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org,
Project_Global_Chrome_Upstream_Group@...iatek.com,
linux-mediatek@...ts.infradead.org, trevor.wu@...iatek.com,
matthias.bgg@...il.com, aaronyu@...gle.com,
linux-arm-kernel@...ts.infradead.org,
angelogioacchino.delregno@...labora.com
Subject: Re: [v5 3/4] ASoC: mediatek: mt8192: refactor for I2S8/I2S9 DAI
links of headset
On Sat, Mar 19, 2022 at 07:41:10PM +0800, Jiaxin Yu wrote:
> @@ -1145,6 +1140,13 @@ static int mt8192_mt6359_dev_probe(struct platform_device *pdev)
> goto err_speaker_codec;
> }
>
> + headset_codec = of_get_child_by_name(pdev->dev.of_node, "mediatek,headset-codec");
> + if (!headset_codec) {
> + ret = -EINVAL;
> + dev_err_probe(&pdev->dev, ret, "Property 'headset_codec' missing or invalid\n");
> + goto err_headset_codec;
> + }
(to be neat) Does it have any reason to prevent from using of_parse_phandle()
but of_get_child_by_name()?
Powered by blists - more mailing lists