From: Oleksij Rempel <o.rempel@pengutronix.de>
To: Wolfram Sang <wsa@the-dreams.de>, Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>
Cc: Oleksij Rempel <o.rempel@pengutronix.de>,
linux-i2c@vger.kernel.org,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <fabio.estevam@nxp.com>,
linux-arm-kernel@lists.infradead.org,
NXP Linux Team <linux-imx@nxp.com>
Subject: [PATCH v1 0/3] i2c: imx: DMA related fixes
Date: Thu, 18 Oct 2018 13:26:12 +0200 [thread overview]
Message-ID: <20181018112615.29362-1-o.rempel@pengutronix.de> (raw)
Current i2c-imx module prints DMA warnings which in many cases are
false positive and just confuse testers:
1. DMA is not available on chips before i.MX50
2. DMA for i2c is muxed with some other peripheral, and can be used only
for one of devices at same time. So, obvious choice it to use it with
SDHC instead of i2c.
Oleksij Rempel (3):
ARM: dts: imx6sll: fix typo for fsl,imx6sll-i2c node
i2c: imx: probe dma only only on i.MX50 and later.
i2c: imx: don't print error if DMA is not configured
arch/arm/boot/dts/imx6sll.dtsi | 2 +-
drivers/i2c/busses/i2c-imx.c | 89 +++++++++++++++++++++++++++-------
2 files changed, 73 insertions(+), 18 deletions(-)
--
2.19.0
next reply other threads:[~2018-10-18 11:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 11:26 Oleksij Rempel [this message]
2018-10-18 11:26 ` [PATCH v1 1/3] ARM: dts: imx6sll: fix typo for fsl,imx6sll-i2c node Oleksij Rempel
2018-10-18 18:43 ` Uwe Kleine-König
2018-10-31 7:50 ` Shawn Guo
2018-10-18 11:26 ` [PATCH v1 2/3] i2c: imx: probe dma only only on i.MX50 and later Oleksij Rempel
2018-10-19 7:12 ` Uwe Kleine-König
2018-10-19 9:01 ` Oleksij Rempel
2018-10-19 9:21 ` Uwe Kleine-König
2018-10-19 10:17 ` Oleksij Rempel
2018-10-18 11:26 ` [PATCH v1 3/3] i2c: imx: don't print error if DMA is not configured Oleksij Rempel
2018-10-28 22:11 ` Wolfram Sang
2018-10-29 8:07 ` Oleksij Rempel
2018-10-29 8:54 ` Wolfram Sang
2018-11-03 20:59 ` Uwe Kleine-König
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=20181018112615.29362-1-o.rempel@pengutronix.de \
--to=o.rempel@pengutronix.de \
--cc=fabio.estevam@nxp.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wsa@the-dreams.de \
/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).