From: Dipen Patel <dipenp@nvidia.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
thierry.reding@gmail.com, jonathanh@nvidia.com,
linux-kernel@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-gpio@vger.kernel.org, linus.walleij@linaro.org,
devicetree@vger.kernel.org, linux-doc@vger.kernel.org,
robh+dt@kernel.org, timestamp@lists.linux.dev
Subject: Re: [PATCH V2 4/6] dt-bindings: timestamp: Add Tegra234 support
Date: Wed, 8 Mar 2023 10:45:24 -0800 [thread overview]
Message-ID: <7a8027c9-dc73-3684-c5f2-3071f315b3cd@nvidia.com> (raw)
In-Reply-To: <3c0ad963-ce69-bd5b-20cd-888e5fbdecaf@kernel.org>
On 2/16/23 6:17 AM, Krzysztof Kozlowski wrote:
> On 14/02/2023 12:55, Dipen Patel wrote:
>> Added timestamp provider support for the Tegra234 in devicetree
>> bindings.
>
> 1. Your commit does much more. You need to explain it why you drop some
> property.
ACK, will address it next patch
>
> 2. Bindings go before its usage (in the patchset).
Ack...
>
> 3. Please use scripts/get_maintainers.pl to get a list of necessary
> people and lists to CC. It might happen, that command when run on an
> older kernel, gives you outdated entries. Therefore please be sure you
> base your patches on recent Linux kernel.
It is based on recent linux at the time patch series was sent...
>
>
>>
>> Signed-off-by: Dipen Patel <dipenp@nvidia.com>
>> ---
>> v2:
>> - Removed nvidia,slices property
>> - Added nvidia,gpio-controller based on review comments from Thierry,
>> this will help simplify the hte provider driver.
>>
>> .../timestamp/nvidia,tegra194-hte.yaml | 30 ++++++++++++-------
>> 1 file changed, 19 insertions(+), 11 deletions(-)
>>
>> diff --git a/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml b/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
>> index c31e207d1652..d0f4ed75baee 100644
>> --- a/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
>> +++ b/Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
>> @@ -4,7 +4,7 @@
>> $id: http://devicetree.org/schemas/timestamp/nvidia,tegra194-hte.yaml#
>> $schema: http://devicetree.org/meta-schemas/core.yaml#
>>
>> -title: Tegra194 on chip generic hardware timestamping engine (HTE)
>> +title: Tegra on chip generic hardware timestamping engine (HTE) provider
>>
>> maintainers:
>> - Dipen Patel <dipenp@nvidia.com>
>> @@ -23,6 +23,8 @@ properties:
>> enum:
>> - nvidia,tegra194-gte-aon
>> - nvidia,tegra194-gte-lic
>> + - nvidia,tegra234-gte-aon
>> + - nvidia,tegra234-gte-lic
>>
>> reg:
>> maxItems: 1
>> @@ -38,14 +40,11 @@ properties:
>> minimum: 1
>> maximum: 256
>>
>> - nvidia,slices:
>> - $ref: /schemas/types.yaml#/definitions/uint32
>> + nvidia,gpio-controller:
>> + $ref: /schemas/types.yaml#/definitions/phandle
>> description:
>> - HTE lines are arranged in 32 bit slice where each bit represents different
>> - line/signal that it can enable/configure for the timestamp. It is u32
>> - property and depends on the HTE instance in the chip. The value 3 is for
>> - GPIO GTE and 11 for IRQ GTE.
>> - enum: [3, 11]
>> + The phandle to AON gpio controller instance. This is required to handle
>> + namespace conversion between GPIO and GTE.
>>
>> '#timestamp-cells':
>> description:
>> @@ -55,11 +54,21 @@ properties:
>> mentioned in the nvidia GPIO device tree binding document.
>> const: 1
>>
>> +if:
>
> Keep it under allOf (so you no need to re-indent it on next if statement
> in the future) and put entire allOf after "required:".
>
Ack...
>> + properties:
>> + compatible:
>> + contains:
>> + enum:
>> + - nvidia,tegra194-gte-aon
>
> This is an ABI break. Does your driver handle it?
yes, handling patch is part of this patch series.
>
>> + - nvidia,tegra234-gte-aon
>> +then:
>> + required:
>> + - nvidia,gpio-controller
>> +
>> required:
>> - compatible
>> - reg
>> - interrupts
>> - - nvidia,slices
>> - "#timestamp-cells"
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2023-03-08 18:45 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-14 11:55 [PATCH V2 0/6] Add Tegra234 HTE support Dipen Patel
2023-02-14 11:55 ` [PATCH V2 1/6] MAINTAINERS: Add HTE/timestamp subsystem details Dipen Patel
2023-02-14 11:55 ` [PATCH V2 2/6] hte: Add Tegra234 provider Dipen Patel
2023-02-14 11:55 ` [PATCH V2 3/6] gpio: tegra186: Add Tegra234 hte support Dipen Patel
2023-02-14 11:55 ` [PATCH V2 4/6] dt-bindings: timestamp: Add Tegra234 support Dipen Patel
2023-02-16 14:17 ` Krzysztof Kozlowski
2023-03-08 18:45 ` Dipen Patel [this message]
2023-03-08 19:05 ` Krzysztof Kozlowski
2023-03-08 20:09 ` Dipen Patel
2023-03-09 6:16 ` Krzysztof Kozlowski
2023-03-09 18:49 ` Dipen Patel
2023-03-10 8:45 ` Krzysztof Kozlowski
2023-03-10 17:19 ` Dipen Patel
2023-03-10 18:08 ` Krzysztof Kozlowski
2023-02-14 11:55 ` [PATCH V2 5/6] hte: Re-phrase tegra API document Dipen Patel
2023-02-14 11:55 ` [PATCH V2 6/6] arm64: tegra: Add GTE nodes Dipen Patel
2023-02-16 14:18 ` Krzysztof Kozlowski
2023-03-08 20:13 ` Dipen Patel
2023-03-09 6:15 ` Krzysztof Kozlowski
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=7a8027c9-dc73-3684-c5f2-3071f315b3cd@nvidia.com \
--to=dipenp@nvidia.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=krzk@kernel.org \
--cc=linus.walleij@linaro.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=thierry.reding@gmail.com \
--cc=timestamp@lists.linux.dev \
/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