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 mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 7E940C433FE for ; Mon, 18 Oct 2021 19:51:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 64BA4611EF for ; Mon, 18 Oct 2021 19:51:05 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233555AbhJRTxQ (ORCPT ); Mon, 18 Oct 2021 15:53:16 -0400 Received: from mail-oi1-f181.google.com ([209.85.167.181]:33534 "EHLO mail-oi1-f181.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233058AbhJRTxO (ORCPT ); Mon, 18 Oct 2021 15:53:14 -0400 Received: by mail-oi1-f181.google.com with SMTP id q129so1420019oib.0; Mon, 18 Oct 2021 12:51:01 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=lf3qtAxK2ioLkCYFQ61b4Q438IlhGZsYG/jj2QqM7UU=; b=Zgk298lt7ejA3N1TYrRrIQPGeGTXJnbToYhRVFjex1cFjvu7AYmfoXnCHXZ/E2gCZ1 lIyoLaTmU0s2KXuGlyWFLOuhkf731WeQApRy85wPhVpt1hFI9QelJFgtzAWwY1HbbINc Q9WQ/8m3jWcqoS4b+q7jtt2I9EKFmba5pEHKAHQMyhg/tU5nqFhhGslRvUG6zTlBQk7i iZVquoHAKenHTUiPvmlC+AUf6rZB8aDhExtpbsP338GIjl/Ear6pB+SoZCgcryPv5j3R rpNZ2xvNTk6qwcyBN8VO40ncvaGaFG4reoXw93GfLh8moJzyUzYZ6Ama8nsOczGMwdjn yyMg== X-Gm-Message-State: AOAM5337pOeowPq+HIAWIgrL043Q874nMotVoonAUaQ7YKiHa808e0s2 /APSKWx/sZOOUKE3Nl3uwPOEzVkiiw== X-Google-Smtp-Source: ABdhPJwy38f+G119ZJbY4wMzLDCMvMfqXcc7P7WcoSVKfwmQEz684171NnJwHyQXIn1sft4nIxhP7w== X-Received: by 2002:aca:1e04:: with SMTP id m4mr714654oic.67.1634586661558; Mon, 18 Oct 2021 12:51:01 -0700 (PDT) Received: from robh.at.kernel.org (66-90-148-213.dyn.grandenetworks.net. [66.90.148.213]) by smtp.gmail.com with ESMTPSA id bb39sm3360644oib.28.2021.10.18.12.51.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 Oct 2021 12:51:01 -0700 (PDT) Received: (nullmailer pid 2839571 invoked by uid 1000); Mon, 18 Oct 2021 19:51:00 -0000 Date: Mon, 18 Oct 2021 14:51:00 -0500 From: Rob Herring To: Stephan Gerhold Cc: devicetree@vger.kernel.org, Andy Gross , ~postmarketos/upstreaming@lists.sr.ht, linux-arm-msm@vger.kernel.org, dmaengine@vger.kernel.org, Bjorn Andersson , Vinod Koul , Rob Herring Subject: Re: [PATCH v3 1/2] dt-bindings: dmaengine: bam_dma: Add "powered remotely" mode Message-ID: References: <20211018102421.19848-1-stephan@gerhold.net> <20211018102421.19848-2-stephan@gerhold.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211018102421.19848-2-stephan@gerhold.net> Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org On Mon, 18 Oct 2021 12:24:20 +0200, Stephan Gerhold wrote: > In some configurations, the BAM DMA controller is set up by a remote > processor and the local processor can simply start making use of it > without setting up the BAM. This is already supported using the > "qcom,controlled-remotely" property. > > However, for some reason another possible configuration is that the > remote processor is responsible for powering up the BAM, but we are > still responsible for initializing it (e.g. resetting it etc). Add > a "qcom,powered-remotely" property to describe that configuration. > > Signed-off-by: Stephan Gerhold > --- > Changes in v3: None, split from BAM-DMUX patch set > Changes since RFC: > - Rename qcom,remote-power-collapse -> qcom,powered-remotely > for consistency with "qcom,controlled-remotely" > > Also note that there is an ongoing effort to convert these bindings > to DT schema but sadly there were not any updates for a while. :/ > https://lore.kernel.org/linux-arm-msm/20210519143700.27392-2-bhupesh.sharma@linaro.org/ > --- > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > 1 file changed, 2 insertions(+) > Acked-by: Rob Herring