public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
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
Date: Sat, 9 Mar 2024 13:22:35 +0100	[thread overview]
Message-ID: <1ee8fc6f-5299-4ba5-bb61-14b4351c0708@gmail.com> (raw)

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

             reply	other threads:[~2024-03-09 12:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-09 12:22 Javier Carrasco [this message]
2024-03-09 15:00 ` trivial-devices with vdd-supply: true Krzysztof Kozlowski
2024-03-09 15:35   ` Javier Carrasco

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1ee8fc6f-5299-4ba5-bb61-14b4351c0708@gmail.com \
    --to=javier.carrasco.cruz@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox