RE: [PATCH 1/2] dt-bindings: pinctrl: renesas: Add RZ/G2L POEG binding
From: Biju Das <biju.das.jz@bp.renesas.com>
Date: 2022-07-22 09:29:55
Also in:
linux-gpio, linux-renesas-soc
Hi Krzysztof Kozlowski, Thanks for the feedback.
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: renesas: Add RZ/G2L POEG binding On 18/07/2022 15:13, Biju Das wrote:quoted
Hi Krzysztof Kozlowski,quoted
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: renesas: Add RZ/G2L POEG binding On 15/07/2022 12:17, Biju Das wrote:quoted
Hi Krzysztof Kozlowski, Thanks for the feedback.quoted
Subject: Re: [PATCH 1/2] dt-bindings: pinctrl: renesas: Add RZ/G2L POEG binding On 13/07/2022 15:55, Biju Das wrote:quoted
Add device tree bindings for the RZ/G2L Port Output Enable for GPT(POEG).quoted
Signed-off-by: Biju Das <biju.das.jz@bp.renesas.com> --- REF->v1: * Modelled as pincontrol as most of its configuration is intended tobequoted
static. * Updated reg size in example. --- .../bindings/pinctrl/renesas,rzg2l-poeg.yaml | 65 +++++++++++++++++++ 1 file changed, 65 insertions(+) create mode 100644 Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-poeg.yaml diff --git a/Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-poeg.yam l b/Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-poeg.yam l new file mode 100644 index 000000000000..7607dd87fa68--- /dev/null +++ b/Documentation/devicetree/bindings/pinctrl/renesas,rzg2l-poeg +++ .y +++ am +++ l@@ -0,0 +1,65 @@ +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) %YAML +1.2 +--- +$id: + +title: Renesas RZ/G2L Port Output Enable for GPT (POEG) + +maintainers: + - Biju Das <biju.das.jz@bp.renesas.com> + +description: | + The output pins of the general PWM timer (GPT) can be disabled +by using + the port output enabling function for the GPT (POEG). +Specifically, + either of the following ways can be used. + * Input level detection of the GTETRGA to GTETRGD pins. + * Output-disable request from the GPT.Shouldn't this all be part of GPT? Is this a real separate device in the SoC?No, It is separate IP block, having its own register block, interruptsand resets.quoted
Please see RFC discussion here[1] [1]quoted
quoted
+ * Register settings.This is confusing... so you can use POEG to mess up registers of GPT independently, so GPT does not know it?POEG does not mess up registers of GPT. It is basically forprotection.quoted
quoted
quoted
Using POEG register, it is possible to disable GPT output without theknowledge of GPT, after configuring the Output disable source select in the GTINTAD (General PWM Timer Interrupt Output Setting Register) register present in GPT. Then what does it mean: "...following ways can be used. Register settings." I cannot parse it.Threre 3 methods mentioned in chapter 19.3 of RZ/G2L HW manual forOutput-Disable Control Operation.quoted
"Register settings" referred to the 3rd method as mentioned below. 19.3 Output-Disable Control Operation The output of the GTIOCxA and GTIOCxB pins can be disabled when any ofthe following conditions are satisfied.quoted
1) Input level or edge detection of the GTETRGn pins When POEGGn.PIDE is 1, the POEGGn.PIDF flag is set to 1. 2) Output-disable request from the GPT When POEGGn.IOCE is 1, the POEGGn.IOCF flag is set to 1. The output-disable requests enabled by GRPDTE, GRPABH, and GRPABL bits of the GTINTAD register in the GPT are applied to the group selectedby GRP[1:0] bits of the GTINTAD register.quoted
3) SSF bit setting When POEGGn.SSF is set to 1. The state of the GTIOCxA and the GTIOCxB pins when the output isdisabled is controlled by the GPT module.quoted
Please let me know if you need any info.Yes, more info is needed in your patch. The "...following ways can be used. (...) Register settings." does not explain anything.
Ok will update bindings with POEGGn.SSF in "Register settings" section to make it clear. Cheers, Biju