memory: Drop Baikal SoC code and bindings
v3 cover memory: Drop Baikal SoC code and bindings
The platform is not going to be supported, remove stale code and bindings.
In v3:
- combined patches in a series (Krzysztof)
- collected tags
In v2:
- split bindings removal to a separate patch (Krzysztof)
Andy Shevchenko (2):
memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal
SoC
dt-bindings: cache: bt1-l2-ctl: Remove unused bindings
.../bindings/cache/baikal,bt1-l2-ctl.yaml | 63 ---- drivers/memory/Kconfig | 11 - drivers/memory/Makefile | 1 - drivers/memory/bt1-l2-ctl.c | 323 ------------------ 4 files changed, 398 deletions(-) delete mode 100644 Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml delete mode 100644 drivers/memory/bt1-l2-ctl.c
Signature · 1 line
2.50.1
PATCH v3 1/2 memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC
As noticed in the discussion [1] the Baikal SoC and platforms are not going to be finalized, hence remove stale code.
--- drivers/memory/Kconfig | 11 -- drivers/memory/Makefile | 1 - drivers/memory/bt1-l2-ctl.c | 323 ------------------------------------ 3 files changed, 335 deletions(-) delete mode 100644 drivers/memory/bt1-l2-ctl.c
drivers/memory/Kconfig +0 -11
@@ -64,17 +64,6 @@ config BRCMSTB_MEMC controller and specifically control the Self Refresh Power Down (SRPD) inactivity timeout. -config BT1_L2_CTL - bool "Baikal-T1 CM2 L2-RAM Cache Control Block" - depends on MIPS_BAIKAL_T1 || COMPILE_TEST - select MFD_SYSCON - help - Baikal-T1 CPU is based on the MIPS P5600 Warrior IP-core. The CPU - resides Coherency Manager v2 with embedded 1MB L2-cache. It's - possible to tune the L2 cache performance up by setting the data, - tags and way-select latencies of RAM access. This driver provides a - dt properties-based and sysfs interface for it. - config TI_AEMIF tristate "Texas Instruments AEMIF driver" depends on ARCH_DAVINCI || ARCH_KEYSTONE || COMPILE_TEST
drivers/memory/Makefile +0 -1
@@ -11,7 +11,6 @@ obj-$(CONFIG_ARM_PL172_MPMC) += pl172.o obj-$(CONFIG_ATMEL_EBI) += atmel-ebi.o obj-$(CONFIG_BRCMSTB_DPFE) += brcmstb_dpfe.o obj-$(CONFIG_BRCMSTB_MEMC) += brcmstb_memc.o -obj-$(CONFIG_BT1_L2_CTL) += bt1-l2-ctl.o obj-$(CONFIG_TI_AEMIF) += ti-aemif.o obj-$(CONFIG_TI_EMIF) += emif.o obj-$(CONFIG_OMAP_GPMC) += omap-gpmc.o
drivers/memory/bt1-l2-ctl.c deleted +0 -323
323 lines not on this page · raw message
Signature · 1 line
2.50.1
PATCH v3 2/2 dt-bindings: cache: bt1-l2-ctl: Remove unused bindings
In reply to Andy ShevchenkoAs stated in [1] the Baikal platforms are not supported and the respective driver code has just been removed. Remove unused bindings.
--- .../bindings/cache/baikal,bt1-l2-ctl.yaml | 63 ------------------- 1 file changed, 63 deletions(-) delete mode 100644 Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml
Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml deleted +0 -63
@@ -1,63 +0,0 @@ -# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause) -# Copyright (C) 2020 BAIKAL ELECTRONICS, JSC -%YAML 1.2 ---- -$id: http://devicetree.org/schemas/cache/baikal,bt1-l2-ctl.yaml# -$schema: http://devicetree.org/meta-schemas/core.yaml# - -title: Baikal-T1 L2-cache Control Block - -maintainers: - - Serge Semin <[email protected]> - -description: | - By means of the System Controller Baikal-T1 SoC exposes a few settings to - tune the MIPS P5600 CM2 L2 cache performance up. In particular it's possible - to change the Tag, Data and Way-select RAM access latencies. Baikal-T1 - L2-cache controller block is responsible for the tuning. Its DT node is - supposed to be a child of the system controller. - -properties: - compatible: - const: baikal,bt1-l2-ctl - - reg: - maxItems: 1 - - baikal,l2-ws-latency: - $ref: /schemas/types.yaml#/definitions/uint32 - description: Cycles of latency for Way-select RAM accesses - default: 0 - minimum: 0 - maximum: 3 - - baikal,l2-tag-latency: - $ref: /schemas/types.yaml#/definitions/uint32 - description: Cycles of latency for Tag RAM accesses - default: 0 - minimum: 0 - maximum: 3 - - baikal,l2-data-latency: - $ref: /schemas/types.yaml#/definitions/uint32 - description: Cycles of latency for Data RAM accesses - default: 1 - minimum: 0 - maximum: 3 - -additionalProperties: false - -required: - - compatible - -examples: - - | - l2@1f04d028 { - compatible = "baikal,bt1-l2-ctl"; - reg = <0x1f04d028 0x004>; - - baikal,l2-ws-latency = <1>; - baikal,l2-tag-latency = <1>; - baikal,l2-data-latency = <2>; - }; -...
Signature · 1 line
2.50.1
Quoted 10 lines · Andy Shevchenko
The platform is not going to be supported, remove stale code and bindings.
In v3:
- combined patches in a series (Krzysztof)
- collected tagsIn v2:
- split bindings removal to a separate patch (Krzysztof)[...]
Applied, thanks!
[1/2] memory: bt1-l2-ctl: Remove not-going-to-be-supported code for Baikal SoC
https://git.kernel.org/krzk/linux-mem-ctrl/c/d455e0f602d7e4d4ba709418009c39be48fc2149 [2/2] dt-bindings: cache: bt1-l2-ctl: Remove unused bindings https://git.kernel.org/krzk/linux-mem-ctrl/c/9983d51d1a68520ce74663920929e27b191cf43a
Best regards,
Signature · 1 line
Krzysztof Kozlowski <[email protected]>
Quoted 9 lines · Krzysztof Kozlowski
Quoted 8 lines · Andy Shevchenko
The platform is not going to be supported, remove stale code and bindings.
In v3:
- combined patches in a series (Krzysztof)
- collected tagsIn v2:
- split bindings removal to a separate patch (Krzysztof)
[...]
Quoted 1 line
Applied, thanks!
Thank you for your guidance and patience!
Signature · 2 lines
With Best Regards, Andy Shevchenko