[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20201201151645.GI5239@sirena.org.uk>
Date: Tue, 1 Dec 2020 15:16:45 +0000
From: Mark Brown <broonie@...nel.org>
To: Shane Chien <shane.chien@...iatek.com>
Cc: Matthias Brugger <matthias.bgg@...il.com>,
linux-kernel@...r.kernel.org, linux-mediatek@...ts.infradead.org,
devicetree@...r.kernel.org, wsd_upstream@...iatek.com,
alsa-devel@...a-project.org, jiaxin.yu@...iatek.com,
chipeng.chang@...iatek.com, jeter.chen@...iatek.com,
tzungbi@...gle.com, fan.chen@...iatek.com,
Hsin-Hsiung.Wang@...iatek.com
Subject: Re: [RFC] ASoC: Add compatible for mt6359-sound device
On Tue, Dec 01, 2020 at 01:41:33PM +0800, Shane Chien wrote:
> However, if the device is not given a comaptible,
> of_node of struct device is null. I cannot use
> devm_iio_channel_get such iio interface to get
> auxadc value from iio channel. Because during
> using devm_iio_channel_get, of_node of mt6359-sound is a
> input parameter of of_iio_channel_get_by_name.
> If the of_node is null, devm_iio_channel_get will
> eventually return ENODEV error.
I would expect the IIO channel to be requestable using the top level
device for the MFD - part of the deal here is that the function drivers
for the MFD know they're part of the MFD so can look at their parent
device for some things (eg, this is how regmaps are normally obtained).
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists