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 87915C636CC for ; Thu, 16 Feb 2023 09:04:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229810AbjBPJET (ORCPT ); Thu, 16 Feb 2023 04:04:19 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48584 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229739AbjBPJEP (ORCPT ); Thu, 16 Feb 2023 04:04:15 -0500 Received: from soltyk.jannau.net (soltyk.jannau.net [144.76.91.90]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ED13121A2D; Thu, 16 Feb 2023 01:04:12 -0800 (PST) Received: by soltyk.jannau.net (Postfix, from userid 1000) id 295AE26F7A6; Thu, 16 Feb 2023 10:04:11 +0100 (CET) Date: Thu, 16 Feb 2023 10:04:11 +0100 From: Janne Grunau To: Mark Brown Cc: Rob Herring , Krzysztof Kozlowski , Tudor Ambarus , linux-spi@vger.kernel.org, devicetree@vger.kernel.org, Alyssa Rosenzweig , asahi@lists.linux.dev, linux-kernel@vger.kernel.org, Hector Martin , Kazuki Subject: Re: [PATCH v2 0/3] SPI core CS delay fixes and additions Message-ID: <20230216090411.GH17933@jannau.net> References: <20230113102309.18308-1-marcan@marcan.st> <167362544665.163457.10878671229075890152.b4-ty@kernel.org> <20230214185234.uj63aovylzixs6xa@kazuki-mac> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230214185234.uj63aovylzixs6xa@kazuki-mac> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hej Mark, On 2023-02-15 03:52:34 +0900, Kazuki wrote: > On Fri, Jan 13, 2023 at 03:57:26PM +0000, Mark Brown wrote: > > On Fri, 13 Jan 2023 19:23:07 +0900, Hector Martin wrote: > > > Commits f6c911f3308c ("spi: dt-bindings: Introduce > > > spi-cs-setup-ns property") and 33a2fde5f77b ("spi: Introduce > > > spi-cs-setup-ns property") introduced a new property to represent the > > > CS setup delay in the device tree, but they have some issues: > > > > > > - The property is only parsed as a 16-bit integer number of nanoseconds, > > > which limits the maximum value to ~65us. This is not a reasonable > > > upper limit, as some devices might need a lot more. > > > - The property name is inconsistent with other delay properties, which > > > use a "*-delay-ns" naming scheme. > > > - Only the setup delay is introduced, but not the related hold and > > > inactive delay times. > > > > > > [...] > > > > Applied to > > > > https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next > > > > Thanks! > > > > [1/3] spi: Use a 32-bit DT property for spi-cs-setup-delay-ns > > commit: f276aacf5d2f7fb57e400db44c807ea3b9525fd6 > > Shouldn't this be sent to 6.2 before the property becomes a stable ABI? can we still get "spi: Use a 32-bit DT property for spi-cs-setup-delay-ns" into 6.2? If not I can send a single line patch which switches of_property_read_u16() to of_property_read_u32() to avoid defining "spi-cs-setup-delay-ns" to u16 as stable devicetree ABI. sorry this comes so late before 6.2, we missed to track the patches. Thanks, Janne