From patchwork Mon Oct 17 09:16:21 2022 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?C=C3=A9dric_Le_Goater?= X-Patchwork-Id: 1690718 Return-Path: X-Original-To: incoming@patchwork.ozlabs.org Delivered-To: patchwork-incoming@legolas.ozlabs.org Authentication-Results: legolas.ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=lists.ozlabs.org (client-ip=2404:9400:2:0:216:3eff:fee1:b9f1; helo=lists.ozlabs.org; envelope-from=openbmc-bounces+incoming=patchwork.ozlabs.org@lists.ozlabs.org; receiver=) Received: from lists.ozlabs.org (lists.ozlabs.org [IPv6:2404:9400:2:0:216:3eff:fee1:b9f1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature ECDSA (P-384) server-digest SHA384) (No client certificate requested) by legolas.ozlabs.org (Postfix) with ESMTPS id 4MrWbG1dM7z23jp for ; Mon, 17 Oct 2022 20:16:58 +1100 (AEDT) Received: from boromir.ozlabs.org (localhost [IPv6:::1]) by lists.ozlabs.org (Postfix) with ESMTP id 4MrWbG0pPRz3c5G for ; Mon, 17 Oct 2022 20:16:58 +1100 (AEDT) X-Original-To: openbmc@lists.ozlabs.org Delivered-To: openbmc@lists.ozlabs.org Received: from gandalf.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.ozlabs.org (Postfix) with ESMTPS id 4MrWZt6gp1z2xb4; Mon, 17 Oct 2022 20:16:38 +1100 (AEDT) Received: from gandalf.ozlabs.org (mail.ozlabs.org [IPv6:2404:9400:2221:ea00::3]) by gandalf.ozlabs.org (Postfix) with ESMTP id 4MrWZr12rvz4xGl; Mon, 17 Oct 2022 20:16:36 +1100 (AEDT) Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by mail.ozlabs.org (Postfix) with ESMTPSA id 4MrWZh54s8z4wgv; Mon, 17 Oct 2022 20:16:28 +1100 (AEDT) From: =?utf-8?q?C=C3=A9dric_Le_Goater?= To: linux-spi@vger.kernel.org Subject: [PATCH linux v2 0/3] spi: aspeed: Add a "ranges" property Date: Mon, 17 Oct 2022 11:16:21 +0200 Message-Id: <20221017091624.130227-1-clg@kaod.org> X-Mailer: git-send-email 2.37.3 MIME-Version: 1.0 X-BeenThere: openbmc@lists.ozlabs.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Development list for OpenBMC List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: devicetree@vger.kernel.org, linux-aspeed@lists.ozlabs.org, Andrew Jeffery , openbmc@lists.ozlabs.org, linux-kernel@vger.kernel.org, Rob Herring , Mark Brown , Joel Stanley , Krzysztof Kozlowski , Chin-Ting Kuo , linux-arm-kernel@lists.infradead.org, =?utf-8?q?C=C3=A9dric_Le_Goater?= Errors-To: openbmc-bounces+incoming=patchwork.ozlabs.org@lists.ozlabs.org Sender: "openbmc" Hello, Currently, the Linux Aspeed SMC driver computes the decoding ranges of each CS (AHB memory window on which the flash contents are mapped) from the size of the detected flash device. It seems that some chips have issues with the computed ranges and for these, it would be nice to be able to define custom decoding ranges in the DT. Here is a little series doing that. Thanks, C. Changes in v2 : - Tested by Naresh Solanki - sent preliminary fix independently https://patchwork.kernel.org/project/linux-arm-kernel/patch/20221016155722.3520802-1-clg@kaod.org/ - changed the sysfs file exposing the register values to debugfs. - refresh on 6.1-rc1 Cédric Le Goater (3): spi: dt-bindings: aspeed: Add a ranges property spi: aspeed: Handle custom decoding ranges spi: aspeed: Introduce a "ranges" debugfs file drivers/spi/spi-aspeed-smc.c | 131 +++++++++++++++++- .../bindings/spi/aspeed,ast2600-fmc.yaml | 9 ++ 2 files changed, 138 insertions(+), 2 deletions(-)