[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200819194005.GC38371@sirena.org.uk>
Date: Wed, 19 Aug 2020 20:40:05 +0100
From: Mark Brown <broonie@...nel.org>
To: Tzung-Bi Shih <tzungbi@...gle.com>
Cc: Jiaxin Yu <jiaxin.yu@...iatek.com>,
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 Wed, Aug 19, 2020 at 11:42:27PM +0800, Tzung-Bi Shih wrote:
> But I found struct mfd_cell also contains member .of_compatible. What
> is the difference if we use compatible string (as is) for this device
> instead of falling back to use device name to match?
That's for binding the MFD subdevice to an OF node, you don't need to do
that for a device like this - you can just use the of_node of the parent
to get at the properties.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists