Received-SPF: pass (google.com: domain of linux-kernel+bounces-97875-linux.lists.archive=gmail.com@vger.kernel.org designates 147.75.199.223 as permitted sender) client-ip=147.75.199.223;
Message-ID: <1ee8fc6f-5299-4ba5-bb61-14b4351c0708@gmail.com>
Date: Sat, 9 Mar 2024 13:22:35 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: en-US
From: Javier Carrasco <javier.carrasco.cruz@gmail.com>
To: Rob Herring <robh+dt@kernel.org>,
 Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
 Conor Dooley <conor+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: trivial-devices with vdd-supply: true
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi,

I am trying to figure out the current policy to add trivial devices
(I2C/SPI devices with at most one interrupt) to trivial-devices.yaml or
include a dedicated file.

Apparently, bindings for the same sort of devices where "vdd-supply" is
provided require their own file, and I wonder why there is no
"vdd/supplied/whatever-trivial-devices.yaml".

Instead, files with trivial bindings + "vdd-supply: true" are added on a
regular basis. That property is not saying anything specific about the
device beyond that it needs a supply, which is very common. Is that
intended and no more generic bindings are desired?

On the other hand, trivial-devices.yaml includes several devices that do
require a single supply (e.g. several sensors), but it is not explicitly
documented. Did the requirement of providing vdd-supply arise after
those devices were added to trivial-devices? I think that some devices
that were added to trivial-devices in the last months could have also
had a vdd-supply property, so I am not sure about the rules to choose
one way or another.

Thanks and best regards,
Javier Carrasco