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 1595AC43219 for ; Mon, 18 Oct 2021 11:34:45 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id F11E760EE5 for ; Mon, 18 Oct 2021 11:34:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229581AbhJRLgy (ORCPT ); Mon, 18 Oct 2021 07:36:54 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:35804 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229833AbhJRLgy (ORCPT ); Mon, 18 Oct 2021 07:36:54 -0400 Received: from mail-ot1-x32a.google.com (mail-ot1-x32a.google.com [IPv6:2607:f8b0:4864:20::32a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 146D3C061765 for ; Mon, 18 Oct 2021 04:34:43 -0700 (PDT) Received: by mail-ot1-x32a.google.com with SMTP id l10-20020a056830154a00b00552b74d629aso1625793otp.5 for ; Mon, 18 Oct 2021 04:34:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6G8Hfd9HWWdOmQn8dJ/4ZTN0E6g9DldkLudnuHQWD1k=; b=mfWHkg6A++/9gjuM+FUS0mGsRBbFBJOlC/EjyddiPAJctM5q/3aGEkGv0P9ExrHLYf vlnNzUKEfOTtJzDy0NRR4NFTvE8RnCv5Smk1MSYJQUYBgQc5ztrxlGLQ6BvCE6HgqeHR AuoMfraz4oXYEmgUAVhlRhm6sQ6nWYWvEQiL/5R7bLCmzwDP9RIyY3PFQFpKf0P/mdMb //v1bgSYW9PRlFyzfVwe5fv6KzVlQVdy0Ry0vHqL9/4UtfDzq4BV85xu2Uh50jPPrQl5 zIZuwOmHSc6Thw3vfNcXkvSf9F+XlsvT5aeSj7mjWcE3tgqqeaVhgoC46G9Tj2XzjpoB yUtg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6G8Hfd9HWWdOmQn8dJ/4ZTN0E6g9DldkLudnuHQWD1k=; b=pgIV83YSoCFzYVfvtfBIkJDElQ3DVXIx2Y/QmaD/GqSe5uSi6KN8/euI+0bMDdOLEN 3Ok8W/GAVw6sOjA99epvd2tDHa+88nlq6bxKfiPxvXdeieY4RGrANotosDRkdovp9j96 C4VWMo/i9bkQClWitw7Giz8enZm8AfW2Mrh30o+4c9KvEbgNcOv8FHQq/kXSMSS8DfOY qovGZHGd0JKYv3zoh6yIiKGXHU6oM9Q8u+TBs1QkWRjFgkDu1FCe7Kyh3gna4pBvkkYg 0yjSf0rp5Oj34gYmFYshhW29R5WzWxtQYJnFPMBISfgLYFCyLqEYr+jveKAYzu8if0Oi LG0Q== X-Gm-Message-State: AOAM53311BhklrbCEB870aJxzPF62Ef3IkB7xNsMGnElw0LSreUu+ORM mhIwz00aIya3NPju4x4trSlyxgcqkRcTsnW26+Yj8A== X-Google-Smtp-Source: ABdhPJzToQU6dBlbmasyOXnGLHSpLJDGclh9CmgZFd06P3bvgiJJeE2czOxOsSKQnEzr3MFg2ogcNZYW8cFjW+0K93M= X-Received: by 2002:a05:6830:1c26:: with SMTP id f6mr20715033ote.28.1634556882315; Mon, 18 Oct 2021 04:34:42 -0700 (PDT) MIME-Version: 1.0 References: <20211011141733.3999-1-stephan@gerhold.net> <20211011141733.3999-2-stephan@gerhold.net> In-Reply-To: <20211011141733.3999-2-stephan@gerhold.net> From: Bhupesh Sharma Date: Mon, 18 Oct 2021 17:04:31 +0530 Message-ID: Subject: Re: [PATCH net-next v2 1/4] dt-bindings: dmaengine: bam_dma: Add "powered remotely" mode To: Stephan Gerhold Cc: "David S. Miller" , Jakub Kicinski , Loic Poulain , Sergey Ryazanov , Johannes Berg , Bjorn Andersson , Andy Gross , Vinod Koul , Rob Herring , Aleksander Morgado , netdev@vger.kernel.org, MSM , dmaengine@vger.kernel.org, devicetree , Linux Kernel Mailing List , phone-devel@vger.kernel.org, ~postmarketos/upstreaming@lists.sr.ht, Jeffrey Hugo Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-arm-msm@vger.kernel.org Hi Stephan, On Mon, 11 Oct 2021 at 20:12, 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 since RFC: > - Rename qcom,remote-power-collapse -> qcom,powered-remotely > for consistency with "qcom,controlled-remotely" > > NOTE: This is *not* a compile-time requirement for the BAM-DMUX driver > so this could also go through the dmaengine tree. > > 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/ Seems you missed the latest series posted last week - [1]. Sorry I got a bit delayed posting it due to being caught up in other patches. Maybe you can rebase your patch on the same and use the YAML bindings for the qcom,bam_dma controller. [1]. https://lore.kernel.org/linux-arm-msm/20211013105541.68045-1-bhupesh.sharma@linaro.org/T/#t Regards, Bhupesh > --- > Documentation/devicetree/bindings/dma/qcom_bam_dma.txt | 2 ++ > 1 file changed, 2 insertions(+) > > diff --git a/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt b/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt > index cf5b9e44432c..6e9a5497b3f2 100644 > --- a/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt > +++ b/Documentation/devicetree/bindings/dma/qcom_bam_dma.txt > @@ -15,6 +15,8 @@ Required properties: > the secure world. > - qcom,controlled-remotely : optional, indicates that the bam is controlled by > remote proccessor i.e. execution environment. > +- qcom,powered-remotely : optional, indicates that the bam is powered up by > + a remote processor but must be initialized by the local processor. > - num-channels : optional, indicates supported number of DMA channels in a > remotely controlled bam. > - qcom,num-ees : optional, indicates supported number of Execution Environments > -- > 2.33.0 >