From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id 74C07137932; Fri, 29 Mar 2024 17:35:36 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711733736; cv=none; b=FCO+jgpm+6vN+jSoeEIvq20KV2zBzPN4t2VTaat8QWFd//qYNNmFLGjeMsT2x/pljWpa68GecFj8FEY5HTgthwHvzj9DS4N1sU7Ph5er3MRSBOkYycn0B7ZbfzucjBD+7qjoDPRjOcBoIs1TTdArNP2eaeL8nwxKyUCJc4pDNCY= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711733736; c=relaxed/simple; bh=o4A1HO9SIxvTZDIl37Qyw+HvUHARhJ6hxjCxrOrTbU4=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=BEj4+maieL1nQ0BYSjwJsLl0fSKp0VveQeml9tXBgB+b2LwHK+JT34GYhR8c4N7OhIMDyVE2JG2UztoPY46+VyU0+RsV3O5I59dHYlifGhgbSYn61yjZwmjtfUvz7RRTMAAJtIuMsTjU4o65IEealByaLQh0BzEKIYezthF69nE= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=vIZQfmjQ; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="vIZQfmjQ" Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2C54EC433F1; Fri, 29 Mar 2024 17:35:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711733736; bh=o4A1HO9SIxvTZDIl37Qyw+HvUHARhJ6hxjCxrOrTbU4=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=vIZQfmjQzaA4ofkQ0H6qG+dzf3wO3WXHT5uGtVPRykGw5iHbztGUnsnMNouv0Sf3d y7fVkzTLNAzixYo96VrlldogyP1kt/xFQ3uMSKifNvdqgC8HAz5MQX4uzzTcTalWoa oybOAEBM91cBAGda6b1UhP4i2PG2iqopZcA4XDm47x8+kmlxrD5DxqUm2819K67sSO ZWgtwwRqsIcuk5eMwSIaRibxFMGik5CFdRp6CTRqpHd+skL1v3bkC9O0MeA84c56Bg YOaG0ALmC/v64mL5S6g41v2vIp76EIzdNgAkRGMgZCOeWSVSAl8cE04f8nXdZEqc90 +qDnSeeXuKvCg== From: Mark Brown To: Andi Shyti , Krzysztof Kozlowski , Alim Akhtar , Sam Protsenko , Jaewon Kim Cc: linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <20240329085840.65856-1-jaewon02.kim@samsung.com> References: <20240329085840.65856-1-jaewon02.kim@samsung.com> Subject: Re: [PATCH] spi: s3c64xx: Use DMA mode from fifo size Message-Id: <171173373339.1605661.7010691165644854540.b4-ty@kernel.org> Date: Fri, 29 Mar 2024 17:35:33 +0000 Precedence: bulk X-Mailing-List: linux-spi@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13-dev-0438c On Fri, 29 Mar 2024 17:58:40 +0900, Jaewon Kim wrote: > If the SPI data size is smaller than FIFO, it operates in PIO mode, > and if it is larger than FIFO size, it oerates in DMA mode. > > If the SPI data size is equal to fifo, it operates in PIO mode and it is > separated to 2 transfers. To prevent it, it must operate in DMA mode > from the case where the data size and the fifo size are the same. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: s3c64xx: Use DMA mode from fifo size commit: a3d3eab627bbbb0cb175910cf8d0f7022628a642 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 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 bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 6EB20C6FD1F for ; Fri, 29 Mar 2024 17:35:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:Date:Message-Id:Subject: References:In-Reply-To:Cc:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=EcWyACkrZxJD4ZhL2wjr6a0Rpm9x/QuWFOojhxnDxtY=; b=O6wkRnMd2q7Nnc uUk8LVlmFOSHnR+S2cFrdzgXBvhkUc5+sfMRF77GeGOd4bpBtCyWHnwX3cw2P1R92jv4a25AUoEOP 2vl1EdsUCUSfuxc1Jfl6JK4LSPLwZ+5uSmbAxjEgYz0V+xLlEWE85xhhYxN0ww1szmAuNvWoXsULz lXZLsX5gbsmPvXfW8jWyO61xNvTX5wfyV3ovvLhye5aguvTfm3FE1bMz0hnj7rAlHIWo6Y/LIWVEh 0iX5p1Box89jId6IwD0mwIyKd8IY2qcTNZFtHcjS7JBTI3of0iFrjanZw1yshKYEp3hwgypj3DA5N uexriE9l61R6546ai3VA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rqG8j-00000001VBU-1GhI; Fri, 29 Mar 2024 17:35:41 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rqG8g-00000001VAN-12qr for linux-arm-kernel@lists.infradead.org; Fri, 29 Mar 2024 17:35:39 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 7073ECE3035; Fri, 29 Mar 2024 17:35:36 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 2C54EC433F1; Fri, 29 Mar 2024 17:35:34 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1711733736; bh=o4A1HO9SIxvTZDIl37Qyw+HvUHARhJ6hxjCxrOrTbU4=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=vIZQfmjQzaA4ofkQ0H6qG+dzf3wO3WXHT5uGtVPRykGw5iHbztGUnsnMNouv0Sf3d y7fVkzTLNAzixYo96VrlldogyP1kt/xFQ3uMSKifNvdqgC8HAz5MQX4uzzTcTalWoa oybOAEBM91cBAGda6b1UhP4i2PG2iqopZcA4XDm47x8+kmlxrD5DxqUm2819K67sSO ZWgtwwRqsIcuk5eMwSIaRibxFMGik5CFdRp6CTRqpHd+skL1v3bkC9O0MeA84c56Bg YOaG0ALmC/v64mL5S6g41v2vIp76EIzdNgAkRGMgZCOeWSVSAl8cE04f8nXdZEqc90 +qDnSeeXuKvCg== From: Mark Brown To: Andi Shyti , Krzysztof Kozlowski , Alim Akhtar , Sam Protsenko , Jaewon Kim Cc: linux-spi@vger.kernel.org, linux-samsung-soc@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org In-Reply-To: <20240329085840.65856-1-jaewon02.kim@samsung.com> References: <20240329085840.65856-1-jaewon02.kim@samsung.com> Subject: Re: [PATCH] spi: s3c64xx: Use DMA mode from fifo size Message-Id: <171173373339.1605661.7010691165644854540.b4-ty@kernel.org> Date: Fri, 29 Mar 2024 17:35:33 +0000 MIME-Version: 1.0 X-Mailer: b4 0.13-dev-0438c X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240329_103538_508992_75D47CAB X-CRM114-Status: GOOD ( 14.27 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Fri, 29 Mar 2024 17:58:40 +0900, Jaewon Kim wrote: > If the SPI data size is smaller than FIFO, it operates in PIO mode, > and if it is larger than FIFO size, it oerates in DMA mode. > > If the SPI data size is equal to fifo, it operates in PIO mode and it is > separated to 2 transfers. To prevent it, it must operate in DMA mode > from the case where the data size and the fifo size are the same. > > [...] Applied to https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next Thanks! [1/1] spi: s3c64xx: Use DMA mode from fifo size commit: a3d3eab627bbbb0cb175910cf8d0f7022628a642 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 _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel