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 B508DC5AE5B for ; Mon, 20 Nov 2023 17:49:50 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233971AbjKTRtw (ORCPT ); Mon, 20 Nov 2023 12:49:52 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50038 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234316AbjKTRtX (ORCPT ); Mon, 20 Nov 2023 12:49:23 -0500 Received: from mail11.truemail.it (mail11.truemail.it [IPv6:2001:4b7e:0:8::81]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 61669D4D; Mon, 20 Nov 2023 09:48:55 -0800 (PST) Received: from francesco-nb.int.toradex.com (93-49-2-63.ip317.fastwebnet.it [93.49.2.63]) by mail11.truemail.it (Postfix) with ESMTPA id 7D5592071A; Mon, 20 Nov 2023 18:48:53 +0100 (CET) Date: Mon, 20 Nov 2023 18:48:49 +0100 From: Francesco Dolcini To: Stefan Moring Cc: Francesco Dolcini , linux@bigler.io, Linux regressions mailing list , Mark Brown , linux-kernel@vger.kernel.org, linux-spi@vger.kernel.org Subject: Re: spi: imx: Increase imx51 ecspi burst length fails on imx6dl and imx8mm Message-ID: References: <2fcdd99eee9ee4f5d34fa1abab2f51bb@mail.infomaniak.com> <86566391db9c5044f1a082bc8ec697a2@mail.infomaniak.com> <6322fd4c1967a518310140c35ab34f65@mail.infomaniak.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 20, 2023 at 04:30:15PM +0100, Stefan Moring wrote: > Can you verify the values used for the transfer,  spi_imx->count and spi_imx-> > bits_per_word inside the mx51_ecpsi_prepare_transfer() method? Those are the > only two things that changed in the commits. Maybe compare them to the working > version? I would suggest to bisect the issue to the actual commit that introduced the regression, I do not think this was done yet. Francesco