public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Rob Herring <robh@kernel.org>
Cc: linus.walleij@linaro.org,
	Conor Dooley <conor.dooley@microchip.com>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
	devicetree@vger.kernel.org,
	Valentina.FernandezAlanis@microchip.com
Subject: Re: [RFC v2 1/5] dt-bindings: pinctrl: document polarfire soc mssio pin controller
Date: Thu, 18 Dec 2025 00:59:25 +0000	[thread overview]
Message-ID: <20251218-stack-trilogy-5ae1d795cb17@spud> (raw)
In-Reply-To: <20251216220624.GA3114300-robh@kernel.org>

[-- Attachment #1: Type: text/plain, Size: 1208 bytes --]

On Tue, Dec 16, 2025 at 04:16:31PM -0600, Rob Herring wrote:
> On Thu, Nov 27, 2025 at 10:57:57AM +0000, Conor Dooley wrote:
> > +
> > +          microchip,bank-voltage-microvolt:
> > +            description:
> > +              Which bank voltage to use. This cannot differ for pins in a
> > +              given bank, the whole bank uses the same voltage.
> > +            enum: [ 1200000, 1500000, 1800000, 2500000, 3300000 ]
> 
> "power-source" serves this purpose. It's not well defined as sometimes 
> it's a register value and sometimes a voltage (in various units).

I don't recall exactly why I chose not to use that property, because I
did know it existed. I *think* it was because the selection was not per
pin and I wanted to make it clear - but I should probably just use that
property and add the description from above.

> 
> > +
> > +          microchip,clamp-diode:
> > +            $ref: /schemas/types.yaml#/definitions/flag
> > +            description:
> > +              Reflects the "Clamp Diode" setting in the MSS Configurator for
> > +              this pin. This setting controls whether or not input voltage
> > +              clamping should be enabled.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2025-12-18  0:59 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-27 10:57 [RFC v2 0/5] Microchip mpfs/pic64gx pinctrl part 2 Conor Dooley
2025-11-27 10:57 ` [RFC v2 1/5] dt-bindings: pinctrl: document polarfire soc mssio pin controller Conor Dooley
2025-12-16 22:16   ` Rob Herring
2025-12-18  0:59     ` Conor Dooley [this message]
2025-11-27 10:57 ` [RFC v2 2/5] pinctrl: add generic functions + pins mapper Conor Dooley
2025-12-26  9:29   ` Linus Walleij
2026-01-15 17:50     ` Conor Dooley
2025-11-27 10:57 ` [RFC v2 3/5] pinctrl: add polarfire soc mssio pinctrl driver Conor Dooley
2025-12-26  9:40   ` Linus Walleij
2026-01-15 17:55     ` Conor Dooley
2025-11-27 10:58 ` [RFC v2 4/5] MAINTAINERS: add Microchip mpfs mssio driver/bindings to entry Conor Dooley
2025-11-27 10:58 ` [RFC v2 5/5] riscv: dts: microchip: add pinctrl nodes for mpfs/icicle kit Conor Dooley

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=20251218-stack-trilogy-5ae1d795cb17@spud \
    --to=conor@kernel.org \
    --cc=Valentina.FernandezAlanis@microchip.com \
    --cc=conor.dooley@microchip.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --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