Received: by 2002:a05:6358:a55:b0:ec:fcf4:3ecf with SMTP id 21csp1186424rwb; Fri, 13 Jan 2023 08:59:03 -0800 (PST) X-Google-Smtp-Source: AMrXdXs0XVR4xZ/JgZYwmZVs4r5uUqiTYZaDwtlW/WMxC5IC6eT4T1c+QsPq6cHeaciK64hOJkmL X-Received: by 2002:a05:6a20:cf49:b0:b6:b9f:7e62 with SMTP id hz9-20020a056a20cf4900b000b60b9f7e62mr10568975pzb.17.1673629143483; Fri, 13 Jan 2023 08:59:03 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673629143; cv=none; d=google.com; s=arc-20160816; b=og/RwxDsxzpTtd1I3d+JOqQyFebNun2ttDtGaxpopYqEVo5skQ203gYJ03rc9qz107 bmcSqy6Qmj7NLfTgH8iBVMeWahQG7KhmAVeZsKIETItawrbDAWBNFBbtjgvaYjIuMfWL pLPLjzG8a2A/teN9WYO06MdPiepifL+1xGKcOITJzySFykk3e/HqCJK8ORoOMkbay37T RGZVnfCPOUhD/92zcOh5eNl/DaDYYWyHfCDFwrv6AbZNPiYp+sIX/jcNftuzENweNZ5u /n+gOMuItHlIKQlC/FM8Z29p0oqsMhSf5kPhGHo9PgkIrlpfJShiWBuwq4PiXcAtUi7Y KPqA== 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:date :message-id:subject:references:in-reply-to:cc:to:from:dkim-signature; bh=yOwo6yMdPriE2vJt+0y7qGGUK+GhCdxTYHge7FDjJ7w=; b=a63VbnZ79ZGvKADfazP+uSHsk0/cPmK1aZvBJrZZkecWL1X0fRCoOpM7PbceVxmk9M CdZQsX+Hido3LOvysHkuoh5q6a6cglpESs57I40Gzhwad4F9hkM9oTZdsIC/iOZxNkuy oFwsCuExP3djVi7J7QcWtF/PZnSSV/jlY1FZGjn7gnmxc3jRkn2uyhNmvnW35jZ7xCc9 iXoe/KXBF+KhuAu3+A4XrRUsrBraJMH4k5/OrpMaDkcOZ4SHATF+k6bNNxik+Rz5jC8i wPIE4QMpOIvBRypSi7+Ce6uJ9WBMsVw4fGVBcqFF1dyOtB3cJ9uwu7OfzsaaZfxg47zI Ptiw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=SO7NS2P4; 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=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id h125-20020a636c83000000b0044e12bf26ecsi21495359pgc.465.2023.01.13.08.58.57; Fri, 13 Jan 2023 08:59:03 -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=@kernel.org header.s=k20201202 header.b=SO7NS2P4; 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=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229797AbjAMQFr (ORCPT + 51 others); Fri, 13 Jan 2023 11:05:47 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53250 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230110AbjAMQFQ (ORCPT ); Fri, 13 Jan 2023 11:05:16 -0500 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E7E3421A8; Fri, 13 Jan 2023 07:57:29 -0800 (PST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id 86B7E6216E; Fri, 13 Jan 2023 15:57:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id E4ADEC433D2; Fri, 13 Jan 2023 15:57:26 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1673625449; bh=RgE8Fj7iLHFPKGSsXzQDcEmsYGxZ0rV3hVEWaEMDJr4=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=SO7NS2P4DPwFr/A1++KqO020SxXyW1XnTE9vxLY8j3xLOBS0Df9wfDocbp3xZRVEz kCphu1x3II9PfiO9B7cmpkegKuxK+ybMlSQyqVLR2zuXMGeAIBGmKvRDRQCjXyFONX wE6PFzd7SzVE7xvGI2loOIMh5c7hv8w78t7XEhPPm7tHUSxfL3Lsme6/dY6jcCt8iK o4q+qC1GsAsB36/Rx6ZGmEpt7ptRSPKGgTIYhefXLmcABSvTVCYenDcev+dr7j9VNi oBXtNqKFTD5HbZmtrioaJP8M9sj5CgIfRmTAfvz/PKISJN5L5JQxJw/b6T9Bow5nMD 2tkgJxa/kSQjg== From: Mark Brown To: Hector Martin Cc: Rob Herring , Krzysztof Kozlowski , Tudor Ambarus , linux-spi@vger.kernel.org, devicetree@vger.kernel.org, Janne Grunau , Alyssa Rosenzweig , asahi@lists.linux.dev, linux-kernel@vger.kernel.org In-Reply-To: <20230113102309.18308-1-marcan@marcan.st> References: <20230113102309.18308-1-marcan@marcan.st> Subject: Re: [PATCH v2 0/3] SPI core CS delay fixes and additions Message-Id: <167362544665.163457.10878671229075890152.b4-ty@kernel.org> Date: Fri, 13 Jan 2023 15:57:26 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.12-dev-8b3d1 X-Spam-Status: No, score=-7.1 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,RCVD_IN_DNSWL_HI, SPF_HELO_NONE,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: X-Mailing-List: linux-kernel@vger.kernel.org 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 [2/3] spi: dt-bindings: Add hold/inactive CS delay peripheral properties commit: 34f89f238c545d4fd0166e37c201d96c10443953 [3/3] spi: Parse hold/inactive CS delay values from the DT commit: 5827b31d858e399e0ba9fbd33da7a39b31769e11 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