[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20260120-daring-amethyst-shark-50ebcc@quoll>
Date: Tue, 20 Jan 2026 11:35:27 +0100
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Petr Hodina <petr.hodina@...tonmail.com>
Cc: Song Qiang <songqiang1304521@...il.com>,
Jonathan Cameron <jic23@...nel.org>, David Lechner <dlechner@...libre.com>,
Nuno Sá <nuno.sa@...log.com>, Andy Shevchenko <andy@...nel.org>, Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>, Conor Dooley <conor+dt@...nel.org>,
Liam Girdwood <lgirdwood@...il.com>, Mark Brown <broonie@...nel.org>,
David Heidelberg <david@...t.cz>, linux-iio@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/4] iio: proximity: vl53l0x-i2c: Add optional vddio
regulator
On Mon, Jan 19, 2026 at 06:19:55PM +0100, Petr Hodina wrote:
> The VL53L0X can be powered using separate core (VDD) and I/O (VDDIO)
There is no VDDIO pin. I checked on datasheet.
> supplies. Add support for an optional vio regulator and enable/disable
> it during power on/off when present.
Last sentence is incorrect in this context. This patch is not doing that
and anyway, whatever your driver is doing is not here really that
relevant.
Best regards,
Krzysztof
Powered by blists - more mailing lists