[PATCH v4 0/2] interconnect: qcom: Add support for upcoming Hawi SoC

Vivek Aknurwar posted 2 patches 2 weeks, 5 days ago
.../bindings/interconnect/qcom,hawi-rpmh.yaml      |  131 ++
drivers/interconnect/qcom/Kconfig                  |    9 +
drivers/interconnect/qcom/Makefile                 |    2 +
drivers/interconnect/qcom/hawi.c                   | 2028 ++++++++++++++++++++
include/dt-bindings/interconnect/qcom,hawi-rpmh.h  |  165 ++
5 files changed, 2335 insertions(+)
[PATCH v4 0/2] interconnect: qcom: Add support for upcoming Hawi SoC
Posted by Vivek Aknurwar 2 weeks, 5 days ago
Add interconnect bindings and RPMh-based interconnect
driver support for the upcoming Qualcomm Hawi SoC.

Signed-off-by: Vivek Aknurwar <vivek.aknurwar@oss.qualcomm.com>
---
Changes in v4:
- Address review comment by adding missing SLAVE_PCIE_1 node
  and corresponding PCIe path.
- Link to v3: https://lore.kernel.org/r/20260409-icc-hawi-v3-0-851cac12a81d@oss.qualcomm.com

Changes in v3:
- Fix alignment of macros in the binding header.
- Update binding header commit summary and description to mention
  Qualcomm SoC.
- Collected missing Reviewed-bys.
- Link to v2: https://lore.kernel.org/r/20260406-icc-hawi-v2-0-6cfee87a1d25@oss.qualcomm.com

Changes in v2:
- Fix warning reported by dt_binding_check.
- Collected Acked-bys.
- Link to v1: https://lore.kernel.org/r/20260330-icc-hawi-v1-0-4b54a9e7d38c@oss.qualcomm.com

---
Vivek Aknurwar (2):
      dt-bindings: interconnect: qcom: document the RPMh NoC for Hawi SoC
      interconnect: qcom: add Hawi interconnect provider driver

 .../bindings/interconnect/qcom,hawi-rpmh.yaml      |  131 ++
 drivers/interconnect/qcom/Kconfig                  |    9 +
 drivers/interconnect/qcom/Makefile                 |    2 +
 drivers/interconnect/qcom/hawi.c                   | 2028 ++++++++++++++++++++
 include/dt-bindings/interconnect/qcom,hawi-rpmh.h  |  165 ++
 5 files changed, 2335 insertions(+)
---
base-commit: 4cd074ae20bbcc293bbbce9163abe99d68ae6ae0
change-id: 20260311-icc-hawi-d6dc165f8935

Best regards,
-- 
Vivek Aknurwar <vivek.aknurwar@oss.qualcomm.com>