From: Jonathan Cameron <jic23@kernel.org>
To: "Miclaus, Antoniu" <Antoniu.Miclaus@analog.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"linux-iio@vger.kernel.org" <linux-iio@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required
Date: Sat, 29 Jul 2023 12:55:16 +0100 [thread overview]
Message-ID: <20230729125516.68a29852@jic23-huawei> (raw)
In-Reply-To: <BN6PR03MB3395F9139A225AA97A100B829B01A@BN6PR03MB3395.namprd03.prod.outlook.com>
On Thu, 27 Jul 2023 12:02:04 +0000
"Miclaus, Antoniu" <Antoniu.Miclaus@analog.com> wrote:
> > -----Original Message-----
> > From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> > Sent: Thursday, July 27, 2023 2:47 PM
> > To: Miclaus, Antoniu <Antoniu.Miclaus@analog.com>; jic23@kernel.org;
> > robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org;
> > conor+dt@kernel.org; linux-iio@vger.kernel.org;
> > devicetree@vger.kernel.org; linux-kernel@vger.kernel.org
> > Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required
> >
> > [External]
> >
> > On 27/07/2023 13:31, Antoniu Miclaus wrote:
> > > Since the regulators are required in the driver implementation, make
> > > them required also in the bindings.
This bit is probably not strictly true. Try no providing them and you will
probably find stub regulators created on assumption they are fixed regs
that we aren't interested in controlling.
> > >
> >
> > The true reason should be whether the hardware requires them. Because if
> > hardware does not need some, the driver should be fixed.
> The datasheet is not very explicit on this topic, but all the specifications of the
> part are built around these pins being supplied.
> Moreover, the evaluation board or the part comes with all VCC pins connected
> to fixed supplies.
Agreed - these should be required in the binding.
There was an old disagreement on this in which it they were not marked
required in some bindings because the regulator subsystem would assume they
were fixed supplies that were just missing in the DT and so provides stub regulators.
My understanding at least has changed and now we mark the required even if
the driver works fine on some boards without them being supplied.
Note though that this means the whole of trivial-devices.yaml is garbage
as very few devices actually work without any power :)
Jonathan
> > Best regards,
> > Krzysztof
>
next prev parent reply other threads:[~2023-07-29 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 11:31 [PATCH] dt-bindings: iio: admv1014: make all regs required Antoniu Miclaus
2023-07-27 11:47 ` Krzysztof Kozlowski
2023-07-27 12:02 ` Miclaus, Antoniu
2023-07-29 11:55 ` Jonathan Cameron [this message]
2023-07-31 7:40 ` Miclaus, Antoniu
2023-07-31 10:13 ` Jonathan Cameron
2023-07-31 10:16 ` Miclaus, Antoniu
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=20230729125516.68a29852@jic23-huawei \
--to=jic23@kernel.org \
--cc=Antoniu.Miclaus@analog.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-iio@vger.kernel.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