From: Rob Herring <robh@kernel.org>
To: Phil Edworthy <phil.edworthy@renesas.com>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>,
Magnus Damm <magnus.damm@gmail.com>,
Biju Das <biju.das.jz@bp.renesas.com>,
linux-renesas-soc@vger.kernel.org, linux-serial@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v4 1/2] dt-bindings: serial: renesas,em-uart: Add RZ/V2M clock to access the registers
Date: Wed, 11 May 2022 10:03:58 -0500 [thread overview]
Message-ID: <20220511150358.GA305958-robh@kernel.org> (raw)
In-Reply-To: <20220504094456.24386-2-phil.edworthy@renesas.com>
On Wed, May 04, 2022 at 10:44:55AM +0100, Phil Edworthy wrote:
> The RZ/V2M SoC has an additional clock to access the registers. The HW
> manual says this clock should not be touched as it is used by the
> "ISP Firmware".
>
> Signed-off-by: Phil Edworthy <phil.edworthy@renesas.com>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
> ---
> v4:
> - Removed "optional" from description of clock to access the registers
> v3:
> - New patch added
> ---
> .../bindings/serial/renesas,em-uart.yaml | 32 +++++++++++++++----
> 1 file changed, 25 insertions(+), 7 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/serial/renesas,em-uart.yaml b/Documentation/devicetree/bindings/serial/renesas,em-uart.yaml
> index 332c385618e1..40a03f255666 100644
> --- a/Documentation/devicetree/bindings/serial/renesas,em-uart.yaml
> +++ b/Documentation/devicetree/bindings/serial/renesas,em-uart.yaml
> @@ -9,9 +9,6 @@ title: Renesas EMMA Mobile UART Interface
> maintainers:
> - Magnus Damm <magnus.damm@gmail.com>
>
> -allOf:
> - - $ref: serial.yaml#
> -
> properties:
> compatible:
> oneOf:
> @@ -29,11 +26,32 @@ properties:
> interrupts:
> maxItems: 1
>
> - clocks:
> - maxItems: 1
> +allOf:
> + - $ref: serial.yaml#
>
> - clock-names:
> - const: sclk
> + - if:
> + properties:
> + compatible:
> + contains:
> + const: renesas,r9a09g011-uart
> + then:
> + properties:
> + clocks:
> + items:
> + - description: UART functional clock
> + - description: Internal clock to access the registers
> + clock-names:
> + items:
> + - const: sclk
> + - const: pclk
Better to put all this at the top level with 'minItems: 1' and then use
minItems/maxItems in the if/then schema to define which platforms have 1
or 2 clocks.
> + else:
> + properties:
> + clocks:
> + items:
> + - description: UART functional clock
> + clock-names:
> + items:
> + - const: sclk
>
> required:
> - compatible
> --
> 2.32.0
>
>
next prev parent reply other threads:[~2022-05-11 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 9:44 [PATCH v4 0/2] Add new Renesas RZ/V2M SoC and Renesas RZ/V2M EVK support Phil Edworthy
2022-05-04 9:44 ` [PATCH v4 1/2] dt-bindings: serial: renesas,em-uart: Add RZ/V2M clock to access the registers Phil Edworthy
2022-05-11 15:03 ` Rob Herring [this message]
2022-05-12 7:04 ` Phil Edworthy
2022-05-04 9:44 ` [PATCH v4 2/2] arm64: dts: renesas: Add initial DTSI for RZ/V2M SoC Phil Edworthy
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=20220511150358.GA305958-robh@kernel.org \
--to=robh@kernel.org \
--cc=biju.das.jz@bp.renesas.com \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=phil.edworthy@renesas.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).