From: Vignesh R <vigneshr@ti.com>
To: Rob Herring <robh+dt@kernel.org>,
Wolfram Sang <wsa+renesas@sang-engineering.com>
Cc: Vignesh R <vigneshr@ti.com>, Sekhar Nori <nsekhar@ti.com>,
Nishanth Menon <nm@ti.com>, Peter Rosin <peda@axentia.se>,
<linux-i2c@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 2/2] i2c: busses: Kconfig: Enable I2C_OMAP for ARCH_K3
Date: Fri, 28 Sep 2018 10:55:57 +0530 [thread overview]
Message-ID: <20180928052557.21663-3-vigneshr@ti.com> (raw)
In-Reply-To: <20180928052557.21663-1-vigneshr@ti.com>
Allow I2C_OMAP to be built for K3 platforms.
Signed-off-by: Vignesh R <vigneshr@ti.com>
---
v2: No changes
drivers/i2c/busses/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
index 451d4ae50e66..ac4b09642f63 100644
--- a/drivers/i2c/busses/Kconfig
+++ b/drivers/i2c/busses/Kconfig
@@ -751,7 +751,7 @@ config I2C_OCORES
config I2C_OMAP
tristate "OMAP I2C adapter"
- depends on ARCH_OMAP
+ depends on ARCH_OMAP || ARCH_K3
default y if MACH_OMAP_H3 || MACH_OMAP_OSK
help
If you say yes to this option, support will be included for the
--
2.19.0
next prev parent reply other threads:[~2018-09-28 5:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-28 5:25 [PATCH v2 0/2] i2c-omap: Enable i2c-omap driver for AM654 SoCs Vignesh R
2018-09-28 5:25 ` [PATCH v2 1/2] dt-bindings: i2c-omap: Add new compatible " Vignesh R
2018-10-12 19:33 ` Rob Herring
2018-09-28 5:25 ` Vignesh R [this message]
2018-10-20 7:53 ` [PATCH v2 0/2] i2c-omap: Enable i2c-omap driver " Vignesh R
2018-10-28 22:34 ` Wolfram Sang
2018-11-07 17:01 ` Vignesh R
2018-11-01 16:18 ` Grygorii Strashko
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=20180928052557.21663-3-vigneshr@ti.com \
--to=vigneshr@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=nsekhar@ti.com \
--cc=peda@axentia.se \
--cc=robh+dt@kernel.org \
--cc=wsa+renesas@sang-engineering.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).