diff for duplicates of <20230808120626.bfw5hl6hzszhccsg@spectrum> diff --git a/a/1.txt b/N1/1.txt index 8b13789..c68d531 100644 --- a/a/1.txt +++ b/N1/1.txt @@ -1 +1,52 @@ +On 23:45-20230807, Hari Nagalla wrote: +> The following series introduces K3 M4F remoteproc driver support for +> AM64x and AM62x SoC families. These SoCs have a ARM Cortex M4F core in +> the MCU voltage domain. For safety oriented applications, this core is +> operated independently with out any IPC to other cores on the SoC. +> However, for non safety applications, some customers use it as a remote +> processor and so linux remote proc support is extended to the M4F core. +> +> See AM64x Technical Reference Manual (SPRUIM2C – SEPTEMBER 2021) for +> further details: https://www.ti.com/lit/pdf/SPRUIM2 +> +> Hari Nagalla (3): +> dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs +> arm64: dts: ti: k3-am62 : Add M4F remote proc node +> arm64: dts: ti: k3-am64 : Add M4F remote proc node +> +> Martyn Welch (2): +> remoteproc: k3: Split out functions common with M4 driver +> remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem +> +> .../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 136 ++++ +> arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 12 + +> .../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 19 + +> arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi | 12 + +> arch/arm64/boot/dts/ti/k3-am642-evm.dts | 18 + +> arch/arm64/boot/dts/ti/k3-am642-sk.dts | 18 + +> drivers/remoteproc/Kconfig | 13 + +> drivers/remoteproc/Makefile | 3 +- +> drivers/remoteproc/ti_k3_common.c | 513 +++++++++++++++ +> drivers/remoteproc/ti_k3_common.h | 108 ++++ +> drivers/remoteproc/ti_k3_dsp_remoteproc.c | 598 +----------------- +> drivers/remoteproc/ti_k3_m4_remoteproc.c | 333 ++++++++++ +> 12 files changed, 1213 insertions(+), 570 deletions(-) +> create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml +> create mode 100644 drivers/remoteproc/ti_k3_common.c +> create mode 100644 drivers/remoteproc/ti_k3_common.h +> create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c +Please keep the device tree seperate from driver changes. +ordering of patches should be: +a) binding +b) driver updates +c) mark device tree changes in the same series (if you are posting) as +"DONOTMERGE" to help driver maintainers understand that the dts come in +via SoC tree (most maintainers do not need this, but it keeps things +sane and adjust your expectation that this will hit the same window as +the driver changes). + +-- +Regards, +Nishanth Menon +Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D diff --git a/a/content_digest b/N1/content_digest index 67a2452..ba22ab5 100644 --- a/a/content_digest +++ b/N1/content_digest @@ -18,5 +18,57 @@ " <devicetree@vger.kernel.org>\0" "\00:1\0" "b\0" + "On 23:45-20230807, Hari Nagalla wrote:\n" + "> The following series introduces K3 M4F remoteproc driver support for\n" + "> AM64x and AM62x SoC families. These SoCs have a ARM Cortex M4F core in\n" + "> the MCU voltage domain. For safety oriented applications, this core is\n" + "> operated independently with out any IPC to other cores on the SoC.\n" + "> However, for non safety applications, some customers use it as a remote\n" + "> processor and so linux remote proc support is extended to the M4F core.\n" + "> \n" + "> See AM64x Technical Reference Manual (SPRUIM2C \342\200\223 SEPTEMBER 2021) for\n" + "> further details: https://www.ti.com/lit/pdf/SPRUIM2\n" + "> \n" + "> Hari Nagalla (3):\n" + "> dt-bindings: remoteproc: k3-m4f: Add K3 AM64x SoCs\n" + "> arm64: dts: ti: k3-am62 : Add M4F remote proc node\n" + "> arm64: dts: ti: k3-am64 : Add M4F remote proc node\n" + "> \n" + "> Martyn Welch (2):\n" + "> remoteproc: k3: Split out functions common with M4 driver\n" + "> remoteproc: k3-m4: Add a remoteproc driver for M4F subsystem\n" + "> \n" + "> .../bindings/remoteproc/ti,k3-m4f-rproc.yaml | 136 ++++\n" + "> arch/arm64/boot/dts/ti/k3-am62-mcu.dtsi | 12 +\n" + "> .../arm64/boot/dts/ti/k3-am62x-sk-common.dtsi | 19 +\n" + "> arch/arm64/boot/dts/ti/k3-am64-mcu.dtsi | 12 +\n" + "> arch/arm64/boot/dts/ti/k3-am642-evm.dts | 18 +\n" + "> arch/arm64/boot/dts/ti/k3-am642-sk.dts | 18 +\n" + "> drivers/remoteproc/Kconfig | 13 +\n" + "> drivers/remoteproc/Makefile | 3 +-\n" + "> drivers/remoteproc/ti_k3_common.c | 513 +++++++++++++++\n" + "> drivers/remoteproc/ti_k3_common.h | 108 ++++\n" + "> drivers/remoteproc/ti_k3_dsp_remoteproc.c | 598 +-----------------\n" + "> drivers/remoteproc/ti_k3_m4_remoteproc.c | 333 ++++++++++\n" + "> 12 files changed, 1213 insertions(+), 570 deletions(-)\n" + "> create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-m4f-rproc.yaml\n" + "> create mode 100644 drivers/remoteproc/ti_k3_common.c\n" + "> create mode 100644 drivers/remoteproc/ti_k3_common.h\n" + "> create mode 100644 drivers/remoteproc/ti_k3_m4_remoteproc.c\n" + "\n" + "Please keep the device tree seperate from driver changes.\n" + "ordering of patches should be:\n" + "a) binding\n" + "b) driver updates\n" + "c) mark device tree changes in the same series (if you are posting) as\n" + "\"DONOTMERGE\" to help driver maintainers understand that the dts come in\n" + "via SoC tree (most maintainers do not need this, but it keeps things\n" + "sane and adjust your expectation that this will hit the same window as\n" + "the driver changes).\n" + "\n" + "-- \n" + "Regards,\n" + "Nishanth Menon\n" + Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D -7f83e57a3784ad1984ee875705125ab7e7ab2b6e7b88373d0db3521a1cbb4aec +3f328e63169290383d5d6096d7a8917c57fd5ee47bcf92eb9e941d767deca06b
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox