The kernel communicates with the E902 core through the mailbox
transport using AON firmware protocol. Add dt-bindings to document it
the dt node.
Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Signed-off-by: Michal Wilczynski <m.wilczynski@samsung.com>
---
.../bindings/firmware/thead,th1520-aon.yaml | 53 +++++++++++++++++++
MAINTAINERS | 1 +
2 files changed, 54 insertions(+)
create mode 100644 Documentation/devicetree/bindings/firmware/thead,th1520-aon.yaml
diff --git a/Documentation/devicetree/bindings/firmware/thead,th1520-aon.yaml b/Documentation/devicetree/bindings/firmware/thead,th1520-aon.yaml
new file mode 100644
index 000000000000..bbc183200400
--- /dev/null
+++ b/Documentation/devicetree/bindings/firmware/thead,th1520-aon.yaml
@@ -0,0 +1,53 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/firmware/thead,th1520-aon.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+
+title: T-HEAD TH1520 AON (Always-On) Firmware
+
+description: |
+ The Always-On (AON) subsystem in the TH1520 SoC is responsible for managing
+ low-power states, system wakeup events, and power management tasks. It is
+ designed to operate independently in a dedicated power domain, allowing it to
+ remain functional even during the SoC's deep sleep states.
+
+ At the heart of the AON subsystem is the E902, a low-power core that executes
+ firmware responsible for coordinating tasks such as power domain control,
+ clock management, and system wakeup signaling. Communication between the main
+ SoC and the AON subsystem is handled through a mailbox interface, which
+ enables message-based interactions with the AON firmware.
+
+maintainers:
+ - Michal Wilczynski <m.wilczynski@samsung.com>
+
+properties:
+ compatible:
+ const: thead,th1520-aon
+
+ mboxes:
+ maxItems: 1
+
+ mbox-names:
+ items:
+ - const: aon
+
+ "#power-domain-cells":
+ const: 1
+
+required:
+ - compatible
+ - mboxes
+ - mbox-names
+ - "#power-domain-cells"
+
+additionalProperties: false
+
+examples:
+ - |
+ aon: aon {
+ compatible = "thead,th1520-aon";
+ mboxes = <&mbox_910t 1>;
+ mbox-names = "aon";
+ #power-domain-cells = <1>;
+ };
diff --git a/MAINTAINERS b/MAINTAINERS
index 8e0736dc2ee0..46745cfe9d1f 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -20427,6 +20427,7 @@ L: linux-riscv@lists.infradead.org
S: Maintained
T: git https://github.com/pdp7/linux.git
F: Documentation/devicetree/bindings/clock/thead,th1520-clk-ap.yaml
+F: Documentation/devicetree/bindings/firmware/thead,th1520-aon.yaml
F: Documentation/devicetree/bindings/mailbox/thead,th1520-mbox.yaml
F: Documentation/devicetree/bindings/net/thead,th1520-gmac.yaml
F: Documentation/devicetree/bindings/pinctrl/thead,th1520-pinctrl.yaml
--
2.34.1On 03/03/2025 15:58, Michal Wilczynski wrote: > The kernel communicates with the E902 core through the mailbox > transport using AON firmware protocol. Add dt-bindings to document it > the dt node. > > Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> How is this possible? That's v1 and I never review outside of mailing list. > Signed-off-by: Michal Wilczynski <m.wilczynski@samsung.com> > --- > .../bindings/firmware/thead,th1520-aon.yaml | 53 +++++++++++++++++++ > MAINTAINERS | 1 + Best regards, Krzysztof
On 03/03/2025 18:42, Krzysztof Kozlowski wrote: > On 03/03/2025 15:58, Michal Wilczynski wrote: >> The kernel communicates with the E902 core through the mailbox >> transport using AON firmware protocol. Add dt-bindings to document it >> the dt node. >> >> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> > > > How is this possible? That's v1 and I never review outside of mailing list. > OK, I found v5: https://lore.kernel.org/all/20250219140239.1378758-4-m.wilczynski@samsung.com/ so is this the same? Best regards, Krzysztof
On 3/3/25 18:46, Krzysztof Kozlowski wrote: > On 03/03/2025 18:42, Krzysztof Kozlowski wrote: >> On 03/03/2025 15:58, Michal Wilczynski wrote: >>> The kernel communicates with the E902 core through the mailbox >>> transport using AON firmware protocol. Add dt-bindings to document it >>> the dt node. >>> >>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >> >> >> How is this possible? That's v1 and I never review outside of mailing list. >> > OK, I found v5: > https://lore.kernel.org/all/20250219140239.1378758-4-m.wilczynski@samsung.com/ > > so is this the same? Yeah, I thought by splitting the patchset and creating new sub-series I should start versioning from v1 again, and leave that bigger patchset as a reference, I've linked it in each cover letter for each sub-series. > > Best regards, > Krzysztof >
On 04/03/2025 08:43, Michal Wilczynski wrote: > > > On 3/3/25 18:46, Krzysztof Kozlowski wrote: >> On 03/03/2025 18:42, Krzysztof Kozlowski wrote: >>> On 03/03/2025 15:58, Michal Wilczynski wrote: >>>> The kernel communicates with the E902 core through the mailbox >>>> transport using AON firmware protocol. Add dt-bindings to document it >>>> the dt node. >>>> >>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >>> >>> >>> How is this possible? That's v1 and I never review outside of mailing list. >>> >> OK, I found v5: >> https://lore.kernel.org/all/20250219140239.1378758-4-m.wilczynski@samsung.com/ >> >> so is this the same? > > Yeah, I thought by splitting the patchset and creating new sub-series I > should start versioning from v1 again, and leave that bigger patchset as What was unclear in my "keep versioning and keep changelog"? How this can lead to "start new versioning"? > a reference, I've linked it in each cover letter for each sub-series. Best regards, Krzysztof
On 3/4/25 08:45, Krzysztof Kozlowski wrote: > On 04/03/2025 08:43, Michal Wilczynski wrote: >> >> >> On 3/3/25 18:46, Krzysztof Kozlowski wrote: >>> On 03/03/2025 18:42, Krzysztof Kozlowski wrote: >>>> On 03/03/2025 15:58, Michal Wilczynski wrote: >>>>> The kernel communicates with the E902 core through the mailbox >>>>> transport using AON firmware protocol. Add dt-bindings to document it >>>>> the dt node. >>>>> >>>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >>>> >>>> >>>> How is this possible? That's v1 and I never review outside of mailing list. >>>> >>> OK, I found v5: >>> https://lore.kernel.org/all/20250219140239.1378758-4-m.wilczynski@samsung.com/ >>> >>> so is this the same? >> >> Yeah, I thought by splitting the patchset and creating new sub-series I >> should start versioning from v1 again, and leave that bigger patchset as > > What was unclear in my "keep versioning and keep changelog"? How this > can lead to "start new versioning"? OK, my bad misunderstood you. I don't want to spam too much so maybe I should wait if there will be any comments before re-sending with the proper changelog and version. > >> a reference, I've linked it in each cover letter for each sub-series. > > Best regards, > Krzysztof >
On 04/03/2025 08:52, Michal Wilczynski wrote: > > > On 3/4/25 08:45, Krzysztof Kozlowski wrote: >> On 04/03/2025 08:43, Michal Wilczynski wrote: >>> >>> >>> On 3/3/25 18:46, Krzysztof Kozlowski wrote: >>>> On 03/03/2025 18:42, Krzysztof Kozlowski wrote: >>>>> On 03/03/2025 15:58, Michal Wilczynski wrote: >>>>>> The kernel communicates with the E902 core through the mailbox >>>>>> transport using AON firmware protocol. Add dt-bindings to document it >>>>>> the dt node. >>>>>> >>>>>> Reviewed-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org> >>>>> >>>>> >>>>> How is this possible? That's v1 and I never review outside of mailing list. >>>>> >>>> OK, I found v5: >>>> https://lore.kernel.org/all/20250219140239.1378758-4-m.wilczynski@samsung.com/ >>>> >>>> so is this the same? >>> >>> Yeah, I thought by splitting the patchset and creating new sub-series I >>> should start versioning from v1 again, and leave that bigger patchset as >> >> What was unclear in my "keep versioning and keep changelog"? How this >> can lead to "start new versioning"? > > OK, my bad misunderstood you. I don't want to spam too much so maybe I > should wait if there will be any comments before re-sending with the proper > changelog and version. Just provide changelog as response to your cover letter. Best regards, Krzysztof
© 2016 - 2026 Red Hat, Inc.