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 7A888C64EC7 for ; Wed, 1 Mar 2023 12:23:38 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229897AbjCAMXh (ORCPT ); Wed, 1 Mar 2023 07:23:37 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57894 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229805AbjCAMXf (ORCPT ); Wed, 1 Mar 2023 07:23:35 -0500 X-Greylist: delayed 14990 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Wed, 01 Mar 2023 04:23:31 PST Received: from 4.mo548.mail-out.ovh.net (4.mo548.mail-out.ovh.net [188.165.42.229]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 209031EBCE for ; Wed, 1 Mar 2023 04:23:31 -0800 (PST) Received: from mxplan5.mail.ovh.net (unknown [10.109.143.25]) by mo548.mail-out.ovh.net (Postfix) with ESMTPS id 6E55B212FB; Wed, 1 Mar 2023 07:34:00 +0000 (UTC) Received: from kaod.org (37.59.142.110) by DAG4EX2.mxp5.local (172.16.2.32) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2507.21; Wed, 1 Mar 2023 08:33:59 +0100 Authentication-Results: garm.ovh; auth=pass (GARM-110S004a495a9e5-a5cd-4f60-b657-3841be6cd6d6, BA6511934B6943C3167A88A21852BB5F3FADB7F3) smtp.auth=clg@kaod.org X-OVh-ClientIp: 82.64.250.170 Message-ID: <36da41c9-2396-5dd4-7fef-c85412f23045@kaod.org> Date: Wed, 1 Mar 2023 08:33:58 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.7.2 Subject: Re: [PATCH v2 3/3] ARM: dts: aspeed: asrock: Correct firmware flash SPI clocks To: Joel Stanley , Zev Weiss CC: Andrew Jeffery , Krzysztof Kozlowski , Rob Herring , , , , , , References: <20230224000400.12226-1-zev@bewilderbeest.net> <20230224000400.12226-4-zev@bewilderbeest.net> Content-Language: en-US From: =?UTF-8?Q?C=c3=a9dric_Le_Goater?= In-Reply-To: Content-Type: text/plain; charset="UTF-8"; format=flowed Content-Transfer-Encoding: 8bit X-Originating-IP: [37.59.142.110] X-ClientProxiedBy: DAG2EX1.mxp5.local (172.16.2.11) To DAG4EX2.mxp5.local (172.16.2.32) X-Ovh-Tracer-GUID: b1580e2c-5d52-471c-b456-c19902cff7ea X-Ovh-Tracer-Id: 18439707202531920885 X-VR-SPAMSTATE: OK X-VR-SPAMSCORE: -100 X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgedvhedrudelgedguddtfecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpefkffggfgfuvfevfhfhjggtgfhisehtkeertddtfeejnecuhfhrohhmpeevrogurhhitgcunfgvucfiohgrthgvrhcuoegtlhhgsehkrghougdrohhrgheqnecuggftrfgrthhtvghrnhepffdufeeliedujeeffffhjeffiefghffhhfdvkeeijeehledvueffhfejtdehgeegnecukfhppeduvdejrddtrddtrddupdefjedrheelrddugedvrdduuddtnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehinhgvthepuddvjedrtddrtddruddpmhgrihhlfhhrohhmpeeotghlgheskhgrohgurdhorhhgqedpnhgspghrtghpthhtohepuddprhgtphhtthhopehjohgvlhesjhhmshdrihgurdgruhdpiigvvhessggvfihilhguvghrsggvvghsthdrnhgvthdprghnughrvgifsegrjhdrihgurdgruhdpkhhriiihshiithhofhdrkhhoiihlohifshhkihdoughtsehlihhnrghrohdrohhrghdprhhosghhodgutheskhgvrhhnvghlrdhorhhgpdguvghvihgtvghtrhgvvgesvhhgvghrrdhkvghrnhgvlhdrohhrghdplhhinhhugidqrghrmhdqkhgvrhhnvghlsehlihhsthhsrdhinhhfrhgruggvrggurdhorhhgpdhlihhnuhigqdgrshhpvg gvugeslhhishhtshdrohiilhgrsghsrdhorhhgpdhlihhnuhigqdhkvghrnhgvlhesvhhgvghrrdhkvghrnhgvlhdrohhrghdpohhpvghnsghmtgeslhhishhtshdrohiilhgrsghsrdhorhhgpdhsthgrsghlvgesvhhgvghrrdhkvghrnhgvlhdrohhrghdpoffvtefjohhsthepmhhoheegkedpmhhouggvpehsmhhtphhouhht Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 3/1/23 02:30, Joel Stanley wrote: > On Fri, 24 Feb 2023 at 00:04, Zev Weiss wrote: >> >> While I'm not aware of any problems that have occurred running these >> at 100 MHz, the official word from ASRock is that 50 MHz is the >> correct speed to use, so let's be safe and use that instead. > > :( > > Validated with which driver? > > Cédric, do you have any thoughts on this? Transactions on the Firmware SPI controller are usually configured at 50MHz by U-Boot and Linux to stay on the safe side, specially CE0 from which the board boots. The other SPI controllers are generally set at a higher freq : 100MHz, because the devices on these buses are not for booting the BMC, they are mostly only written to (at a default lower freq). There are some exceptions when the devices and the wiring permit higher rates. For the record, we lowered the SPI freq on the AST2400 (palmetto) because some chips would freak out once in a while at 100MHz. C. >> Signed-off-by: Zev Weiss >> Cc: stable@vger.kernel.org >> Fixes: 2b81613ce417 ("ARM: dts: aspeed: Add ASRock E3C246D4I BMC") >> Fixes: a9a3d60b937a ("ARM: dts: aspeed: Add ASRock ROMED8HM3 BMC") >> --- >> arch/arm/boot/dts/aspeed-bmc-asrock-e3c246d4i.dts | 2 +- >> arch/arm/boot/dts/aspeed-bmc-asrock-romed8hm3.dts | 2 +- >> 2 files changed, 2 insertions(+), 2 deletions(-) >> >> diff --git a/arch/arm/boot/dts/aspeed-bmc-asrock-e3c246d4i.dts b/arch/arm/boot/dts/aspeed-bmc-asrock-e3c246d4i.dts >> index 67a75aeafc2b..c4b2efbfdf56 100644 >> --- a/arch/arm/boot/dts/aspeed-bmc-asrock-e3c246d4i.dts >> +++ b/arch/arm/boot/dts/aspeed-bmc-asrock-e3c246d4i.dts >> @@ -63,7 +63,7 @@ flash@0 { >> status = "okay"; >> m25p,fast-read; >> label = "bmc"; >> - spi-max-frequency = <100000000>; /* 100 MHz */ >> + spi-max-frequency = <50000000>; /* 50 MHz */ >> #include "openbmc-flash-layout.dtsi" >> }; >> }; >> diff --git a/arch/arm/boot/dts/aspeed-bmc-asrock-romed8hm3.dts b/arch/arm/boot/dts/aspeed-bmc-asrock-romed8hm3.dts >> index 00efe1a93a69..4554abf0c7cd 100644 >> --- a/arch/arm/boot/dts/aspeed-bmc-asrock-romed8hm3.dts >> +++ b/arch/arm/boot/dts/aspeed-bmc-asrock-romed8hm3.dts >> @@ -51,7 +51,7 @@ flash@0 { >> status = "okay"; >> m25p,fast-read; >> label = "bmc"; >> - spi-max-frequency = <100000000>; /* 100 MHz */ >> + spi-max-frequency = <50000000>; /* 50 MHz */ >> #include "openbmc-flash-layout-64.dtsi" >> }; >> }; >> -- >> 2.39.1.438.gdcb075ea9396.dirty >>