[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20190516165407.GJ5598@sirena.org.uk>
Date: Thu, 16 May 2019 17:54:07 +0100
From: Mark Brown <broonie@...nel.org>
To: Fabio Estevam <festevam@...il.com>
Cc: Viorel Suman <viorel.suman@....com>,
Liam Girdwood <lgirdwood@...il.com>,
Jaroslav Kysela <perex@...ex.cz>,
Takashi Iwai <tiwai@...e.com>,
"S.j. Wang" <shengjiu.wang@....com>,
Daniel Baluta <daniel.baluta@....com>,
Julia Lawall <Julia.Lawall@...6.fr>,
Colin Ian King <colin.king@...onical.com>,
"alsa-devel@...a-project.org" <alsa-devel@...a-project.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Viorel Suman <viorel.suman@...il.com>,
dl-linux-imx <linux-imx@....com>
Subject: Re: [alsa-devel] [PATCH] ASoC: AK4458: add regulator for ak4458
On Thu, May 16, 2019 at 10:14:42AM -0300, Fabio Estevam wrote:
> > + ret = devm_regulator_bulk_get(ak4458->dev, ARRAY_SIZE(ak4458->supplies),
> > + ak4458->supplies);
> > + if (ret != 0) {
> > + dev_err(ak4458->dev, "Failed to request supplies: %d\n", ret);
> > + return ret;
> This would break existing users that do not pass the regulators in device tree.
It won't, if you're using regulator_get() and there's just no regulator
in the DT the regulator framework just assumes that there is actually a
regulator there which isn't described in the DT and substitutes in a
dummy regulator for you.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists