From: Biwen Li <biwen.li@oss.nxp.com>
To: leoyang.li@nxp.com, linux@rempel-privat.de,
kernel@pengutronix.de, wsa@the-dreams.de, shawnguo@kernel.org,
s.hauer@pengutronix.de, festevam@gmail.com, aisheng.dong@nxp.com,
xiaoning.wang@nxp.com, o.rempel@pengutronix.de
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
jiafei.pan@nxp.com, xiaobo.xie@nxp.com,
linux-arm-kernel@lists.infradead.org, Biwen Li <biwen.li@nxp.com>
Subject: [v9 2/2] i2c: imx: select I2C_SLAVE by default
Date: Mon, 2 Nov 2020 16:21:02 +0800 [thread overview]
Message-ID: <20201102082102.16508-2-biwen.li@oss.nxp.com> (raw)
In-Reply-To: <20201102082102.16508-1-biwen.li@oss.nxp.com>
From: Biwen Li <biwen.li@nxp.com>
Select I2C_SLAVE by default
Signed-off-by: Biwen Li <biwen.li@nxp.com>
---
Change in v9:
- none
drivers/i2c/busses/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index a4f473ef4e5c..d3d9a61db76e 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -675,6 +675,7 @@ config I2C_IMG
config I2C_IMX
tristate "IMX I2C interface"
depends on ARCH_MXC || ARCH_LAYERSCAPE || COLDFIRE
+ select I2C_SLAVE
help
Say Y here if you want to use the IIC bus controller on
the Freescale i.MX/MXC, Layerscape or ColdFire processors.
--
2.17.1
next prev parent reply other threads:[~2020-11-02 8:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 8:21 [v9 1/2] i2c: imx: support slave mode for imx I2C driver Biwen Li
2020-11-02 8:21 ` Biwen Li [this message]
2020-11-10 10:48 ` [v9 2/2] i2c: imx: select I2C_SLAVE by default Oleksij Rempel
2020-11-11 3:16 ` Biwen Li (OSS)
2020-11-10 6:07 ` [v9 1/2] i2c: imx: support slave mode for imx I2C driver Biwen Li
2020-11-10 11:49 ` Oleksij Rempel
2020-11-11 8:47 ` Biwen Li (OSS)
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=20201102082102.16508-2-biwen.li@oss.nxp.com \
--to=biwen.li@oss.nxp.com \
--cc=aisheng.dong@nxp.com \
--cc=biwen.li@nxp.com \
--cc=festevam@gmail.com \
--cc=jiafei.pan@nxp.com \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rempel-privat.de \
--cc=o.rempel@pengutronix.de \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=wsa@the-dreams.de \
--cc=xiaobo.xie@nxp.com \
--cc=xiaoning.wang@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;
as well as URLs for NNTP newsgroup(s).