From: Rob Herring <robh@kernel.org>
To: Brenda Streiff <brenda.streiff@ni.com>
Cc: Gratian Crisan <gratian.crisan@ni.com>,
Jason Smith <jason.smith@ni.com>,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v6 tty-next 1/2] dt-bindings: serial: ni,ni16650: add bindings
Date: Tue, 24 Oct 2023 08:33:34 -0500 [thread overview]
Message-ID: <20231024133334.GA3505191-robh@kernel.org> (raw)
In-Reply-To: <20231023210458.447779-2-brenda.streiff@ni.com>
On Mon, Oct 23, 2023 at 04:04:56PM -0500, Brenda Streiff wrote:
> Add bindings for the NI 16550 UART.
>
> Signed-off-by: Brenda Streiff <brenda.streiff@ni.com>
> Cc: Gratian Crisan <gratian.crisan@ni.com>
> Cc: Jason Smith <jason.smith@ni.com>
> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
> ---
> .../bindings/serial/ni,ni16550.yaml | 51 +++++++++++++++++++
> 1 file changed, 51 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/serial/ni,ni16550.yaml
>
> diff --git a/Documentation/devicetree/bindings/serial/ni,ni16550.yaml b/Documentation/devicetree/bindings/serial/ni,ni16550.yaml
> new file mode 100644
> index 000000000000..72ab125dd892
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/serial/ni,ni16550.yaml
> @@ -0,0 +1,51 @@
> +# SPDX-License-Identifier: (GPL-2.0 OR BSD-2-Clause)
> +%YAML 1.2
> +---
> +$id: http://devicetree.org/schemas/serial/ni,ni16550.yaml#
> +$schema: http://devicetree.org/meta-schemas/core.yaml#
> +
> +title: NI 16550 asynchronous serial interface (UART)
Is this significantly different than all the other 8250 compatible UARTs
in 8250.yaml?
> +
> +maintainers:
> + - Brenda Streiff <brenda.streiff@ni.com>
> +
> +allOf:
> + - $ref: serial.yaml#
> +
> +properties:
> + compatible:
> + const: ni,ni16550
> +
> + reg:
> + maxItems: 1
> +
> + interrupts:
> + maxItems: 1
> +
> + clocks:
> + maxItems: 1
> +
> + ni,serial-port-mode:
> + description: Indicates whether this is an RS-232 or RS-485 serial port.
> + $ref: /schemas/types.yaml#/definitions/string
> + enum: [ RS-232, RS-485 ]
> + default: RS-485
We already have 'linux,rs485-enabled-at-boot-time' which seems similar
purpose. It also tells me this is not a fixed in hardware setting. If
that property doesn't work for you, come up with something common and
explain why. Or explain why this is completely unique to this UART.
Rob
next prev parent reply other threads:[~2023-10-24 13:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-23 21:04 [PATCH v6 tty-next 0/2] serial: Add driver for National Instruments UARTs Brenda Streiff
2023-10-23 21:04 ` [PATCH v6 tty-next 1/2] dt-bindings: serial: ni,ni16650: add bindings Brenda Streiff
2023-10-24 13:33 ` Rob Herring [this message]
2023-10-23 21:04 ` [PATCH v6 tty-next 2/2] serial: 8250: add driver for NI UARTs Brenda Streiff
2023-10-24 5:54 ` Jiri Slaby
2023-10-24 10:10 ` Ilpo Järvinen
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=20231024133334.GA3505191-robh@kernel.org \
--to=robh@kernel.org \
--cc=brenda.streiff@ni.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gratian.crisan@ni.com \
--cc=gregkh@linuxfoundation.org \
--cc=jason.smith@ni.com \
--cc=jirislaby@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.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;
as well as URLs for NNTP newsgroup(s).