From: Vinod Koul <vkoul@kernel.org>
To: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Cc: gustavo.pimentel@synopsys.com, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Serge Semin <fancer.lancer@gmail.com>,
Frank Li <Frank.Li@nxp.com>
Subject: Re: [PATCH] dmaengine: dw-edma: Remove runtime PM support
Date: Sun, 4 Sep 2022 22:51:59 +0530 [thread overview]
Message-ID: <YxTet82IgKtQ+q9q@matsya> (raw)
In-Reply-To: <20220819084018.GC215264@thinkpad>
On 19-08-22, 14:10, Manivannan Sadhasivam wrote:
> On Thu, May 12, 2022 at 02:06:12PM +0530, Manivannan Sadhasivam wrote:
> > Currently, the dw-edma driver enables the runtime_pm for parent device
> > (chip->dev) and increments/decrements the refcount during alloc/free
> > chan resources callbacks.
> >
> > This leads to a problem when the eDMA driver has been probed, but the
> > channels were not used. This scenario can happen when the DW PCIe driver
> > probes eDMA driver successfully, but the PCI EPF driver decides not to
> > use eDMA channels and use iATU instead for PCI transfers.
> >
> > In this case, the underlying device would be runtime suspended due to
> > pm_runtime_enable() in dw_edma_probe() and the PCI EPF driver would have
> > no knowledge of it.
> >
> > Ideally, the eDMA driver should not be the one doing the runtime PM of
> > the parent device. The responsibility should instead belong to the client
> > drivers like PCI EPF.
> >
> > So let's remove the runtime PM support from eDMA driver.
> >
> > Cc: Serge Semin <fancer.lancer@gmail.com>
> > Cc: Frank Li <Frank.Li@nxp.com>
> > Signed-off-by: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
>
> Looks like this one missed 6.0. Vinod, can you please merge this now?
This fails for me, can you pls rebase and resend
--
~Vinod
prev parent reply other threads:[~2022-09-04 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-12 8:36 [PATCH] dmaengine: dw-edma: Remove runtime PM support Manivannan Sadhasivam
2022-05-12 11:13 ` Serge Semin
2022-08-19 8:40 ` Manivannan Sadhasivam
2022-09-04 17:21 ` Vinod Koul [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YxTet82IgKtQ+q9q@matsya \
--to=vkoul@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=dmaengine@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox