From: "Rob Herring (Arm)" <robh@kernel.org>
To: "André Draszik" <andre.draszik@linaro.org>
Cc: devicetree@vger.kernel.org,
Peter Griffin <peter.griffin@linaro.org>,
linux-kernel@vger.kernel.org,
Will McVicker <willmcvicker@google.com>,
linux-serial@vger.kernel.org, kernel-team@android.com,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Jiri Slaby <jirislaby@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tudor Ambarus <tudor.ambarus@linaro.org>,
Conor Dooley <conor+dt@kernel.org>
Subject: Re: [PATCH v4 2/2] dt-bindings: serial: samsung: fix maxItems for gs101
Date: Mon, 22 Jul 2024 17:24:27 -0600 [thread overview]
Message-ID: <172169065730.292676.195019467020873816.robh@kernel.org> (raw)
In-Reply-To: <20240712-gs101-uart-binding-v4-2-24e9f8d4bdcb@linaro.org>
On Fri, 12 Jul 2024 15:51:18 +0100, André Draszik wrote:
> While gs101 needs exactly two clocks for the UART, the schema doesn't
> currently limit the maximum number to this and instead the default of
> five from this schema is applied.
>
> Update the schema accordingly.
>
> Signed-off-by: André Draszik <andre.draszik@linaro.org>
>
> ---
> v4:
> * drop description from clocks:, it was Linux-specific and a we'll
> implement something that makes it obsolete anyway
> * no need to duplicate clock-names anymore
> ---
> Documentation/devicetree/bindings/serial/samsung_uart.yaml | 6 ++++++
> 1 file changed, 6 insertions(+)
>
Reviewed-by: Rob Herring (Arm) <robh@kernel.org>
prev parent reply other threads:[~2024-07-22 23:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-12 14:51 [PATCH v4 0/2] dt-bindings: serial: samsung: style and gs101 fixes André Draszik
2024-07-12 14:51 ` [PATCH v4 1/2] dt-bindings: serial: samsung: avoid duplicating permitted clock-names André Draszik
2024-07-22 23:23 ` Rob Herring
2024-07-12 14:51 ` [PATCH v4 2/2] dt-bindings: serial: samsung: fix maxItems for gs101 André Draszik
2024-07-22 23:24 ` Rob Herring (Arm) [this message]
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=172169065730.292676.195019467020873816.robh@kernel.org \
--to=robh@kernel.org \
--cc=andre.draszik@linaro.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=kernel-team@android.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=peter.griffin@linaro.org \
--cc=tudor.ambarus@linaro.org \
--cc=willmcvicker@google.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