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 50DFFC433F5 for ; Tue, 15 Feb 2022 05:44:17 +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:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=/uVjAhTeHl8DvjCVoLI9DjxPW2mdmiI9HZ+0dsud724=; b=GnHEYJKrKnQZNc a43/tnlQMTZdAOsIZeE3t/E4gS8b/bwziqfe1E8cMcXpwh+vfN9CunL/V9MWeyWA6J/WjmUv8klg/ IXAowc4TCaDTPR/KzXelINPnxY1RMBM6Ed5FYsR9bW83qaVKBirFgD0nJ0PYrgRHyT0Kniaw09LmC L9PjKhF9dj9HmXGHbw3FR5JTRTIlvVMJCKAv16pr9Rf9O9gbAhxariQxYjGzRPq+azkn7w6v2+u7g cDmVUtF4dmsymDlqoK0WN0DnBHQnCPIclfPO3Yrmgflgbrm84itHFwaJF2Edw8ubCRSqxkZy+q+AM TPBELR3VeimEpuXNQhhA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nJqbZ-000KMH-P4; Tue, 15 Feb 2022 05:42:25 +0000 Received: from ams.source.kernel.org ([2604:1380:4601:e00::1]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nJqbW-000KKm-0m for linux-arm-kernel@lists.infradead.org; Tue, 15 Feb 2022 05:42:23 +0000 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 ams.source.kernel.org (Postfix) with ESMTPS id 91CF7B8171A; Tue, 15 Feb 2022 05:42:20 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 7F64FC340EC; Tue, 15 Feb 2022 05:42:18 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1644903739; bh=ea5uavDZWYK+1btNRQTGqmqDvg/Qnuw0OTjPXj0lYaA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=c7+SElxUQ+qFQPU2reBVjOq/J4pODDFbxRufI7yBhTG4U4XceJvnk6gRFXHvWvax9 eoVV8+AQHviE7J2oaANhRo8nrxhKJng8moYtiv9QPlgrWSLoQUz7sg3IgZEkAXdsHs if/jmjQsNyw9Ifpm8/+qbbzvEBVhrPyqkPinZWLePoPktx7xx3IcF3sOwhOZhX5m8Q wXvPlHHSAyJq93PPe9GTdxwHPqQuZzY8Nbkt1QB9MYt7W6ohQ8z3qv77ipZxx/TT8o EMsqVbEkmh9vqlaSSY5goh1XwmjbDXEIl9GwS5h6Vhzf2XclL7nu3TgcRnwGJnmMNa t/UyqHIRCzLDQ== Date: Tue, 15 Feb 2022 11:12:15 +0530 From: Vinod Koul To: Amelie Delaunay Cc: Maxime Coquelin , Alexandre Torgue , dmaengine@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Alain Volmat Subject: Re: [PATCH] dmaengine: stm32-dma: set dma_device max_sg_burst Message-ID: References: <20220117091740.11064-1-amelie.delaunay@foss.st.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220117091740.11064-1-amelie.delaunay@foss.st.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220214_214222_272227_014C52BD X-CRM114-Status: GOOD ( 10.70 ) 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 17-01-22, 10:17, Amelie Delaunay wrote: > Some stm32-dma consumers [1] rather use dma_get_slave_caps() to get > max_sg_burst of their DMA channel as dma_get_max_seg_size() is specific to > the DMA controller. > All stm32-dma channels have the same features so, don't need to implement > device_caps ops. Let dma_get_slave_caps() relies on dma_device > configuration. > That's why this patch sets dma_device max_sg_burst to the maximum segment > size, which is the maximum of data items that can be transferred without > software intervention. Applied, thanks -- ~Vinod _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel