[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BN6PR03MB339557689BCCF795B18C68319B05A@BN6PR03MB3395.namprd03.prod.outlook.com>
Date: Mon, 31 Jul 2023 07:40:14 +0000
From: "Miclaus, Antoniu" <Antoniu.Miclaus@...log.com>
To: Jonathan Cameron <jic23@...nel.org>
CC: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
"robh+dt@...nel.org" <robh+dt@...nel.org>,
"krzysztof.kozlowski+dt@...aro.org"
<krzysztof.kozlowski+dt@...aro.org>,
"conor+dt@...nel.org" <conor+dt@...nel.org>,
"linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: RE: [PATCH] dt-bindings: iio: admv1014: make all regs required
> -----Original Message-----
> From: Jonathan Cameron <jic23@...nel.org>
> Sent: Saturday, July 29, 2023 2:55 PM
> To: Miclaus, Antoniu <Antoniu.Miclaus@...log.com>
> Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>;
> robh+dt@...nel.org; krzysztof.kozlowski+dt@...aro.org;
> conor+dt@...nel.org; linux-iio@...r.kernel.org;
> devicetree@...r.kernel.org; linux-kernel@...r.kernel.org
> Subject: Re: [PATCH] dt-bindings: iio: admv1014: make all regs required
>
> [External]
>
> On Thu, 27 Jul 2023 12:02:04 +0000
> "Miclaus, Antoniu" <Antoniu.Miclaus@...log.com> wrote:
>
> > > -----Original Message-----
> > > From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
> > > Sent: Thursday, July 27, 2023 2:47 PM
> > > To: Miclaus, Antoniu <Antoniu.Miclaus@...log.com>; jic23@...nel.org;
> > > robh+dt@...nel.org; krzysztof.kozlowski+dt@...aro.org;
> > > conor+dt@...nel.org; linux-iio@...r.kernel.org;
> > > devicetree@...r.kernel.org; linux-kernel@...r.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.
>
Hello Jonathan,
Not sure if I fully understand. Should I drop this patch?
And also drop the "required" of the regulators in the admv1013 patch?
https://patchwork.kernel.org/project/linux-iio/patch/20230727110121.93546-1-antoniu.miclaus@analog.com/
Thanks,
> 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
> >
Powered by blists - more mailing lists