[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <61e9fb59448837cfc8e3ec862b711294bcb68872.camel@mediatek.com>
Date: Wed, 30 Mar 2022 22:06:24 +0800
From: Jiaxin Yu <jiaxin.yu@...iatek.com>
To: Mark Brown <broonie@...nel.org>
CC: "NĂcolas F. R. A. Prado" <nfraprado@...labora.com>,
<robh+dt@...nel.org>, <tzungbi@...gle.com>,
<angelogioacchino.delregno@...labora.com>, <aaronyu@...gle.com>,
<matthias.bgg@...il.com>, <trevor.wu@...iatek.com>,
<linmq006@...il.com>, <alsa-devel@...a-project.org>,
<devicetree@...r.kernel.org>,
<linux-arm-kernel@...ts.infradead.org>,
<linux-mediatek@...ts.infradead.org>,
<linux-kernel@...r.kernel.org>,
<Project_Global_Chrome_Upstream_Group@...iatek.com>,
Tzung-Bi Shih <tzungbi@...nel.org>
Subject: Re: [v7 2/4] ASoC: mediatek: mt8192: refactor for I2S3 DAI link of
speaker
On Wed, 2022-03-30 at 13:30 +0100, Mark Brown wrote:
> On Wed, Mar 30, 2022 at 10:33:06AM +0800, Jiaxin Yu wrote:
>
> > "(Although I think this would technicallybreak the ABI?)"
> > ==> I can't understand this question, could you help explain it in
> > more
> > detail.
>
> Making a previously optional property required means that systems
> that
> previously worked may stop working unless they update their DT, DTs
> may
> be distributed separately to the kernel and perhaps even baked into
> firmware or similar.
Hi Mark,
Thank you for your detailed answer. I should keep the driver's behavior
consistent with the description of dt-bindings. The "mediatek,hdmi-
codec" needs to be set as the required property. Is my understanding
right?
Thanks,
Jiaxin.Yu
Powered by blists - more mailing lists