Message ID | 20220726170725.3245278-1-mail@conchuod.ie |
---|---|
Headers | show
Return-Path: <devicetree-owner@kernel.org> 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 7D0B9C00140 for <linux-devicetree@archiver.kernel.org>; Tue, 26 Jul 2022 17:08:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230074AbiGZRIC (ORCPT <rfc822;linux-devicetree@archiver.kernel.org>); Tue, 26 Jul 2022 13:08:02 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40620 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229677AbiGZRIB (ORCPT <rfc822;devicetree@vger.kernel.org>); Tue, 26 Jul 2022 13:08:01 -0400 Received: from mail-wr1-x42b.google.com (mail-wr1-x42b.google.com [IPv6:2a00:1450:4864:20::42b]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5181C1408C for <devicetree@vger.kernel.org>; Tue, 26 Jul 2022 10:07:58 -0700 (PDT) Received: by mail-wr1-x42b.google.com with SMTP id m17so20750844wrw.7 for <devicetree@vger.kernel.org>; Tue, 26 Jul 2022 10:07:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=conchuod.ie; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=DqEbmzhKx0NMjg0VvinCoPEfypWpQp7BkQaC0Xs8ciA=; b=NhvjhaDnJnixTK5JKS13CF/cGWT95PlYz5ESq87WVqMG6WDROqjbUK6xqAdGJULCpz mZAEIbbjJbwrPzrktT3T+hs2SojuMjASB5/5RaZoK38FRiqIXI9nm4IqEXTYfpBUQxtF OPtgT59X4RnD04NW5HDTK6tYnDxxB2LsL5xk2MnnjXPyXCal1tupwafaj+/mzZ6Fj9W/ JfPOIe+myCgsz1tzJGLmJmP3pdNNjuat7gTHpEFrvR0In+IQ2op4pUbfhe/IF2sD+2gR IfxFyDXvhZ3ePvPndTkPjf9k+OU+nebEjUnlZWBsRDd2q5POSB7gmnFOjIdy0UhQpO3n T4Lw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=DqEbmzhKx0NMjg0VvinCoPEfypWpQp7BkQaC0Xs8ciA=; b=EQRlN8lX0Q2SHFMjWESxbcz4c4BHzc/FptrMnkrBRNMJdKxRGmBEMd52PtuCisXwup mthImJS52jRcYnctO2D5WqvGFXhOz+sxZmnWUlJc1LUD8WKDd7JnBupfcGhyqhpzMVGT YvygG9bSgItJlqJc6DSr+PCktpHNGWDvuBtC/8n0JiMhaI/fnIf3eHVw4shSgffBp3U5 DaFidB9EoLUy7N0bFcnsIWqPSleg5u1q8SYLxOYOhzmE73/fkq1JAIZh3ZsVxc3IsEV8 7CNUTnplbNcf9fpEYrzNrOaGAQxYR8bICWkJkLM1rKQwjh78i6F9/Cw25nIsgajlk8oG UCOg== X-Gm-Message-State: AJIora/uZ0iZ97cb8HcNvE9hVBEQQMORpFZyNyXJtM9zwjcj6tsjf4xQ 77MuGtDgJfRV/cU9zGjWcUCw/Q== X-Google-Smtp-Source: AGRyM1ujJrahHNmwiwz/mBnF/zHJW0mN4KLDNf4jcWEuw6EW0rtMpqQBl3Uq7RHHGJqWG90H0YU3xw== X-Received: by 2002:adf:e193:0:b0:21e:626c:d082 with SMTP id az19-20020adfe193000000b0021e626cd082mr11227518wrb.159.1658855276724; Tue, 26 Jul 2022 10:07:56 -0700 (PDT) Received: from henark71.. ([109.76.124.168]) by smtp.gmail.com with ESMTPSA id r17-20020a5d52d1000000b0021d68a504cbsm14859618wrv.94.2022.07.26.10.07.55 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 26 Jul 2022 10:07:55 -0700 (PDT) From: Conor Dooley <mail@conchuod.ie> To: Linus Walleij <linus.walleij@linaro.org>, Bartosz Golaszewski <brgl@bgdev.pl>, Rob Herring <robh+dt@kernel.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>, Palmer Dabbelt <palmer@dabbelt.com>, Paul Walmsley <paul.walmsley@sifive.com>, Albert Ou <aou@eecs.berkeley.edu>, Conor Dooley <conor.dooley@microchip.com>, Atul Khare <atulkhare@rivosinc.com>, Sagar Kadam <sagar.kadam@sifive.com> Cc: linux-gpio@vger.kernel.org, devicetree@vger.kernel.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org Subject: [PATCH v3 0/2] Fix SiFive dt-schema errors Date: Tue, 26 Jul 2022 18:07:24 +0100 Message-Id: <20220726170725.3245278-1-mail@conchuod.ie> X-Mailer: git-send-email 2.37.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: <devicetree.vger.kernel.org> X-Mailing-List: devicetree@vger.kernel.org |
Series |
Fix SiFive dt-schema errors
|
expand
|
From: Conor Dooley <conor.dooley@microchip.com> Hi all, As these are the last remaining dtbs_check warnings for the default riscv defconfig I am reviving the series. Atul has been hit by some hardware issues so has not had a chance to send an applicable version of these patches. All I have done here is rebase on linux-next, so by the time the merge window reopens it will hopefully apply.. On Atul's V2, Rob had a comment about changing the cache-sets in the patch 1/2: There is not any way to express power of 2, so you have to list values. Rather than just adding 1 more value, I would add at least a few more so we're not adding these one by one. This is for a specific cache implementation, so it can't really be *any* power of 2. Designs have some limits or physics does. /endquote I don't think that there's value in speculatively adding values to this enum especially as (I think at least) the scala for this cache IP has been released publicly: https://github.com/sifive/block-inclusivecache-sifive/blob/master/design/craft/inclusivecache/src/Parameters.scala#L32 The two compatibles in the file match only against two specific cache implemenations: the fu540's & the fu740's. I would seem to me that, it would be better to lock this to a single value per compatible since the 1024 applies to the fu540 & the new value of 2048 applies only to the fu740. I have not made that change, I simply wanted to repackage this series in a way that could be more easily applied & restart the discussion. Thanks, Conor. Atul Khare (2): dt-bindings: sifive: add cache-set value of 2048 dt-bindings: sifive: add gpio-line-names Documentation/devicetree/bindings/gpio/sifive,gpio.yaml | 4 ++++ Documentation/devicetree/bindings/riscv/sifive-l2-cache.yaml | 2 +- 2 files changed, 5 insertions(+), 1 deletion(-) base-commit: 058affafc65a74cf54499fb578b66ad0b18f939b