From: <Marius.Cristea@microchip.com>
To: <jic23@kernel.org>
Cc: <devicetree@vger.kernel.org>, <conor+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>, <lars@metafoo.de>,
<linux-iio@vger.kernel.org>, <robh+dt@kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] iio: adc: adding support for MCP3564 ADC
Date: Fri, 18 Aug 2023 16:29:26 +0000 [thread overview]
Message-ID: <1c0f578669737e7f27a8ff9e0416b6c96eb917f2.camel@microchip.com> (raw)
In-Reply-To: <20230805185900.2441a20e@jic23-huawei>
Hi Jonathan,
>
> > @@ -0,0 +1,53 @@
> > +What:
> > /sys/bus/iio/devices/iio:deviceX/boost_current
> > +KernelVersion: 6.4
> > +Contact: linux-iio@vger.kernel.org
> > +Description:
> > + This attribute is used to set the biasing circuit of
> > the
> > + Delta-Sigma modulator. The different BOOST settings
> > are applied
> > + to the entire modulator circuit, including the
> > voltage reference
> > + buffers.
>
> Units? Should be mA given that is what we use for other current
> attributes
> in IIO.
>
This should have no units because is a "gain" for the bias current. I
think it will be better to change the name of the attribute to
"boost_current_gain".
> This one may cause us problems with generality of the description if
> we reuse
> if for other devices (and hence move it to the more general files),
> but we
> can figure this out at the time.
>
> >
Thanks and Best Regards,
Marius
next prev parent reply other threads:[~2023-08-18 16:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 14:28 [PATCH v3 0/2] Adding support for Microchip MCP3564 ADC family marius.cristea
2023-08-04 14:28 ` [PATCH v3 1/2] dt-bindings: iio: adc: adding MCP3564 ADC marius.cristea
2023-08-05 17:39 ` Jonathan Cameron
2023-08-04 14:28 ` [PATCH v3 2/2] iio: adc: adding support for " marius.cristea
2023-08-05 17:59 ` Jonathan Cameron
2023-08-18 16:29 ` Marius.Cristea [this message]
2023-08-28 13:48 ` Jonathan Cameron
2023-08-04 15:28 ` [PATCH v3 0/2] Adding support for Microchip MCP3564 ADC family Conor Dooley
2023-08-05 17:08 ` Jonathan Cameron
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=1c0f578669737e7f27a8ff9e0416b6c96eb917f2.camel@microchip.com \
--to=marius.cristea@microchip.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jic23@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lars@metafoo.de \
--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;
as well as URLs for NNTP newsgroup(s).