Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp4859747rwd; Tue, 30 May 2023 10:55:26 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ5aSmNuby1vKkmFBQrTrfyTo08bktpHV0tIBidunK3JPEJQUHK9/Pr+MTvfFhEMKo/PBpx7 X-Received: by 2002:a17:902:ec81:b0:1ad:bb89:16f6 with SMTP id x1-20020a170902ec8100b001adbb8916f6mr3674935plg.50.1685469326148; Tue, 30 May 2023 10:55:26 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685469326; cv=none; d=google.com; s=arc-20160816; b=wpU3E6zVKhCV/B1Ac2Q9sfSvhvW1b5Y5b0bPS5QwR3ak34+3F13x+ihcYgRW3ux3+n MDp48smeT1fm/KM+Vg2CWhDCSm2b1r9wEek/xgUaXzdFMyFuIWiqEh7epKVP56IS1vy9 vFAZaispIr1VXj3ZC0v4Jo6Yl/9ZUCgZIVMLvUS1cOkZfcuT1XkVmoI6sJBY/rt0MtyW ybmXlbgKMNRFHfCJYbA9EYAORSGDdup8EbLhRiVAsd7y48h65A6tZnCPuxD54f7TBMQd jzPaxyC9bYn1ZzNkBlzcUp290F8yemMFnKQn6FlP0JZvQQ+uAFUbPsXAmAkN9RbfR6vb cloQ== 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=wAwxfY2X7qdETpWnMtGFNc8fhRRNQ2ovC0GFrLjYycw=; b=Sle13qBOYxVbWAlWWn6drztrxhE0KR4G9wMTBCvSiBahgKp9oz3cO9p5xZn4YLbesX hYrptkrtJd00N45Xj1x/QLO1xdMFnTVUVWcD9u5xize9B3rhWXK7sgPgW2wm1UYm141H Gi7tx/GCOpO+tmS+TSqry3HJ5dy03afOPmL2Lg7uHQRFq5h592X5MDsUrO7G+Kk5hgC6 /pGDgBSOv/xTGDXis7HgK758rC1OXsjKBUUdgY3FY+izXwqbHbmr4KkSaA/t0K4ZBEVS ckNEEnfZbdXzJK5mOzketiRUCzGezoxkj2m5QrX2Oqw2QKBGXLBsvyna31Dux5Tpde04 kP5w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b=D+8X1h2H; 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 q3-20020a170902788300b001aaed82c2afsi11170302pll.171.2023.05.30.10.55.12; Tue, 30 May 2023 10:55:26 -0700 (PDT) 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=D+8X1h2H; 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 S233215AbjE3RlD (ORCPT + 99 others); Tue, 30 May 2023 13:41:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35434 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232289AbjE3Rk5 (ORCPT ); Tue, 30 May 2023 13:40:57 -0400 Received: from dfw.source.kernel.org (dfw.source.kernel.org [IPv6:2604:1380:4641:c500::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 7D099C5; Tue, 30 May 2023 10:40:56 -0700 (PDT) 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 071F66315B; Tue, 30 May 2023 17:40:56 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 18B86C433D2; Tue, 30 May 2023 17:40:52 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1685468455; bh=w1NSZYYEBgNyVUqt+H+MeKBqo+IDthEwPi4Kkb5qD/M=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=D+8X1h2HONo52l0m9O4m3gQrGOFvIBRYgKU0nP8Vq/QP+CxqlmxVcE8C0EfyHKmI4 rQEen38kgnd1EWVDQGSVyFpom4Pl/MmWGfYP4if5IG07jejorzb0IZRM2/s6UvfcYI vVdwp95qyNdk1nCpgI2NWo8GFMDcVApjMjWOicfvqLRNBEXFGm/rqxRNy9egSizf3K DopwCi61LJugeC3nQ9Bh1zKZ5gtL4NoUkZvN1pgk5lIdFW6gUsSM+9XZtxwJbS7AUc iZTvIc7lUvC+jgbAlR/drR+9dXWXxEkzrrl+JsD3LOZAn5XF2KzlqHOme7aaoonS2z xfZSr3G7Rcr4g== From: Mark Brown To: Boerge Struempfel Cc: bstruempfel@ultratronik.de, andy.shevchenko@gmail.com, festevam@gmail.com, amit.kumar-mahapatra@amd.com, Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , NXP Linux Team , linux-spi@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <20230530141641.1155691-1-boerge.struempfel@gmail.com> References: <20230530141641.1155691-1-boerge.struempfel@gmail.com> Subject: Re: [PATCH v7 0/5] spi: add SPI_MOSI_IDLE_LOW mode bit Message-Id: <168546845282.691057.8142290135375086082.b4-ty@kernel.org> Date: Tue, 30 May 2023 18:40:52 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13-dev-bfdf5 X-Spam-Status: No, score=-4.6 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_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE 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 Tue, 30 May 2023 16:16:36 +0200, Boerge Struempfel wrote: > Some spi controller switch the mosi line to high, whenever they are > idle. This may not be desired in all use cases. For example neopixel > leds can get confused and flicker due to misinterpreting the idle state. > Therefore, we introduce a new spi-mode bit, with which the idle behaviour > can be overwritten on a per device basis. > Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/5] spi: add SPI_MOSI_IDLE_LOW mode bit commit: fe73245592fef75a7c41180a3fbb07c9a75f622e [2/5] spi: spi-imx: add support for SPI_MOSI_IDLE_LOW mode bit commit: 6a983ff5102ff0d859df05ca3f5cf2f6a17c0fad [3/5] spi: spidev: add two new spi mode bits commit: 5cc223ca4858ec40bd2b8522ebc51c0d4963e51f [4/5] spi: spidev_test: Sorted the options into logical groups commit: 113f36f2dce3a5a1aacbfa700c44080ec37ee3a0 [5/5] spi: spidev_test Add three missing spi mode bits commit: b229a7f530ebea90c8e21b56872f3102e3d54461 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