public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Andrew F. Davis" <afd@ti.com>
To: Arnd Bergmann <arnd@arndb.de>, Sebastian Reichel <sre@kernel.org>,
	Pali Rohar <pali.rohar@gmail.com>,
	Xiong Zhou <jencce.kernel@gmail.com>,
	Dmitry Eremin-Solenikov <dbaryshkov@gmail.com>,
	David Woodhouse <dwmw2@infradead.org>
Cc: <linux-pm@vger.kernel.org>, <linux-i2c@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, "Andrew F. Davis" <afd@ti.com>
Subject: [PATCH] power: bq27xxx_battery: Add I2C module check dependency in Kconfig
Date: Mon, 9 Nov 2015 15:23:03 -0600	[thread overview]
Message-ID: <1447104183-13556-1-git-send-email-afd@ti.com> (raw)

Check if I2C core has been built as a module when BATTERY_BQ27XXX
is built-in. If so disable I2C functionality.

Fixes: 6bd03ce3c12a ("power: bq27xxx_battery: Remove unneeded dependency in Kconfig")
Reported-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Andrew F. Davis <afd@ti.com>
---
 drivers/power/Kconfig | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/power/Kconfig b/drivers/power/Kconfig
index 237d7aa..2f944d7 100644
--- a/drivers/power/Kconfig
+++ b/drivers/power/Kconfig
@@ -166,6 +166,7 @@ config BATTERY_BQ27XXX_I2C
 	bool "BQ27xxx I2C support"
 	depends on BATTERY_BQ27XXX
 	depends on I2C
+	depends on !(I2C=m && BATTERY_BQ27XXX=y)
 	default y
 	help
 	  Say Y here to enable support for batteries with BQ27xxx (I2C) chips.
-- 
1.9.1


             reply	other threads:[~2015-11-09 21:24 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-09 21:23 Andrew F. Davis [this message]
2015-11-09 21:32 ` [PATCH] power: bq27xxx_battery: Add I2C module check dependency in Kconfig Arnd Bergmann
2015-11-10  3:50 ` Sebastian Reichel

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=1447104183-13556-1-git-send-email-afd@ti.com \
    --to=afd@ti.com \
    --cc=arnd@arndb.de \
    --cc=dbaryshkov@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=jencce.kernel@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@vger.kernel.org \
    --cc=pali.rohar@gmail.com \
    --cc=sre@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