public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Stach <l.stach@pengutronix.de>
To: Robin Gong <yibin.gong@nxp.com>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"vkoul@kernel.org" <vkoul@kernel.org>,
	"dan.j.williams@intel.com" <dan.j.williams@intel.com>
Cc: "dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v3 0/6] add virt-dma support for imx-sdma
Date: Wed, 13 Jun 2018 18:07:52 +0200	[thread overview]
Message-ID: <1528906072.21021.22.camel@pengutronix.de> (raw)
In-Reply-To: <1528822708.13468.9.camel@nxp.com>

Hi Robin,

Am Dienstag, den 12.06.2018, 08:58 +0000 schrieb Robin Gong:
> Hi Lucas,
> 	Is the below DEAD LOCK issue same as your side? If yes, then
> I'm afraid that we have to make another patch for uart to split dma
> functions in uart driver out of the code area which protected by
> port.lock. The warning make sense since allocate sdma bd memory
> dynamically in virt-dma instead of static allocated as before. I'll
> make another uart patch into my next version patchset.

Yes, I see the same lockdep splat on my system. Though I'm not sure if
this is really the root cause of the issue I see.

I'm getting timeouts for a serdev attached device and I don't think
this system ever enters memory reclaim, so the issue reported by
lockdep seems to be a mostly theoretical on this system. But lets see
how far I get when you fixed this issue, maybe the real bug is hiding
behind this one.

Regards,
Lucas

  reply	other threads:[~2018-06-13 16:08 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-11 14:59 [PATCH v3 0/6] add virt-dma support for imx-sdma Robin Gong
2018-06-11 11:01 ` Lucas Stach
2018-06-11 12:09   ` Robin Gong
2018-06-12  8:58   ` Robin Gong
2018-06-13 16:07     ` Lucas Stach [this message]
2018-06-14  3:04       ` Robin Gong
2018-06-11 14:59 ` [PATCH v3 1/6] dmaengine: imx-sdma: factor out a struct sdma_desc from struct sdma_channel Robin Gong
2018-06-11 14:59 ` [PATCH v3 2/6] dmaengine: imx-sdma: add virt-dma support Robin Gong
2018-06-11 14:59 ` [PATCH v3 3/6] Revert "dmaengine: imx-sdma: fix pagefault when channel is disabled during interrupt" Robin Gong
2018-06-11 14:59 ` [PATCH v3 4/6] dmaengine: imx-sdma: remove usless lock Robin Gong
2018-06-13  9:53   ` Sascha Hauer
2018-06-11 14:59 ` [PATCH v3 5/6] dmaengine: imx-sdma: remove the maximum limation for bd numbers Robin Gong
2018-06-13  9:54   ` Sascha Hauer
2018-06-11 14:59 ` [PATCH v3 6/6] dmaengine: imx-sdma: add sdma_transfer_init to decrease code overlap Robin Gong

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=1528906072.21021.22.camel@pengutronix.de \
    --to=l.stach@pengutronix.de \
    --cc=dan.j.williams@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=vkoul@kernel.org \
    --cc=yibin.gong@nxp.com \
    /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