From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <dmaengine-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 091CCC433EF
	for <dmaengine@archiver.kernel.org>; Mon, 11 Apr 2022 13:28:39 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S244137AbiDKNav (ORCPT <rfc822;dmaengine@archiver.kernel.org>);
        Mon, 11 Apr 2022 09:30:51 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41220 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S233050AbiDKNau (ORCPT
        <rfc822;dmaengine@vger.kernel.org>); Mon, 11 Apr 2022 09:30:50 -0400
Received: from ams.source.kernel.org (ams.source.kernel.org [145.40.68.75])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 01843A18F;
        Mon, 11 Apr 2022 06:28:36 -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 ams.source.kernel.org (Postfix) with ESMTPS id B05A8B815E9;
        Mon, 11 Apr 2022 13:28:35 +0000 (UTC)
Received: by smtp.kernel.org (Postfix) with ESMTPSA id BCE23C385A3;
        Mon, 11 Apr 2022 13:28:33 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
        s=k20201202; t=1649683714;
        bh=wY2kkpkdJta5VZ4YNiEH8OvoR3YdYHuwo0F1OuTyYj8=;
        h=Date:From:To:Cc:Subject:References:In-Reply-To:From;
        b=IvvY1WzzHSzYXvYnOKCFUjS4UgpB0CDgJmIrACaNIhTZY3PhF79b3OVRp1LoGpM/S
         VfI6g2m25yIelLafewradRDZlul1qbeZi2n1gHeCxqVv0iI/j4m4tDna18EzJzZt1N
         oiL73LjDk9SZ3rq9bC850P0LNimGAlYr8l8IXMPb1k7Mu/ePKVusAM8SE8THQXtH6y
         PGrK8cpM4ZRpqQsqjP8bLqhX2SLgorBNfJMpF9D4l0FM9Qw2O4/aU684TuO3s8aRwj
         x2InZKP4gHKMtgNPOmZYhiTKuOlfPs0tAOKNNumVUZlDVeIz5TDikSjo4m7KR3flqr
         3TwceEzvkDKsA==
Date:   Mon, 11 Apr 2022 18:58:30 +0530
From:   Vinod Koul <vkoul@kernel.org>
To:     Amelie Delaunay <amelie.delaunay@foss.st.com>
Cc:     Maxime Coquelin <mcoquelin.stm32@gmail.com>,
        Alexandre Torgue <alexandre.torgue@foss.st.com>,
        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-mdma: check the channel availability
 (secure or not)
Message-ID: <YlQs/rPFnRWP6W6D@matsya>
References: <20220330103645.99969-1-amelie.delaunay@foss.st.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20220330103645.99969-1-amelie.delaunay@foss.st.com>
Precedence: bulk
List-ID: <dmaengine.vger.kernel.org>
X-Mailing-List: dmaengine@vger.kernel.org

On 30-03-22, 12:36, Amelie Delaunay wrote:
> STM32_MDMA_CCR bit[8] is used to enable Secure Mode (SM). If this bit is
> set, it means that all the channel registers are write-protected. So the
> channel is not available for Linux use.
> 
> Add stm32_mdma_filter_fn() callback filter and give it to
> __dma_request_chan (instead of dma_get_any_slave_channel()), to exclude the
> channel if it is marked Secure.

Applied, thanks

-- 
~Vinod