Skip to contentSkip to conversation

dt-bindings: Renamed hte directory to timestamp

PATCH In review Dipen Patel 4 participants 5 messages May 12, 2022 – May 23, 2022

Subsystems (3)
lore
Share & tools
lore

Dipen Patel

author maintainer
#0 lore raw

PATCH 1/1 dt-bindings: Renamed hte directory to timestamp

Renamed hte dt binding directory to timestamp according review comment. Addressed minor comment about having HTE acronym first in the common dt binding document.

The change reflects above renaming in MAINTAINERS files too.

---
This patch is on top of old series (Intro to Hardware timestamping engine V6) present in linux-next tentatively in preparation for merge.

 .../{hte => timestamp}/hardware-timestamps-common.yaml      | 6 +++---
 .../bindings/{hte => timestamp}/hte-consumer.yaml           | 0
 .../bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml    | 0
 MAINTAINERS                                                 | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hardware-timestamps-common.yaml (71%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hte-consumer.yaml (100%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml (100%)
Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml renamed from Documentation/devicetree/bindings/hte/hardware-timestamps-common.yaml +3 -3
similarity index 71%
rename from Documentation/devicetree/bindings/hte/hardware-timestamps-common.yaml
rename to Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml
index 3e26de605f08..4c25ba248a72 100644
@@ -10,9 +10,9 @@ maintainers:
   - Dipen Patel <[email protected]>
 
 description:
-  Some devices/SoCs have hardware time stamping engines which can use hardware
-  means to timestamp entity in realtime. The entity could be anything from
-  GPIOs, IRQs, Bus and so on. The hardware timestamp engine (HTE) present
+  Some devices/SoCs have hardware timestamp engines (HTE) which can use
+  hardware means to timestamp entity in realtime. The entity could be anything
+  from GPIOs, IRQs, Bus and so on. The hardware timestamp engine present
   itself as a provider with the bindings described in this document.
 
 properties:
Documentation/devicetree/bindings/timestamp/hte-consumer.yaml renamed from Documentation/devicetree/bindings/hte/hte-consumer.yaml +0 -0
similarity index 100%
rename from Documentation/devicetree/bindings/hte/hte-consumer.yaml
rename to Documentation/devicetree/bindings/timestamp/hte-consumer.yaml
Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml renamed from Documentation/devicetree/bindings/hte/nvidia,tegra194-hte.yaml +0 -0
similarity index 100%
rename from Documentation/devicetree/bindings/hte/nvidia,tegra194-hte.yaml
rename to Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml
MAINTAINERS +1 -1
index 4e1e6dbb1ad8..74a61ea4beef 100644
@@ -9057,7 +9057,7 @@ F:	drivers/input/touchscreen/htcpen.c
 HTE SUBSYSTEM
 M:	Dipen Patel <[email protected]>
 S:	Maintained
-F:	Documentation/devicetree/bindings/hte/
+F:	Documentation/devicetree/bindings/timestamp/
 F:	Documentation/hte/
 F:	drivers/hte/
 F:	include/linux/hte.h

base-commit: 6107040c99d5dfc920721c198d45ed2d639b113a

Signature · 1 line
2.17.1
Reviewed-by on v1 1/1
#1 lore raw
Quoted 11 lines · Dipen Patel

Renamed hte dt binding directory to timestamp according review comment. Addressed minor comment about having HTE acronym first in the common dt binding document.

The change reflects above renaming in MAINTAINERS files too.

---
This patch is on top of old series (Intro to Hardware timestamping engine V6) present in linux-next tentatively in preparation for merge.

Yours,
Linus Walleij

maintainer Acked-by on v1 1/1
#2 lore raw
In reply to Dipen Patel
Quoted 12 lines · Dipen Patel

Renamed hte dt binding directory to timestamp according review comment. Addressed minor comment about having HTE acronym first in the common dt binding document.

The change reflects above renaming in MAINTAINERS files too.

---
This patch is on top of old series (Intro to Hardware timestamping engine V6) present in linux-next tentatively in preparation for merge.

Quoted 9 lines
 .../{hte => timestamp}/hardware-timestamps-common.yaml      | 6 +++---
 .../bindings/{hte => timestamp}/hte-consumer.yaml           | 0
 .../bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml    | 0
 MAINTAINERS                                                 | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hardware-timestamps-common.yaml (71%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hte-consumer.yaml (100%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml (100%)
#3 lore raw
Quoted 24 lines · Rob Herring
Quoted 12 lines · Dipen Patel

Renamed hte dt binding directory to timestamp according review comment. Addressed minor comment about having HTE acronym first in the common dt binding document.

The change reflects above renaming in MAINTAINERS files too.

---
This patch is on top of old series (Intro to Hardware timestamping engine V6) present in linux-next tentatively in preparation for merge.

Quoted 9 lines
 .../{hte => timestamp}/hardware-timestamps-common.yaml      | 6 +++---
 .../bindings/{hte => timestamp}/hte-consumer.yaml           | 0
 .../bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml    | 0
 MAINTAINERS                                                 | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hardware-timestamps-common.yaml (71%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hte-consumer.yaml (100%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml (100%)
Quoted 1 line

I take that back:

./Documentation/devicetree/bindings/timestamp/hte-consumer.yaml: $id:
relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/timestamp/hte-consumer.yaml#
./Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml:
$id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/timestamp/nvidia,tegra194-hte.yaml#
./Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml:
$id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/timestamp/hardware-timestamps-common.yaml#

I was wondering why a new common binding was already in next without a Reviewed-by, but I let that slide. Now I regret doing that.

Rob

author maintainer
#4 lore raw

Hi Rob,

I have just sent out the patch to fix this.

Best Regards,

Dipen Patel

Quoted 41 lines · Rob Herring
Quoted 22 lines · Rob Herring
Quoted 12 lines · Dipen Patel

Renamed hte dt binding directory to timestamp according review comment. Addressed minor comment about having HTE acronym first in the common dt binding document.

The change reflects above renaming in MAINTAINERS files too.

---
This patch is on top of old series (Intro to Hardware timestamping engine V6) present in linux-next tentatively in preparation for merge.

Quoted 9 lines
 .../{hte => timestamp}/hardware-timestamps-common.yaml      | 6 +++---
 .../bindings/{hte => timestamp}/hte-consumer.yaml           | 0
 .../bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml    | 0
 MAINTAINERS                                                 | 2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hardware-timestamps-common.yaml (71%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/hte-consumer.yaml (100%)
 rename Documentation/devicetree/bindings/{hte => timestamp}/nvidia,tegra194-hte.yaml (100%)
Quoted 1 line

I take that back:

./Documentation/devicetree/bindings/timestamp/hte-consumer.yaml: $id:
relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/timestamp/hte-consumer.yaml#
./Documentation/devicetree/bindings/timestamp/nvidia,tegra194-hte.yaml:
$id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/timestamp/nvidia,tegra194-hte.yaml#
./Documentation/devicetree/bindings/timestamp/hardware-timestamps-common.yaml:
$id: relative path/filename doesn't match actual path or filename
expected: http://devicetree.org/schemas/timestamp/hardware-timestamps-common.yaml#

I was wondering why a new common binding was already in next without a Reviewed-by, but I let that slide. Now I regret doing that.

Rob