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 D3226C433FE for ; Thu, 19 May 2022 17:50:39 +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=p24LMWQPKUq5VoWiUplHQUBWxfLjLPkmr9NRvZZ0G3g=; b=lcWYX1NqyqiVoL JAjraB7e8ntw2KNzPUuMat1/7YBuhV7LlAaLiTC6WQdvwsGyNFEnd13f73OqohB8p1HYcueGz/pE/ VMrzPW+we+X8OuEbUNoPr27Y7rN3tnsmwtQXH9tpmKUwLf4SfKpHnTfB0DsGKA0ydd7dhXRlD4Vfw wtJT1e9Mced1forDzVrfGLf7muuoATTabp/rfsEys8m2vp2/wM3/Yk7enXWKEz3lWFwz66HOYf048 x5CifaeP6ePXQfiNSGRXJ/7HiKAz2/CfIPBG/0oKnUa1l5KIVVUweieGDfOZmR4YO/gQ/W6RbU9h0 IPpafJgWgJ/cfArMH4bQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1nrkHR-008hko-QR; Thu, 19 May 2022 17:49:45 +0000 Received: from dfw.source.kernel.org ([139.178.84.217]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1nrkHO-008hjr-Sk for linux-arm-kernel@lists.infradead.org; Thu, 19 May 2022 17:49:44 +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 dfw.source.kernel.org (Postfix) with ESMTPS id 684DD618D6; Thu, 19 May 2022 17:49:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 42F71C385AA; Thu, 19 May 2022 17:49:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1652982581; bh=9A5+aIyuXlTlURbYrnNECxCHAE/FESaqMNCsL6/awOI=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=Puppa7FBRvhE6BDdhEDwhEJWvRlwJNek6upoz4Dr5kf0mDHj/ln2DX4S+ztY5+U2P li2U6dtnwbQWT2DzDSeUBXj1B+Ks0lur/ohsr7Zo6HPaXQl1bPK4My2L2oQURzkH61 Wygy+6X6rvUAirXy1GXvHbF6nQKFmuDyjZIqN5p4kAYuBpNF9SkqWcBXXOR+AHZJqe 9RM2MvzrVBwE8BZCzeLHjzSV52j2siBqjmr32q2E498BIDkVs1KlBtBF+ouXpEx1hY yxH1Pgb/rzdcgk2/PBiGgx/H1S/B8cVx6ZTWf79pG6NThDKRs8Tt1oWc97caOZqmcl eLd11ncCWxqFw== Date: Thu, 19 May 2022 23:19:37 +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 Subject: Re: [PATCH] dmaengine: stm32-dmamux: avoid reset of dmamux if used by coprocessor Message-ID: References: <20220504161724.123180-1-amelie.delaunay@foss.st.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: <20220504161724.123180-1-amelie.delaunay@foss.st.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220519_104943_000372_AAB40A86 X-CRM114-Status: GOOD ( 16.23 ) 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 04-05-22, 18:17, Amelie Delaunay wrote: > One of the two DMA controllers managed by the DMAMUX can be used by the > coprocessor. It is defined in the device tree with dma-masters. > When the two DMA controllers are used by the main CPU, > dma-masters = <&dma1, &dma2>; is specified in the device tree. > When one of the controllers is used by coprocessor (so not managed by > Linux), dma-masters = <&dma1>; is specified in the device tree. > In this case, Linux driver must not reset the DMAMUX, because it could have > been configured by the coprocessor to use the second DMA controller. > count is the number of DMA controllers defined in dma-masters property. > Reset only if resets property is found and valid in device tree, and if > the two DMA controllers are under Linux control. Applied, thanks -- ~Vinod _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel