[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20151116105035.GA31303@sirena.org.uk>
Date: Mon, 16 Nov 2015 10:50:35 +0000
From: Mark Brown <broonie@...nel.org>
To: Pavel Machek <pavel@....cz>
Cc: sameo@...ux.intel.com, lee.jones@...aro.org,
Charles Keepax <ckeepax@...nsource.wolfsonmicro.com>,
lgirdwood@...il.com, perex@...ex.cz, tiwai@...e.de,
patches@...nsource.wolfsonmicro.com, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org
Subject: Re: multi-codec support for arizona-ldo1 was Re: System with
multiple arizona (wm5102) codecs
On Mon, Nov 16, 2015 at 08:45:34AM +0100, Pavel Machek wrote:
> > > Ok, so SND_SOC_DAPM_REGULATOR_SUPPLY() does not work, because I have
> > > two regulators, right? Is there similar macro I can use?
> > No? What would make you say that?
> Plus, I'd expect to see some kind of "struct device" argument to
> SND_SOC_DAPM_REGULATOR_SUPPLY(). I'm selecting supply name, but I'm
> not selecting on which device...
I've already pointed you at the implementation at least once and
hopefully the regulator API interfaces are quite clear here too that
it's not possible to request a regulator without providing a device.
> > Every single sound driver gets this right, none of them assume the name
> > is global. What makes you say that they assume names are global?
> Ok, so you are saying that if I fix mfd initialization, sound will
> automagically switch from global regulators to device-specific
> regulators and things will start working?
Yes.
Download attachment "signature.asc" of type "application/pgp-signature" (474 bytes)
Powered by blists - more mailing lists