* [PATCH v1 1/1] dt-bindings: cache: bt1-l2-ctl: Remove soon be unused bindings
@ 2026-02-24 15:27 Andy Shevchenko
2026-02-24 16:43 ` Conor Dooley
0 siblings, 1 reply; 3+ messages in thread
From: Andy Shevchenko @ 2026-02-24 15:27 UTC (permalink / raw)
To: devicetree, linux-kernel
Cc: Conor Dooley, Jonathan Cameron, Rob Herring, Krzysztof Kozlowski,
Randy Dunlap, Andy Shevchenko
As stated in [1] the Baikal platforms are not supported and
the respective driver code is going to be removed. Remove
soon be unused bindings.
Link: https://lore.kernel.org/r/20260224150616.3585591-1-andriy.shevchenko@linux.intel.com [1]
Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
---
.../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
diff --git a/Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml b/Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml
deleted file mode 100644
index ec4f367bc0b4..000000000000
--- a/Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml
+++ /dev/null
@@ -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 <fancer.lancer@gmail.com>
-
-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>;
- };
-...
--
2.50.1
^ permalink raw reply related [flat|nested] 3+ messages in thread* Re: [PATCH v1 1/1] dt-bindings: cache: bt1-l2-ctl: Remove soon be unused bindings
2026-02-24 15:27 [PATCH v1 1/1] dt-bindings: cache: bt1-l2-ctl: Remove soon be unused bindings Andy Shevchenko
@ 2026-02-24 16:43 ` Conor Dooley
2026-02-25 9:26 ` Andy Shevchenko
0 siblings, 1 reply; 3+ messages in thread
From: Conor Dooley @ 2026-02-24 16:43 UTC (permalink / raw)
To: Andy Shevchenko
Cc: devicetree, linux-kernel, Jonathan Cameron, Rob Herring,
Krzysztof Kozlowski, Randy Dunlap
[-- Attachment #1: Type: text/plain, Size: 3078 bytes --]
On Tue, Feb 24, 2026 at 04:27:11PM +0100, Andy Shevchenko wrote:
> As stated in [1] the Baikal platforms are not supported and
> the respective driver code is going to be removed. Remove
> soon be unused bindings.
>
> Link: https://lore.kernel.org/r/20260224150616.3585591-1-andriy.shevchenko@linux.intel.com [1]
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
This feels like it should have been in a series with the driver removal.
If Krzysztof wants to take it with the driver to avoid warnings in his
tree:
Acked-by: Conor Dooley <conor.dooley@microchip.com>
Otherwise I'll revisit this in a day or two and grab it.
Cheers,
Conor.
> ---
> .../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
>
> diff --git a/Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml b/Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml
> deleted file mode 100644
> index ec4f367bc0b4..000000000000
> --- a/Documentation/devicetree/bindings/cache/baikal,bt1-l2-ctl.yaml
> +++ /dev/null
> @@ -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 <fancer.lancer@gmail.com>
> -
> -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>;
> - };
> -...
> --
> 2.50.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
^ permalink raw reply [flat|nested] 3+ messages in thread* Re: [PATCH v1 1/1] dt-bindings: cache: bt1-l2-ctl: Remove soon be unused bindings
2026-02-24 16:43 ` Conor Dooley
@ 2026-02-25 9:26 ` Andy Shevchenko
0 siblings, 0 replies; 3+ messages in thread
From: Andy Shevchenko @ 2026-02-25 9:26 UTC (permalink / raw)
To: Conor Dooley
Cc: devicetree, linux-kernel, Jonathan Cameron, Rob Herring,
Krzysztof Kozlowski, Randy Dunlap
On Tue, Feb 24, 2026 at 04:43:58PM +0000, Conor Dooley wrote:
> On Tue, Feb 24, 2026 at 04:27:11PM +0100, Andy Shevchenko wrote:
> > As stated in [1] the Baikal platforms are not supported and
> > the respective driver code is going to be removed. Remove
> > soon be unused bindings.
> >
> > Link: https://lore.kernel.org/r/20260224150616.3585591-1-andriy.shevchenko@linux.intel.com [1]
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> This feels like it should have been in a series with the driver removal.
Yeah, he pointed out to the DT submitting patches documentation, so now
it's clearer.
> If Krzysztof wants to take it with the driver to avoid warnings in his
> tree:
> Acked-by: Conor Dooley <conor.dooley@microchip.com>
Thanks!
> Otherwise I'll revisit this in a day or two and grab it.
It will be a v3 of the combined patches in a series.
--
With Best Regards,
Andy Shevchenko
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-02-25 9:26 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-02-24 15:27 [PATCH v1 1/1] dt-bindings: cache: bt1-l2-ctl: Remove soon be unused bindings Andy Shevchenko
2026-02-24 16:43 ` Conor Dooley
2026-02-25 9:26 ` Andy Shevchenko
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox