Devicetree
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: linux-kernel@vger.kernel.org, monstr@monstr.eu,
	michal.simek@xilinx.com, git@xilinx.com, stable@vger.kernel.org,
	Benjamin Gaignard <benjamin.gaignard@st.com>,
	Conor Dooley <conor+dt@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jirislaby@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Rob Herring <robh@kernel.org>,
	"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	"open list:TTY LAYER AND SERIAL DRIVERS"
	<linux-serial@vger.kernel.org>
Subject: Re: [PATCH v2] dt-bindings: serial: rs485: Fix rs485-rts-delay property
Date: Fri, 13 Sep 2024 18:24:47 +0100	[thread overview]
Message-ID: <20240913-sulk-threaten-79448edf988a@spud> (raw)
In-Reply-To: <1b60e457c2f1bfa2284291ad58af02c982936ac8.1726224922.git.michal.simek@amd.com>

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

On Fri, Sep 13, 2024 at 12:55:23PM +0200, Michal Simek wrote:
> Code expects array only with 2 items which should be checked.
> But also item checking is not working as it should likely because of
> incorrect items description.
> 
> Fixes: d50f974c4f7f ("dt-bindings: serial: Convert rs485 bindings to json-schema")
> Signed-off-by: Michal Simek <michal.simek@amd.com>
> Cc: <stable@vger.kernel.org>
> ---
> 
> Changes in v2:
> - Remove maxItems properties which are not needed
> - Add stable ML to CC
> 
>  .../devicetree/bindings/serial/rs485.yaml     | 19 +++++++++----------
>  1 file changed, 9 insertions(+), 10 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/serial/rs485.yaml b/Documentation/devicetree/bindings/serial/rs485.yaml
> index 9418fd66a8e9..9665de41762e 100644
> --- a/Documentation/devicetree/bindings/serial/rs485.yaml
> +++ b/Documentation/devicetree/bindings/serial/rs485.yaml
> @@ -18,16 +18,15 @@ properties:
>      description: prop-encoded-array <a b>
>      $ref: /schemas/types.yaml#/definitions/uint32-array
>      items:
> -      items:
> -        - description: Delay between rts signal and beginning of data sent in
> -            milliseconds. It corresponds to the delay before sending data.
> -          default: 0
> -          maximum: 100
> -        - description: Delay between end of data sent and rts signal in milliseconds.
> -            It corresponds to the delay after sending data and actual release
> -            of the line.
> -          default: 0
> -          maximum: 100
> +      - description: Delay between rts signal and beginning of data sent in
> +          milliseconds. It corresponds to the delay before sending data.
> +        default: 0
> +        maximum: 50

I would expect to see some mention in the commit message as to why the
maximum has changed from 100 to 50 milliseconds.

> +      - description: Delay between end of data sent and rts signal in milliseconds.
> +          It corresponds to the delay after sending data and actual release
> +          of the line.
> +        default: 0
> +        maximum: 100
>  
>    rs485-rts-active-high:
>      description: drive RTS high when sending (this is the default).
> -- 
> 2.43.0
> 

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

  reply	other threads:[~2024-09-13 17:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-13 10:55 [PATCH v2] dt-bindings: serial: rs485: Fix rs485-rts-delay property Michal Simek
2024-09-13 17:24 ` Conor Dooley [this message]
2024-09-16  5:55   ` Michal Simek

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=20240913-sulk-threaten-79448edf988a@spud \
    --to=conor@kernel.org \
    --cc=benjamin.gaignard@st.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=git@xilinx.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jirislaby@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=michal.simek@amd.com \
    --cc=michal.simek@xilinx.com \
    --cc=monstr@monstr.eu \
    --cc=robh@kernel.org \
    --cc=stable@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