From: Conor Dooley <conor@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jonathan Cameron <jonathan.cameron@huawei.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Randy Dunlap <rdunlap@infradead.org>
Subject: Re: [PATCH v1 1/1] dt-bindings: cache: bt1-l2-ctl: Remove soon be unused bindings
Date: Tue, 24 Feb 2026 16:43:58 +0000 [thread overview]
Message-ID: <20260224-unfounded-blizzard-3f3adb0eecc3@spud> (raw)
In-Reply-To: <20260224152711.3615622-1-andriy.shevchenko@linux.intel.com>
[-- 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 --]
next prev parent reply other threads:[~2026-02-24 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
2026-02-25 9:26 ` Andy Shevchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260224-unfounded-blizzard-3f3adb0eecc3@spud \
--to=conor@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=devicetree@vger.kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox