All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: linus.walleij@linaro.org
Cc: Conor Dooley <conor.dooley@microchip.com>,
	Rob Herring <robh@kernel.org>,
	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: [PATCH v3 3/5] dt-bindings: pinctrl: document polarfire soc iomux0 pinmux
Date: Wed, 22 Oct 2025 18:12:41 +0100	[thread overview]
Message-ID: <20251022-segment-subfloor-9594ee438da8@spud> (raw)
In-Reply-To: <20251022-caregiver-scrubber-3ad2bc328aea@spud>

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

On Wed, Oct 22, 2025 at 11:09:11AM +0100, Conor Dooley wrote:
> From: Conor Dooley <conor.dooley@microchip.com>
> 
> On Polarfire SoC, iomux0 is responsible for routing functions to either
> Multiprocessor Subsystem (MSS) IOs or to the FPGA fabric, where they
> can either interface with custom RTL or be routed to the FPGA fabric's
> IOs. Document it.
> 
> Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
> Signed-off-by: Conor Dooley <conor.dooley@microchip.com>

> +patternProperties:
> +  '^mux-':
> +    type: object
> +    additionalProperties: false
> +
> +    properties:
> +      function:
> +        description:
> +          A string containing the name of the function to mux to the group.
> +        enum: [ spi0, spi1, i2c0, i2c1, can0, can1, qspi, uart0, uart1, uart2,
> +                uart3, uart4, mdio0, mdio1 ]
> +
> +      groups:
> +        description:
> +          An array of strings. Each string contains the name of a group.
> +        items:
> +          enum: [ spi0_fabric, spi0_mssio, spi1_fabric, spi1_mssio, i2c0_fabric,
> +                  i2c0_mssio, i2c1_fabric, i2c1_mssio, can0_fabric, can0_mssio,
> +                  can1_fabric, can1_mssio, qspi_fabric, qspi_mssio,
> +                  uart0_fabric, uart0_mssio, uart1_fabric, uart1_mssio,
> +                  uart2_fabric, uart2_mssio, uart3_fabric, uart3_mssio,
> +                  uart4_fabric, uart4_mssio, mdio0_fabric, mdio0_mssio,
> +                  mdio1_fabric, mdio1_mssio ]
> +
> +    required:
> +      - function
> +      - groups

I realised a few minutes ago that, despite Rob's review, there's a
mistake here. This, and the gpio2 binding, are both missing a
pinmux-node reference in these child nodes, since that's where the
types for function/groups come from.
I guess I'll send another version tomorrow Linus.

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

  reply	other threads:[~2025-10-22 17:12 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-22 10:09 [PATCH v3 0/5] Microchip mpfs/pic64gx pinctrl Conor Dooley
2025-10-22 10:09 ` [PATCH v3 1/5] dt-bindings: pinctrl: document pic64gx "gpio2" pinmux Conor Dooley
2025-10-22 10:09 ` [PATCH v3 2/5] pinctrl: add pic64gx "gpio2" pinmux driver Conor Dooley
2025-10-22 10:09 ` [PATCH v3 3/5] dt-bindings: pinctrl: document polarfire soc iomux0 pinmux Conor Dooley
2025-10-22 17:12   ` Conor Dooley [this message]
2025-10-22 10:09 ` [PATCH v3 4/5] pinctrl: add polarfire soc iomux0 pinmux driver Conor Dooley
2025-10-22 10:09 ` [PATCH v3 5/5] MAINTAINERS: add Microchip RISC-V pinctrl drivers/bindings to entry 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=20251022-segment-subfloor-9594ee438da8@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.