From: Shawn Guo <shawnguo@kernel.org>
To: Li Yang <leoyang.li@nxp.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Grant Likely <grant.likely@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] arm64: defconfig: Enable FSL_EDMA driver
Date: Fri, 10 May 2019 11:05:26 +0800 [thread overview]
Message-ID: <20190510030525.GC15856@dragon> (raw)
In-Reply-To: <20190422183056.16375-1-leoyang.li@nxp.com>
On Mon, Apr 22, 2019 at 01:30:56PM -0500, Li Yang wrote:
> Enables the FSL EDMA driver by default. This also works around an issue
> that imx-i2c driver keeps deferring the probe because of the DMA is not
> ready. And currently the DMA engine framework can not correctly tell
> if the DMA channels will truly become available later (it will never be
> available if the DMA driver is not enabled).
>
> This will cause indefinite messages like below:
> [ 3.335829] imx-i2c 2180000.i2c: can't get pinctrl, bus recovery not supported
> [ 3.344455] ina2xx 0-0040: power monitor ina220 (Rshunt = 1000 uOhm)
> [ 3.350917] lm90 0-004c: 0-004c supply vcc not found, using dummy regulator
> [ 3.362089] imx-i2c 2180000.i2c: can't get pinctrl, bus recovery not supported
> [ 3.370741] ina2xx 0-0040: power monitor ina220 (Rshunt = 1000 uOhm)
> [ 3.377205] lm90 0-004c: 0-004c supply vcc not found, using dummy regulator
> [ 3.388455] imx-i2c 2180000.i2c: can't get pinctrl, bus recovery not supported
> .....
>
> Signed-off-by: Li Yang <leoyang.li@nxp.com>
Applied, thanks.
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2019-05-10 3:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-22 18:30 [PATCH] arm64: defconfig: Enable FSL_EDMA driver Li Yang
2019-05-10 3:05 ` Shawn Guo [this message]
2019-06-12 20:01 ` Li Yang
2019-06-13 0:45 ` Shawn Guo
2019-06-13 14:01 ` Leo Li
2019-06-18 6:31 ` Shawn Guo
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=20190510030525.GC15856@dragon \
--to=shawnguo@kernel.org \
--cc=grant.likely@arm.com \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkoul@kernel.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;
as well as URLs for NNTP newsgroup(s).