devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-gpio@vger.kernel.org, devicetree@vger.kernel.org,
	Nishanth Menon <nm@ti.com>, Vignesh Raghavendra <vigneshr@ti.com>
Subject: Re: [PATCH v4 2/2] dt-bindings: pinctrl: Update pinctrl-single to use yaml
Date: Wed, 10 May 2023 14:20:51 +0300	[thread overview]
Message-ID: <20230510112051.GD14287@atomide.com> (raw)
In-Reply-To: <20230510095330.30742-2-tony@atomide.com>

* Tony Lindgren <tony@atomide.com> [230510 09:54]:
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/pinctrl/pinctrl-single.yaml
...
> +patternProperties:
...
> +  'cpsw_default|cpsw_sleep|davinci_mdio_default|davinci_mdio_sleep':
> +    description: Deprecated legacy naming for cpsw and mdio on TI SoCs
> +    deprecated: true
> +    type: object
> +    $ref: pinmux-node.yaml#
> +
> +  'usb1_drvvbus|usb_hub_ctrl|usb2_phy':
> +    description: Deprecated legacy naming for USB on TI SoCs
> +    deprecated: true
> +    type: object
> +    $ref: pinmux-node.yaml#
> +
> +  'gpio_keys_s0|matrix_keypad_default|matrix_keypad_sleep|matrix_keypad_s0':
> +    description: Deprecated legacy naming for input on TI SoCs
> +    deprecated: true
> +    type: object
> +    $ref: pinmux-node.yaml#
> +
> +  'user_leds_s0|gpio_led_pmx':
> +    description: Deprecated legacy naming for LEDs on TI SoCs
> +    deprecated: true
> +    type: object
> +    $ref: pinmux-node.yaml#
> +
> +  'nand_flash_x8':
> +    description: Deprecated legacy naming for NAND on TI SoCs
> +    deprecated: true
> +    type: object
> +    $ref: pinmux-node.yaml#

Looks like fixing the pin group node names for all the older TI SoC dts
files should not be too bad, for example diffstat for experimental am335x
changes is:

42 files changed, 323 insertions(+), 323 deletions(-)

This includes changing node names to use - instead of _ while at it.
I'll send out about 10 or so patches once Rob has the dts subdirectories
created.

Regards,

Tony

  reply	other threads:[~2023-05-10 11:21 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-10  9:53 [PATCH v4 1/2] dt-bindings: pinctrl: Allow use of pinconf in addition to pinctrl and pinmux Tony Lindgren
2023-05-10  9:53 ` [PATCH v4 2/2] dt-bindings: pinctrl: Update pinctrl-single to use yaml Tony Lindgren
2023-05-10 11:20   ` Tony Lindgren [this message]
2023-05-10 12:48   ` Krzysztof Kozlowski
2023-05-17  8:00     ` Tony Lindgren
2023-05-17  8:23       ` Krzysztof Kozlowski
2023-05-17  9:14         ` Tony Lindgren
2023-05-10 10:13 ` [PATCH v4 1/2] dt-bindings: pinctrl: Allow use of pinconf in addition to pinctrl and pinmux Krzysztof Kozlowski
2023-05-10 10:16   ` Tony Lindgren

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=20230510112051.GD14287@atomide.com \
    --to=tony@atomide.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=nm@ti.com \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    /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).