[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+Px+wUMXoSL6w0wBduE7obJRWgCteeT8=_=U=8LR34JKTTGZA@mail.gmail.com>
Date: Mon, 17 Aug 2020 16:11:03 +0800
From: Tzung-Bi Shih <tzungbi@...gle.com>
To: Jiaxin Yu <jiaxin.yu@...iatek.com>
Cc: Mark Brown <broonie@...nel.org>,
Matthias Brugger <matthias.bgg@...il.com>,
Rob Herring <robh+dt@...nel.org>,
Takashi Iwai <tiwai@...e.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
ALSA development <alsa-devel@...a-project.org>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, howie.huang@...iatek.com,
eason.yen@...iatek.com, shane.chien@...iatek.com,
bicycle.tsai@...iatek.com
Subject: Re: [PATCH v5 2/2] dt-bindings: mediatek: mt6359: add codec document
On Mon, Aug 17, 2020 at 3:29 PM Tzung-Bi Shih <tzungbi@...gle.com> wrote:
>
> On Mon, Aug 17, 2020 at 2:08 PM Jiaxin Yu <jiaxin.yu@...iatek.com> wrote:
> > +properties:
> > + compatible:
> > + const: mediatek,mt6359-sound
>
> The compatible string has been removed since v3.
>
> > +required:
> > + - compatible
>
> The same here.
>
> > +examples:
> > + - |
> > + mt6359codec: mt6359codec {
> > + compatible = "mediatek,mt6359-sound";
>
> And the same here.
I misunderstood. It still needs the compatible string to match the
corresponding driver.
Powered by blists - more mailing lists