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 7EC9CC433F5 for ; Mon, 18 Oct 2021 16:41:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 520C261077 for ; Mon, 18 Oct 2021 16:41:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232708AbhJRQnl (ORCPT ); Mon, 18 Oct 2021 12:43:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51406 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232127AbhJRQnk (ORCPT ); Mon, 18 Oct 2021 12:43:40 -0400 Received: from mail-oi1-x22d.google.com (mail-oi1-x22d.google.com [IPv6:2607:f8b0:4864:20::22d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4032AC06161C for ; Mon, 18 Oct 2021 09:41:29 -0700 (PDT) Received: by mail-oi1-x22d.google.com with SMTP id o204so553310oih.13 for ; Mon, 18 Oct 2021 09:41:29 -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=m/74ZeSghoGWz2Y5U8O6ZsL9J98hmrFFn2k+ASasuxI=; b=V/Sg2umzcGxAR3kKFG3Fy5qzN2KDcjvbNbDPZVaGE9ltjEXcESslh7PJ2o2/ybmpNP UFKEXP1js86ftmV1k/I7e/TrkYC6/wQSVyV+vk68P+lRlhHBXg7o+2ZGRYT/JZ6SJ9sC Rzo6euFvfLpT+re3VFTWKSb+c74m/3JcGY6wipnJ1dHRejNOXrIUSd1GaebdANSi3Qb7 9Mcow/pJUlnMAbcheP/las1Om3h3m3i6zigpriw6Z/MENOdDrDyQkO9R7p7b9ZH8aNLU qKXLUBvNx2XeEqdc9CfCezeBu8rx3mP4+VPFrBP9p2Bpw2JTmyJzSb4QNdb5VMtNxwoL c/iQ== 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=m/74ZeSghoGWz2Y5U8O6ZsL9J98hmrFFn2k+ASasuxI=; b=Jma4dfgD2cwds2mEqq+xxKArQJ+NFSqdigzLvKSQoRF39JOp1OHBywa+cObEW005y0 wQ79gF5xBcGiM8A6IfNVeURX7yQWzgyi/37nRCf+qzxfhafD+vNvR/gjqBuedB1LeQU8 kATAjgJFi8jdBbgmFQdfSzy6AC2YCPyt75eLOuwq7Lu+5ADYdVrdemiU4OePWGYq41cS c8vBmpT0CkoPYfcFovS5Pq3BOmnf9813HkD/FdIjLlgjQBPLee/cg+I+ZX098MsFiOLh PAl8phntgFC38GlktjZYEQr22uLk/53aN1aMFGGEKvmbbj6wGKOMu3YsN0ttvDFbFXyP g96A== X-Gm-Message-State: AOAM531GsSVqmm4C4wi0Nzk6qDusOl0RGClrH77Tv0OCnybMvlOX8/qI 3Sl/+7fkT/WLIPBxcSBljebkLFxzss2U1kIeP66nEg== X-Google-Smtp-Source: ABdhPJyhI/boD/Dqt4cOu1o+91uOGjUh5J0lLqztunxb38ijIyGLzE0BAxzGggtm1QdOFWnWdOHyLHlnrRrD206Ea5U= X-Received: by 2002:aca:58d6:: with SMTP id m205mr737607oib.126.1634575288536; Mon, 18 Oct 2021 09:41:28 -0700 (PDT) MIME-Version: 1.0 References: <20211011141733.3999-1-stephan@gerhold.net> <20211011141733.3999-2-stephan@gerhold.net> In-Reply-To: From: Bhupesh Sharma Date: Mon, 18 Oct 2021 22:11:17 +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: dmaengine@vger.kernel.org Hi, On Mon, 18 Oct 2021 at 18:26, Stephan Gerhold wrote: > > On Mon, Oct 18, 2021 at 05:04:31PM +0530, Bhupesh Sharma wrote: > > 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 > > > > Ah, you're right sorry! Seems like you sent it two days after I sent the > v2 of this patch. Thanks a lot for continuing work on this! :) > > Since I already sent v3 of this patch earlier, I think it is best if > I wait a bit first and see if Vinod has any comments or still wants to > take it for 5.16. Should be simple to rebase either of our patches on > the other one. Sure, let's wait for Vinod's comments. Regards, Bhupesh