From: Kartik <kkartik@nvidia.com>
To: <robh@kernel.org>
Cc: <akhilrajeev@nvidia.com>, <daniel.lezcano@linaro.org>,
<devicetree@vger.kernel.org>, <jonathanh@nvidia.com>,
<kkartik@nvidia.com>, <krzk+dt@kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-tegra@vger.kernel.org>,
<mkumard@nvidia.com>, <mperttunen@nvidia.com>,
<pshete@nvidia.com>, <rgumasta@nvidia.com>, <spujar@nvidia.com>,
<tglx@linutronix.de>, <thierry.reding@gmail.com>,
<vidyas@nvidia.com>
Subject: Re: [PATCH 1/6] dt-bindings: timer: Add Tegra186 & Tegra234 Timer
Date: Wed, 20 Apr 2022 18:44:57 +0530 [thread overview]
Message-ID: <1650460497-26715-1-git-send-email-kkartik@nvidia.com> (raw)
In-Reply-To: <YlhmAQsZVU92OZ3W@robh.at.kernel.org>
On 14/04/2022 18:20, Rob Herring wrote:
>> timestamp counter. The Tegra234 timer provides sixteen 29-bit timer
>> counters and one 32-bit timestamp counter. Each NV timer selects its
>> timing reference signal from the 1 MHz reference generated by USEC,
>> TSC or either clk_m or OSC. Each TMR can be programmed to generate
>> one-shot, periodic, or watchdog interrupts.
>>
>> Signed-off-by: Kartik <kkartik@nvidia.com>
>
>Full name please.
This is my legal name.
>
>> ---
>> .../bindings/timer/nvidia,tegra186-timer.yaml | 116 ++++++++++++++++++
>> 1 file changed, 116 insertions(+)
>> create mode 100644 Documentation/devicetree/bindings/timer/nvidia,tegra186-timer.yaml
>>
>> diff --git a/Documentation/devicetree/bindings/timer/nvidia,tegra186-timer.yaml b/Documentation/devicetree/bindings/timer/nvidia,tegra186-timer.yaml
>> new file mode 100644
>> index 000000000000..7841a68d19f3
>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/timer/nvidia,tegra186-timer.yaml
>> @@ -0,0 +1,116 @@
>> +# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
>> +%YAML 1.2
>> +---
>> +$id: "http://devicetree.org/schemas/timer/nvidia,tegra186-timer.yaml#"
>> +$schema: "http://devicetree.org/meta-schemas/core.yaml#"
>> +
>> +title: NVIDIA Tegra186 timer
>> +
>> +maintainers:
>> + - Thierry Reding <treding@nvidia.com>
>> +
>> +allOf:
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: nvidia,tegra186-timer
>> + then:
>> + properties:
>> + interrupts:
>> + # Either a single combined interrupt or up to 14 individual interrupts
>
>This can be part of 'description'
I will include this in the description in v2.
>
>> + minItems: 1
>> + maxItems: 10
>> + description: >
>> + A list of 10 interrupts; one per each timer channels 0 through 9.
>
>Is it 10 or 14? I'm confused.
My bad, it is 10.
>
>> +
>> + - if:
>> + properties:
>> + compatible:
>> + contains:
>> + const: nvidia,tegra234-timer
>> + then:
>> + properties:
>> + interrupts:
>> + # Either a single combined interrupt or up to 16 individual interrupts
>> + minItems: 1
>> + maxItems: 16
>> + description: >
>> + A list of 16 interrupts; one per each timer channels 0 through 15.
>> +
>> +properties:
>> + compatible:
>> + oneOf:
>> + - const: nvidia,tegra186-timer
>> + description: >
>> + The Tegra186 timer provides ten 29-bit timer counters and one 32-bit
>> + timestamp counter. Each NV timer selects its timing reference signal
>> + from the 1 MHz reference generated by USEC, TSC or either clk_m or
>> + OSC. Each TMR can be programmed to generate one-shot, periodic, or
>> + watchdog interrupts.
>> + - const: nvidia,tegra234-timer
>> + description: >
>> + The Tegra234 timer provides sixteen 29-bit timer counters and one 32-bit
>> + timestamp counter. Each NV timer selects its timing reference signal
>> + from the 1 MHz reference generated by USEC, TSC or either clk_m or
>> + OSC. Each TMR can be programmed to generate one-shot, periodic, or
>> + watchdog interrupts.
>
>Move all this description to top-level description leaving out the exact
>number of counters (as the schema defines that).
>
Do you mean it to be this way?
title: NVIDIA Tegra186 timer
maintainers:
- Thierry Reding <treding@nvidia.com>
description: >
The Tegra timer provides 29-bit timer counters and a 32-bit timestamp
counter. Each NV timer selects its timing reference signal from the 1 MHz
reference generated by USEC, TSC or either clk_m or OSC. Each TMR can be
programmed to generate one-shot, periodic, or watchdog interrupts.
properties:
compatible:
oneOf:
- const: nvidia,tegra186-timer
description: >
The Tegra186 timer provides ten 29-bit timer counters.
- const: nvidia,tegra234-timer
description: >
The Tegra234 timer provides sixteen 29-bit timer counters.
>> +
>> + reg:
>> + maxItems: 1
>> +
>> + interrupts: true
>> +
>> +required:
>> + - compatible
>> + - reg
>> + - interrupts
>> +
>> +additionalProperties: false
>> +
>> +examples:
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + timer@3010000 {
>> + compatible = "nvidia,tegra186-timer";
>> + reg = <0x03010000 0x000e0000>;
>> + interrupts = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 3 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>;
>> + status = "disabled";
>
>Drop status.
>
I will remove this in v2.
>> + };
>> +
>> + - |
>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>> + #include <dt-bindings/interrupt-controller/irq.h>
>> +
>> + timer@2080000 {
>> + compatible = "nvidia,tegra234-timer";
>> + reg = <0x02080000 0x00121000>;
>> + interrupts = <GIC_SPI 0 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 1 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 2 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 3 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 4 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 5 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 6 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 7 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 8 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 9 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 10 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 11 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 12 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 13 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 14 IRQ_TYPE_LEVEL_HIGH>,
>> + <GIC_SPI 15 IRQ_TYPE_LEVEL_HIGH>;
>> + status = "disabled";
>> + };
>> --
>> 2.17.1
>>
>>
next prev parent reply other threads:[~2022-04-20 13:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-14 8:25 [PATCH 0/6] Add watchdog timer support for Tegra186/194/234 SoCs Kartik
2022-04-14 8:25 ` [PATCH 1/6] dt-bindings: timer: Add Tegra186 & Tegra234 Timer Kartik
2022-04-14 18:20 ` Rob Herring
2022-04-20 13:14 ` Kartik [this message]
2022-04-14 8:25 ` [PATCH 2/6] clocksource: Add Tegra186 timers support Kartik
2022-04-14 8:25 ` [PATCH 3/6] clocksource/drivers/timer-tegra186: Add support for Tegra234 SoC Kartik
2022-04-14 8:25 ` [PATCH 4/6] arm64: tegra: Enable native timers on Tegra186 Kartik
2022-04-14 8:25 ` [PATCH 5/6] arm64: tegra: Enable native timers on Tegra194 Kartik
2022-04-14 8:25 ` [PATCH 6/6] arm64: tegra: Enable native timers on Tegra234 Kartik
2022-06-20 15:45 ` [PATCH 0/6] Add watchdog timer support for Tegra186/194/234 SoCs Thierry Reding
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=1650460497-26715-1-git-send-email-kkartik@nvidia.com \
--to=kkartik@nvidia.com \
--cc=akhilrajeev@nvidia.com \
--cc=daniel.lezcano@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=mkumard@nvidia.com \
--cc=mperttunen@nvidia.com \
--cc=pshete@nvidia.com \
--cc=rgumasta@nvidia.com \
--cc=robh@kernel.org \
--cc=spujar@nvidia.com \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=vidyas@nvidia.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).