mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Lech Perczak <lech.perczak@camlingroup.com>
To: Hugo Villeneuve <hugo@hugovil.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: linux-gpio@vger.kernel.org,
	Hugo Villeneuve <hvilleneuve@dimonoff.com>,
	linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH v2 1/2] dt-bindings: sc16is7xx: Add property to change GPIO function
Date: Fri, 19 May 2023 15:03:37 +0200	[thread overview]
Message-ID: <1e4e6886-70ed-2db3-23e1-b22bf2f39dc0@camlingroup.com> (raw)
In-Reply-To: <20230518132905.4182265-1-hugo@hugovil.com>

Hello Hugo,

W dniu 18.05.2023 o 15:29, Hugo Villeneuve pisze:
> From: Hugo Villeneuve <hvilleneuve@dimonoff.com>
>
> Some variants in this series of uart controllers have GPIO pins that
> are shared between GPIO and modem control lines.
>
> The pin mux mode (GPIO or modem control lines) can be set for each
> ports (channels) supported by the variant.
>
> This adds a property to the device tree to set the GPIO pin mux to
> modem control lines on selected ports if needed.
>
> Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> ---
> v1 -> v2: Add nxp vendor prefix
>           Add git base-commit
>
>  .../bindings/serial/nxp,sc16is7xx.txt         | 28 +++++++++++++++++++
>  1 file changed, 28 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> index 0fa8e3e43bf8..23a81c83f012 100644
> --- a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> +++ b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> @@ -23,6 +23,9 @@ Optional properties:
>      1 = active low.
>  - irda-mode-ports: An array that lists the indices of the port that
>                    should operate in IrDA mode.
> +- nxp,modem-control-line-ports: An array that lists the indices of the port that
> +                               should have shared GPIO lines configured as modem
> +                               control lines.
>
>  Example:
>          sc16is750: sc16is750@51 {
> @@ -35,6 +38,17 @@ Example:
>                  #gpio-cells = <2>;
>          };
>
> +       sc16is752: sc16is752@54 {
> +               compatible = "nxp,sc16is752";
> +               reg = <0x54>;
> +               clocks = <&clk20m>;
> +               interrupt-parent = <&gpio3>;
> +               interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
> +               nxp,modem-control-line-ports = <1>; /* Port 1 as modem control lines */
> +               gpio-controller; /* Port 0 as GPIOs */
> +               #gpio-cells = <2>;
> +       };
> +
>  * spi as bus
>
>  Required properties:
> @@ -59,6 +73,9 @@ Optional properties:
>      1 = active low.
>  - irda-mode-ports: An array that lists the indices of the port that
>                    should operate in IrDA mode.
> +- nxp,modem-control-line-ports: An array that lists the indices of the port that
> +                               should have shared GPIO lines configured as modem
> +                               control lines.
>
>  Example:
>         sc16is750: sc16is750@0 {
> @@ -70,3 +87,14 @@ Example:
>                 gpio-controller;
>                 #gpio-cells = <2>;
>         };
> +
> +       sc16is752: sc16is752@0 {
> +               compatible = "nxp,sc16is752";
> +               reg = <0>;
> +               clocks = <&clk20m>;
> +               interrupt-parent = <&gpio3>;
> +               interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
> +               nxp,modem-control-line-ports = <1>; /* Port 1 as modem control lines */
Just a minor nitpick: an example showing syntax for both ports would be great.
This can be included here, leaving the previous example intact. Otherwise, LGTM.
> +               gpio-controller; /* Port 0 as GPIOs */
> +               #gpio-cells = <2>;
> +       };
>
> base-commit: 4d6d4c7f541d7027beed4fb86eb2c451bd8d6fff
> --
> 2.30.2

-- 
Pozdrawiam/With kind regards,
Lech Perczak

Sr. Software Engineer
Camlin Technologies Poland Limited Sp. z o.o.
Strzegomska 54,
53-611 Wroclaw
Tel:     (+48) 71 75 000 16
Email:   lech.perczak@camlingroup.com
Website: http://www.camlingroup.com


  parent reply	other threads:[~2023-05-19 13:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-18 13:29 Hugo Villeneuve
2023-05-18 13:29 ` [RFC PATCH v2 2/2] serial: sc16is7xx: fix regression with GPIO configuration Hugo Villeneuve
2023-05-19 13:00   ` Lech Perczak
2023-05-19 13:30     ` Hugo Villeneuve
2023-05-19 16:00       ` Lech Perczak
2023-05-19 16:38         ` Hugo Villeneuve
2023-05-19 16:56           ` Lech Perczak
2023-05-19 19:23             ` Hugo Villeneuve
2023-05-19 13:41     ` Hugo Villeneuve
2023-05-18 19:24 ` [RFC PATCH v2 1/2] dt-bindings: sc16is7xx: Add property to change GPIO function Conor Dooley
2023-05-19 13:03 ` Lech Perczak [this message]
2023-05-25  3:37   ` Hugo Villeneuve

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=1e4e6886-70ed-2db3-23e1-b22bf2f39dc0@camlingroup.com \
    --to=lech.perczak@camlingroup.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hugo@hugovil.com \
    --cc=hvilleneuve@dimonoff.com \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@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

all inboxes | Powered by JetHome®