Linux IIO development
 help / color / mirror / Atom feed
From: <Victor.Duicu@microchip.com>
To: <conor@kernel.org>
Cc: <dlechner@baylibre.com>, <nuno.sa@analog.com>,
	<linux-iio@vger.kernel.org>, <devicetree@vger.kernel.org>,
	<robh@kernel.org>, <jic23@kernel.org>, <andy@kernel.org>,
	<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<Marius.Cristea@microchip.com>, <conor+dt@kernel.org>
Subject: Re: [PATCH v3 1/2] dt-bindings: iio: temperature: add support for MCP998X
Date: Mon, 23 Jun 2025 13:07:53 +0000	[thread overview]
Message-ID: <8c80baf4616dbec339f3108690046e1dc43e24ae.camel@microchip.com> (raw)
In-Reply-To: <20250613-undergo-reviving-a97dca8f3b69@spud>

On Fri, 2025-06-13 at 15:40 +0100, Conor Dooley wrote:
> On Fri, Jun 13, 2025 at 04:02:06PM +0300,
> victor.duicu@microchip.com wrote:
> > From: Victor Duicu <victor.duicu@microchip.com>
> > 

Hi Conor,

> > This is the devicetree schema for Microchip MCP998X/33 and
> > MCP998XD/33D Automotive Temperature Monitor Family.
> > 
> > Signed-off-by: Victor Duicu <victor.duicu@microchip.com>
> > ---
> >  .../iio/temperature/microchip,mcp9982.yaml    | 211
> > ++++++++++++++++++
> >  1 file changed, 211 insertions(+)
> >  create mode 100644
> > Documentation/devicetree/bindings/iio/temperature/microchip,mcp9982
> > .yaml
> > 
> > diff --git
> > a/Documentation/devicetree/bindings/iio/temperature/microchip,mcp99
> > 82.yaml
> > b/Documentation/devicetree/bindings/iio/temperature/microchip,mcp99
> > 82.yaml
> > new file mode 100644
> > index 000000000000..ec939d463612
> > --- /dev/null
> > +++
> > b/Documentation/devicetree/bindings/iio/temperature/microchip,mcp99
> > 82.yaml
> > @@ -0,0 +1,211 @@
> > +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> > 
> > +
> > +  microchip,resistance-comp-ch1-2-enable:
> > +    description:
> > +      Enable resistance error correction(REC) for external
> > channels 1 and 2.
> > +      The chip internal hardware counterbalances the parasitic
> > resistance in
> > +      series with the external diodes. The compensation can be
> > activated or
> > +      disabled in hardware for both channels 1 and 2 at the same
> > time.
> > +    type: boolean
> 
> On the previous version I objected to this wording for the property,
> where it is being used as an enable, and instead said that it should
> indicate the presence of the parasitic resistance. Did I miss some
> sort
> of new justification for it still talking about being an enable?
> 

My apologies, I forgot to modify the name of the variable.
I will change the variables to something like:

microchip,parasitic-res-on-channel1-2:
description:
Indicates that the chip and the diodes/transistors are sufficiently far
apart that a parasitic resistance is added to the wires, which can
affect the measurements. Due to the anti-parallel diode connections,
channels 1 and 2 are affected together.

> 
> > +  microchip,resistance-comp-ch3-4-enable:
> > +    description:
> > +      Enable resistance error correction(REC) for external
> > channels 3 and 4.
> > +      The chip internal hardware counterbalances the parasitic
> > resistance in
> > +      series with the external diodes. The compensation can be
> > activated or
> > +      disabled in hardware for both channels 3 and 4 at the same
> > time.
> > +    type: boolean
> 
With Kind Regards,
Victor Duicu

> Cheers,
> Conor.

  reply	other threads:[~2025-06-23 13:07 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-13 13:02 [PATCH v3 0/2] add support for MCP998X victor.duicu
2025-06-13 13:02 ` [PATCH v3 1/2] dt-bindings: iio: temperature: " victor.duicu
2025-06-13 14:40   ` Conor Dooley
2025-06-23 13:07     ` Victor.Duicu [this message]
2025-07-28 13:01   ` Victor.Duicu
2025-07-29 16:27     ` David Lechner
2025-06-13 13:02 ` [PATCH v3 2/2] " victor.duicu
2025-06-13 21:50   ` Andy Shevchenko
2025-06-19  7:22     ` Victor.Duicu
2025-06-19  8:29       ` Andy Shevchenko
2025-06-21 17:19         ` Jonathan Cameron
2025-06-23  6:45           ` Andy Shevchenko
2025-06-14 13:18   ` Jonathan Cameron
2025-06-14 13:27     ` 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=8c80baf4616dbec339f3108690046e1dc43e24ae.camel@microchip.com \
    --to=victor.duicu@microchip.com \
    --cc=Marius.Cristea@microchip.com \
    --cc=andy@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=conor@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dlechner@baylibre.com \
    --cc=jic23@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-iio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nuno.sa@analog.com \
    --cc=robh@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