From: Hugo Villeneuve <hugo@hugovil.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: gregkh@linuxfoundation.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, conor+dt@kernel.org,
jirislaby@kernel.org, jringle@gridpoint.com,
jesse.sung@canonical.com, isaac.true@canonical.com,
l.perczak@camlintechnologies.com, tomasz.mon@camlingroup.com,
linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
stable@vger.kernel.org, Conor Dooley <conor.dooley@microchip.com>,
Lech Perczak <lech.perczak@camlingroup.com>
Subject: Re: [PATCH v8 05/10] dt-bindings: sc16is7xx: Add property to change GPIO function
Date: Wed, 7 Jun 2023 10:52:49 -0400 [thread overview]
Message-ID: <20230607105249.6dc95ed226e3578a3c9116aa@hugovil.com> (raw)
In-Reply-To: <a6301c0e-b774-8963-8eb1-8e0948b1468c@linaro.org>
On Wed, 7 Jun 2023 16:46:56 +0200
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> On 07/06/2023 16:41, Hugo Villeneuve wrote:
> > On Wed, 7 Jun 2023 16:30:26 +0200
> > Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> wrote:
> >
> >> On 07/06/2023 16:05, Hugo Villeneuve wrote:
> >>> 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.
> >>>
> >>> Cc: <stable@vger.kernel.org> # 6.1.x
> >>> Signed-off-by: Hugo Villeneuve <hvilleneuve@dimonoff.com>
> >>> Acked-by: Conor Dooley <conor.dooley@microchip.com>
> >>> Reviewed-by: Lech Perczak <lech.perczak@camlingroup.com>
> >>> ---
> >>> .../bindings/serial/nxp,sc16is7xx.txt | 46 +++++++++++++++++++
> >>> 1 file changed, 46 insertions(+)
> >>>
> >>> diff --git a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.txt
> >>> index 0fa8e3e43bf8..1a7e4bff0456 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,26 @@ Example:
> >>> #gpio-cells = <2>;
> >>> };
> >>>
> >>> + sc16is752: sc16is752@53 {
> >>
> >> Since you keep sending new versions, fix the names. nNode names should
> >> be generic. See also explanation and list of examples in DT specification:
> >> https://devicetree-specification.readthedocs.io/en/latest/chapter2-devicetree-basics.html#generic-names-recommendation
> >
> > Hi,
> > by the way, I do not "keep sending new versions" just for the fun of
> > it...
>
> Sure, I know. So when the next version is necessary to send, fix also this.
>
> >
> > Even after reading your link, I cannot see what is wrong with that
> > name.
>
> They are not generic. They are specific.
What do you mean by "They"? My patch adds only a new property...
This patch will not fix old names, but a future patch could do it.
And what do you mean by "They are not generic. They are specific". Of
course the property is specific, because it relates to something very
specific to this chip?
> > You are the first one since V1 to think it is inappropriate.
> >
> > Please suggest what the name should be.
>
> Depends what this is. I know nothing about this device, so I cannot
> suggest you. Therefore I gave you link with ideas to choose from.
>
> Best regards,
> Krzysztof
>
>
next prev parent reply other threads:[~2023-06-07 14:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-07 14:05 [PATCH v8 00/10] serial: sc16is7xx: fix GPIO regression and rs485 improvements Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 01/10] serial: sc16is7xx: fix broken port 0 uart init Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 02/10] serial: sc16is7xx: mark IOCONTROL register as volatile Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 03/10] serial: sc16is7xx: remove obsolete out_thread label Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 04/10] serial: sc16is7xx: refactor GPIO controller registration Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 05/10] dt-bindings: sc16is7xx: Add property to change GPIO function Hugo Villeneuve
2023-06-07 14:30 ` Krzysztof Kozlowski
2023-06-07 14:41 ` Hugo Villeneuve
2023-06-07 14:46 ` Krzysztof Kozlowski
2023-06-07 14:52 ` Hugo Villeneuve [this message]
2023-06-07 14:57 ` Krzysztof Kozlowski
2023-06-07 15:09 ` Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 06/10] serial: sc16is7xx: fix regression with GPIO configuration Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 07/10] serial: sc16is7xx: fix bug when first setting GPIO direction Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 08/10] serial: sc16is7xx: add call to get rs485 DT flags and properties Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 09/10] serial: sc16is7xx: add post reset delay Hugo Villeneuve
2023-06-07 14:05 ` [PATCH v8 10/10] serial: sc16is7xx: improve comments about variants Hugo Villeneuve
2023-06-12 12:10 ` [PATCH v8 00/10] serial: sc16is7xx: fix GPIO regression and rs485 improvements Lech Perczak
2023-06-12 13:40 ` 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=20230607105249.6dc95ed226e3578a3c9116aa@hugovil.com \
--to=hugo@hugovil.com \
--cc=conor+dt@kernel.org \
--cc=conor.dooley@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hvilleneuve@dimonoff.com \
--cc=isaac.true@canonical.com \
--cc=jesse.sung@canonical.com \
--cc=jirislaby@kernel.org \
--cc=jringle@gridpoint.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=l.perczak@camlintechnologies.com \
--cc=lech.perczak@camlingroup.com \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tomasz.mon@camlingroup.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).