[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y1ks6n7wCfhArza/@sirena.org.uk>
Date: Wed, 26 Oct 2022 13:49:46 +0100
From: Mark Brown <broonie@...nel.org>
To: Chen-Yu Tsai <wenst@...omium.org>
Cc: NĂcolas F. R. A. Prado
<nfraprado@...labora.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Rob Herring <robh+dt@...nel.org>, devicetree@...r.kernel.org,
alsa-devel@...a-project.org, Liam Girdwood <lgirdwood@...il.com>,
linux-kernel@...r.kernel.org, Derek Fang <derek.fang@...ltek.com>,
kernel@...labora.com,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
Subject: Re: [PATCH v2 2/4] ASoC: dt-bindings: realtek, rt5682s: Add AVDD and
MICVDD supplies
On Tue, Oct 25, 2022 at 01:12:49PM -0700, Chen-Yu Tsai wrote:
> On Mon, Oct 24, 2022 at 3:01 PM NĂcolas F. R. A. Prado
> > The rt5682s codec can have two supplies: AVDD and MICVDD. They are
> Neither does the datasheet specify the ordering of AVDD, DBVDD, and
> LDO1_IN for power sequencing, just that three should be toggled together.
> Should we model these? Or wait until some design actually splits these?
Yes, the driver for a chip should be a driver for the chip not for some
specific board.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists