From patchwork Wed Jun 8 23:39:31 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Atul Khare X-Patchwork-Id: 580061 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5732FCCA480 for ; Wed, 8 Jun 2022 23:40:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233902AbiFHXj7 (ORCPT ); Wed, 8 Jun 2022 19:39:59 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33282 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233836AbiFHXj5 (ORCPT ); Wed, 8 Jun 2022 19:39:57 -0400 Received: from mail-qk1-x72f.google.com (mail-qk1-x72f.google.com [IPv6:2607:f8b0:4864:20::72f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id A5E1816A276 for ; Wed, 8 Jun 2022 16:39:43 -0700 (PDT) Received: by mail-qk1-x72f.google.com with SMTP id o73so11716003qke.7 for ; Wed, 08 Jun 2022 16:39:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rivosinc-com.20210112.gappssmtp.com; s=20210112; h=mime-version:from:date:message-id:subject:to:cc; bh=4bA3l8NMW5sqINO1r/1lERkOkDyuT51+2Y6gy5uYSqQ=; b=mXaDkRe8akpJUduhvftHXEgn4sTGP0eEV2OaV+blJVeqoLJU1FEsR+FaDtaokIeTFo 2lK9ZQ4Btqss0RkOkxW3x432KfPG90WprbHJVWggfQXq/JRB2Eq9KakDyq54PxapLUsb hc6YdA++zF2yvpOYXxd4kGmXlP5tGj74azeYSpCXzSP0+1Vit7dY6IoOTH7fSQqlIj1s yee9YeuMp2V1s6EzXiZugIO5erzHwONKUBaKeFuAOfghBQjn4RHqP8EMP8KRQjpuqLhj j/JyfzkL+nHfEYgjqoadJF0gmOwtxWmOPdx8NHbKw5rZr5qqyAIjW29A8Wlv2ZY5Mo2g 8Bzg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=4bA3l8NMW5sqINO1r/1lERkOkDyuT51+2Y6gy5uYSqQ=; b=NrQCG75q5SCnu5hsxaUKYj2FjMouJT3H+7inL7aBAgJv0+6VvMBRS5hBqTUs6cFO+U 8ScP/qUrp4WqeQ8xXmL3Kud9pUGx1UVR+FcMXx0B30xSoOp0J0M5G1GK2rN7h2qgxx8u jCzcsM2rNUbBKSs3WK3GvfwatsufwjQnkmENyDphmhgy2Hj6NC3IIiGo3J6La7lwxQ0Q OLVuwoCJwA2bsYLVk2+LT3H6U/GTjYaazdDASMg3BNbk/9DQWQuq+TCQrioNh4ZwiTau ATJAN5Q4rFZd5QHkPhxvEIHZOHXXoJOrtr6GyhRb76Kis35VUZjN61gKHV6ETH6IKYPz iOAg== X-Gm-Message-State: AOAM530NkI7I0mQA/xsaQ2qRsZmn/wYsN0QN6JhFZx7Ds0dTlCqEQWjN dL/0itaNuc9hMFxE3K7+/jKIxRPyNqDODDQuTAdo+g== X-Google-Smtp-Source: ABdhPJwxVJsLtov+PvfiuEXEacNmD+Ogc8ArgM4bwUX+jOqXRNefAAAkqXzWVsoVgFJ+AB4KhEa/eKHzBy+/FzxL2p0= X-Received: by 2002:a37:9b09:0:b0:6a6:b23e:8534 with SMTP id d9-20020a379b09000000b006a6b23e8534mr14825420qke.214.1654731582051; Wed, 08 Jun 2022 16:39:42 -0700 (PDT) MIME-Version: 1.0 From: Atul Khare Date: Wed, 8 Jun 2022 16:39:31 -0700 Message-ID: Subject: [PATCH v2 1/2] dt-bindings: sifive: add cache-set value of 2048 To: Palmer Dabbelt , Conor Dooley , Atul Khare Cc: linux-i2c@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mmc@vger.kernel.org, linux-riscv@lists.infradead.org, Rob Herring Precedence: bulk List-ID: X-Mailing-List: linux-i2c@vger.kernel.org Fixes Running device tree schema validation error messages like '... cache-sets:0:0: 1024 was expected'. The existing bindings had a single enumerated value of 1024, which trips up the dt-schema checks. The ISA permits any arbitrary power of two for the cache-sets value, but we decided to add the single additional value of 2048 because we couldn't spot an obvious way to express the constraint in the schema. Signed-off-by: Atul Khare --- Changes since v1 [1]: Rebased on latest version [1]: https://tinyurl.com/yvdvmsjd --- --- Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) const: 2097152 -- 2.34.1 diff --git a/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml b/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml index e2d330bd4608..309517b78e84 100644 --- a/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml +++ b/Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml @@ -46,7 +46,9 @@ properties: const: 2 cache-sets: - const: 1024 + # Note: Technically this can be any power of 2, but we didn't see an obvious way + # to express the constraint in Yaml + enum: [1024, 2048] cache-size: