From mboxrd@z Thu Jan 1 00:00:00 1970 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 8D778C00140 for ; Tue, 26 Jul 2022 17:35:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239396AbiGZRfa (ORCPT ); Tue, 26 Jul 2022 13:35:30 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59666 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S239386AbiGZRfa (ORCPT ); Tue, 26 Jul 2022 13:35:30 -0400 Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::235]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C49CDBF70 for ; Tue, 26 Jul 2022 10:35:28 -0700 (PDT) Received: by mail-lj1-x235.google.com with SMTP id w18so6215516lje.1 for ; Tue, 26 Jul 2022 10:35:28 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :cc:references:from:in-reply-to:content-transfer-encoding; bh=JHc7AYlRXZ6aiCtTe+oSlD5N4Ua+N3EzvkXaFf2RC4o=; b=N0deSDI+LiMOpces5+etS+NS14zNCm+md+u9gARDG0ixEpQGvSTtzErTuNz2esW0bT pXkajtBnlcabT+ZLAsxwBTnlCw0OlA5Cnt5/ohO0aXrKf0uwf5hwWi+MviSEd1CBBRjP GARs+6N9PoIAG51nVHvY68XB+6nN5SRbaAn23aBQTdq0DEDKIKgdLAY6y7p2XvQ/XosN Pd37hCg3n0SvCLNIHyOn3l0YWoYBZjVqlvxzuBK6aPAttokOg9VMKY/XelUJ/ZtuLpoj 0gVLchzNRRmyDsHubxvRY9zv5ZG+0x3LJCGdwPqzLDj1wQMo8FO3NBAQE4g3UBz085Vd cq5g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:cc:references:from:in-reply-to :content-transfer-encoding; bh=JHc7AYlRXZ6aiCtTe+oSlD5N4Ua+N3EzvkXaFf2RC4o=; b=rgNtyj+gT3ohFcejWTEy6mD5uDeYNkkXuljw2ZTK0zbMzJrI+HxaxgPjsOO6Verq7a rKJzdBs6OX/F7n0phoOMgkOc8YnBKh7oHWEsJnODX3Ai13IzWB+6cPchO6L7KJgSNr73 09qXmS/66NIjYKYa7yoLe/4Fwkc/qIibgHxzv1JA5n/xoeZd/0IbPOZZWWNBAYgDI+dr zN0h9peUOY1Icn/kzsP0QpLYDx+/5d0c2PzNk8vEr+puH9gnD5/paInnHugn8A91HkeT HuscNBfRginuAH/bSfEmfLqbUR20oLS9oi/HR1OlbgILM5lcFrSly65zIr5DYI7Ewup8 hP8w== X-Gm-Message-State: AJIora/CFL1LHA0YnrxwhUBoYfKvRecnkAAbpeNtJq/KI6BefEccbJFX j+ffCOWH0140ViXm1p6ZqRAp9w== X-Google-Smtp-Source: AGRyM1tmwXLiYKvaVFxKBF/ccqtJ5bZ4CGr5twneruJ80NjxbDQMnHuz7XCk6ts4YVIGB6Rk6qhsRA== X-Received: by 2002:a2e:a16b:0:b0:25e:8fb:a1e1 with SMTP id u11-20020a2ea16b000000b0025e08fba1e1mr3784078ljl.270.1658856927106; Tue, 26 Jul 2022 10:35:27 -0700 (PDT) Received: from [192.168.3.197] (78-26-46-173.network.trollfjord.no. [78.26.46.173]) by smtp.gmail.com with ESMTPSA id w14-20020a05651234ce00b0048a7ce3ff84sm2246967lfr.285.2022.07.26.10.35.25 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 26 Jul 2022 10:35:26 -0700 (PDT) Message-ID: <246f132a-a23d-7c53-38a7-2bcec50d65e5@linaro.org> Date: Tue, 26 Jul 2022 19:35:25 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.12.0 Subject: Re: [PATCH v3 1/2] dt-bindings: sifive: add cache-set value of 2048 Content-Language: en-US To: Conor Dooley , Linus Walleij , Bartosz Golaszewski , Rob Herring , Krzysztof Kozlowski , Palmer Dabbelt , Paul Walmsley , Albert Ou , Conor Dooley , Atul Khare , Sagar Kadam Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org References: <20220726170725.3245278-1-mail@conchuod.ie> <20220726170725.3245278-2-mail@conchuod.ie> From: Krzysztof Kozlowski In-Reply-To: <20220726170725.3245278-2-mail@conchuod.ie> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On 26/07/2022 19:07, Conor Dooley wrote: > From: Atul Khare > > 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. There is no way to express "power of two" but enum for multiple values would work. Is there a reason to limit only to 2048? Best regards, Krzysztof