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 X-Spam-Level: X-Spam-Status: No, score=-6.1 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING, SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D348BC433E0 for ; Fri, 5 Jun 2020 11:14:09 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AE98820772 for ; Fri, 5 Jun 2020 11:14:09 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591355649; bh=FhAb3NUX5XtgX3SNWFKeMQklpim0Rc+VQXAf3n11B48=; h=Date:From:To:Cc:In-Reply-To:References:Subject:List-ID:From; b=GQXWQZ1zkGfbVPER3DuB7CXkCUOsOOoWYK0rjbMLkVsaJdN1gSaY9OLDNf3yOhzpt SQw0ysTwoBoj0xb8uSi3mmBYmK6Zm+NRMhBdgnkSrVYDyk3RF2AFKizVRgO5e1BBTA 8ZF1dQxem7DslJLEehr+t3f3DxKIG7Zoz8G88zjw= Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726748AbgFELOI (ORCPT ); Fri, 5 Jun 2020 07:14:08 -0400 Received: from mail.kernel.org ([198.145.29.99]:39634 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726225AbgFELOH (ORCPT ); Fri, 5 Jun 2020 07:14:07 -0400 Received: from localhost (fw-tnat.cambridge.arm.com [217.140.96.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id 1CA18206DC; Fri, 5 Jun 2020 11:14:05 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1591355646; bh=FhAb3NUX5XtgX3SNWFKeMQklpim0Rc+VQXAf3n11B48=; h=Date:From:To:Cc:In-Reply-To:References:Subject:From; b=RsNurQNAk+Ygtpn2S+ix+bGTrsx7FD9Wjhd1QTeKJ93xOpk85sjG8ut2NJ8JJwG8A qEumIvaXxE7pxU/vLtRjt0oV2BIvt3iMH2r6gFpPePJM9YWmvv/Hzbc616507Yz4rS ZlJS5qtQfer0Js4I41SxPRLdulUbbdzq3QDdtn5I= Date: Fri, 05 Jun 2020 12:14:04 +0100 From: Mark Brown To: linux-kernel@vger.kernel.org, Florian Fainelli Cc: Ray Jui , "open list:SPI SUBSYSTEM" , lukas@wunner.de, Rob Herring , "maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..." , Martin Sperl , Scott Branden , Nicolas Saenz Julienne , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , "moderated list:BROADCOM BCM2711/BCM2835 ARM ARCHITECTURE" , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" In-Reply-To: <20200604212819.715-1-f.fainelli@gmail.com> References: <20200604212819.715-1-f.fainelli@gmail.com> Subject: Re: [PATCH v2] spi: bcm2835: Enable shared interrupt support Message-Id: <159135564425.14579.13716287498736798458.b4-ty@kernel.org> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, 4 Jun 2020 14:28:19 -0700, Florian Fainelli wrote: > The 4 SPI controller instances added in BCM2711 and BCM7211 SoCs (SPI3, > SPI4, SPI5 and SPI6) share the same interrupt line with SPI0. > > For the BCM2835 case which is deemed performance critical, we would like > to continue using an interrupt handler which does not have the extra > comparison on BCM2835_SPI_CS_INTR. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: bcm2835: Enable shared interrupt support commit: ecfbd3cf3b8bb73ac6a80ddf430b5912fd4402a6 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