Message ID | 20221117105249.115649-1-tudor.ambarus@microchip.com |
---|---|
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:adf:f944:0:0:0:0:0 with SMTP id q4csp331214wrr; Thu, 17 Nov 2022 02:54:41 -0800 (PST) X-Google-Smtp-Source: AA0mqf4fatl4fYVpcpxsvgkHVeBQKLQ86/QCQKjT7p+jFItQBOKLR3o7wKx5EHkMGl2oTTjPqr98 X-Received: by 2002:a05:6a00:d59:b0:56e:5bcd:d025 with SMTP id n25-20020a056a000d5900b0056e5bcdd025mr2316029pfv.65.1668682481579; Thu, 17 Nov 2022 02:54:41 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1668682481; cv=none; d=google.com; s=arc-20160816; b=lU/oMfvIkdWgVvItTx3KxiJ3rJp8wIYpO1Unm0EkYcg8nrHBgCT5fJkNSJCerGvLXG voku94siLpvCpJyavbPenohoHsztYM6CPMGtlBZqM6ObRnCdYMmY4D4+zMItGWeT1hib V+eW2FcTAJTYeGDKgA51p4RpAT3SHrcoIZ5FIiuXH6W6QSB++SMyoYMxPD1QLZjM3wmK dIQEc94dvqY95GQ9iTKtW//dQ8VfdK7q+BJ1NHTEFxE2NJmlWunokF5rbT+2mXQdCs3Y tLeX4FItICeaMpuXHtoYOgUWqc1h7Hy53rRAvX0HOr91MbOR+rbHyFA6VhN3haZKzahb 0Mpw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=uOtV/C9x5SCxECGvEiBQ1GNOMs0zOrDdnyOSIax6th8=; b=kzChCYmf7lAan4B8e2a3uqQYu6yDcAPfJA29h9eQaEYHRfn+4I6hbZoZr00CDL3U1e my6Xm9yMaJ5z8q2Lucc0azBqx1N9QAhKgiPGJkTJ/GFSv4e8elJf8huve+u4CTImzPMa 3vnCE7XVyDdmaBFTGEk1LkD8JA0w/t8lTobVUx/BC0GpIqaWOcYLy3XkpQiHUmJktdg+ eIbuWsTLJnVCUyFFy1ILmJGHszG+snFTg6W5wEspodNS5RbiNoWAz5+Rujs3fZluNMEh 0FjXqze9/NKXPpihgBuRLT+e1GA4NFq64P0yzCcCYGU03WIqJ8a1bP3fph1xuEwo3lPV pKpA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=wc+3Uc0g; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=microchip.com Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id l9-20020a170903120900b001873fc89846si758398plh.345.2022.11.17.02.54.28; Thu, 17 Nov 2022 02:54:41 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@microchip.com header.s=mchp header.b=wc+3Uc0g; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=QUARANTINE dis=NONE) header.from=microchip.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239634AbiKQKxn (ORCPT <rfc822;just.gull.subs@gmail.com> + 99 others); Thu, 17 Nov 2022 05:53:43 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41986 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232825AbiKQKxG (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Thu, 17 Nov 2022 05:53:06 -0500 Received: from esa.microchip.iphmx.com (esa.microchip.iphmx.com [68.232.154.123]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D4A8C5ADF7; Thu, 17 Nov 2022 02:52:57 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=microchip.com; i=@microchip.com; q=dns/txt; s=mchp; t=1668682379; x=1700218379; h=from:to:cc:subject:date:message-id:mime-version: content-transfer-encoding; bh=PgRUd/gJcLJbdlYAmpEJ7HzosgEa1Fgc6gekCvI/uMM=; b=wc+3Uc0gmuAMn5+RMaPo8J904atdsKv6pGcG5W7gHfmXXVBla4cLO7ww knd6AyHAk+1dUTfR5ZAjU9bv7EowKygpJCpAEld9w85l/OioasazE3N73 tG3OoO15DZoh2qYfp+JzdBRRYLhDBu1p5avSDHEfKgV/mjyDlm3ecfOck 7eerUdGWZ1VGtuqd4qXO5aTwhMpRy253nGkPy1MomAXdnLbcXBFcy2t7U hty7LtrohVgh2fv6+U4cCsXJMoMnzpqUxqT0cotV2u8SYDL7KOLXTKKmj PZcIVBNSPHEeHOjnmmpdigwc/QjLkVJZSUhJTWIRd7RF7CtTZt080ih+n A==; X-IronPort-AV: E=Sophos;i="5.96,171,1665471600"; d="scan'208";a="183965587" Received: from unknown (HELO email.microchip.com) ([170.129.1.10]) by esa4.microchip.iphmx.com with ESMTP/TLS/AES256-SHA256; 17 Nov 2022 03:52:58 -0700 Received: from chn-vm-ex02.mchp-main.com (10.10.85.144) by chn-vm-ex03.mchp-main.com (10.10.85.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.12; Thu, 17 Nov 2022 03:52:53 -0700 Received: from ROB-ULT-M18064N.mchp-main.com (10.10.115.15) by chn-vm-ex02.mchp-main.com (10.10.85.144) with Microsoft SMTP Server id 15.1.2507.12 via Frontend Transport; Thu, 17 Nov 2022 03:52:50 -0700 From: Tudor Ambarus <tudor.ambarus@microchip.com> To: <broonie@kernel.org>, <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>, <nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>, <claudiu.beznea@microchip.com> CC: <linux-spi@vger.kernel.org>, <devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>, <linux-arm-kernel@lists.infradead.org>, <linux-mtd@lists.infradead.org>, Tudor Ambarus <tudor.ambarus@microchip.com> Subject: [PATCH 0/8] spi: Introduce spi-cs-setup-ns dt property Date: Thu, 17 Nov 2022 12:52:41 +0200 Message-ID: <20221117105249.115649-1-tudor.ambarus@microchip.com> X-Mailer: git-send-email 2.25.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Content-Type: text/plain X-Spam-Status: No, score=-4.4 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_MED, SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1749740401788875618?= X-GMAIL-MSGID: =?utf-8?q?1749740401788875618?= |
Series |
spi: Introduce spi-cs-setup-ns dt property
|
|
Message
Tudor Ambarus
Nov. 17, 2022, 10:52 a.m. UTC
SPI NOR flashes have specific cs-setup time requirements without which they can't work at frequencies close to their maximum supported frequency, as they miss the first bits of the instruction command. Unrecognized commands are ignored, thus the flash will be unresponsive. Introduce the spi-cs-setup-ns property to allow spi devices to specify their cs setup time. Tudor Ambarus (8): spi: dt-bindings: Introduce spi-cs-setup-ns property spi: Introduce spi-cs-setup-ns property spi: Reintroduce spi_set_cs_timing() spi: atmel-quadspi: Add support for configuring CS timing ARM: dts: at91-sama5d27_wlsom1: Set sst26vf064b SPI NOR flash at its maximum frequency ARM: dts: at91-sama5d27_som1: Set sst26vf064b SPI NOR flash at its maximum frequency ARM: dts: at91: sama5d2_icp: Set sst26vf064b SPI NOR flash at its maximum frequency ARM: dts: at91: sam9x60ek: Set sst26vf064b SPI NOR flash at its maximum frequency .../bindings/spi/spi-peripheral-props.yaml | 5 +++ arch/arm/boot/dts/at91-sam9x60ek.dts | 3 +- arch/arm/boot/dts/at91-sama5d27_som1.dtsi | 3 +- arch/arm/boot/dts/at91-sama5d27_wlsom1.dtsi | 3 +- arch/arm/boot/dts/at91-sama5d2_icp.dts | 3 +- drivers/spi/atmel-quadspi.c | 34 +++++++++++++++ drivers/spi/spi.c | 43 +++++++++++++++++++ 7 files changed, 90 insertions(+), 4 deletions(-)
Comments
On Thu, 17 Nov 2022 12:52:41 +0200, Tudor Ambarus wrote: > SPI NOR flashes have specific cs-setup time requirements without which > they can't work at frequencies close to their maximum supported frequency, > as they miss the first bits of the instruction command. Unrecognized > commands are ignored, thus the flash will be unresponsive. Introduce the > spi-cs-setup-ns property to allow spi devices to specify their cs setup > time. > > [...] Applied to broonie/spi.git for-next Thanks! [1/8] spi: dt-bindings: Introduce spi-cs-setup-ns property commit: f6c911f3308c1cfb97ae1da6654080d7104e2df2 [2/8] spi: Introduce spi-cs-setup-ns property commit: 33a2fde5f77bd744b8bd0c694bc173cc968e55a5 [3/8] spi: Reintroduce spi_set_cs_timing() commit: 684a47847ae639689e7b823251975348a8e5434f [4/8] spi: atmel-quadspi: Add support for configuring CS timing commit: f732646d0ccd22f42ed7de5e59c0abb7a848e034 All being well this means that it will be integrated into the linux-next tree (usually sometime in the next 24 hours) and sent to Linus during the next merge window (or sooner if it is a bug fix), however if problems are discovered then the patch may be dropped or reverted. You may get further e-mails resulting from automated or manual testing and review of the tree, please engage with people reporting problems and send followup patches addressing any issues that are reported if needed. If any updates are required or you are submitting further changes they should be sent as incremental updates against current git, existing patches will not be replaced. Please add any relevant lists and maintainers to the CCs when replying to this mail. Thanks, Mark