From: Jon Hunter <jonathanh@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Wolfram Sang <wsa@the-dreams.de>, <linux-i2c@vger.kernel.org>,
<linux-tegra@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] i2c: tegra-bpmp: Enable Tegra BPMP I2C adapter
Date: Fri, 24 Mar 2017 09:30:08 +0000 [thread overview]
Message-ID: <245d5500-5a99-cb76-f72d-16e2ebf3d415@nvidia.com> (raw)
In-Reply-To: <20170320140503.GA28203@ulmo.ba.sec>
On 20/03/17 14:05, Thierry Reding wrote:
> * PGP Signed by an unknown key
>
> On Wed, Mar 15, 2017 at 12:20:10PM +0000, Jon Hunter wrote:
>> Enable the Tegra BPMP I2C adapter by default if the Tegra BPMP itself
>> is enabled. This adapter is used as the I2C interface for the PMIC on
>> the Tegra186 Jetson-TX2 platform.
>>
>> Signed-off-by: Jon Hunter <jonathanh@nvidia.com>
>> ---
>> drivers/i2c/busses/Kconfig | 1 +
>> 1 file changed, 1 insertion(+)
>>
>> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
>> index 8adc0f1d7ad0..9e024ae8a067 100644
>> --- a/drivers/i2c/busses/Kconfig
>> +++ b/drivers/i2c/busses/Kconfig
>> @@ -933,6 +933,7 @@ config I2C_TEGRA
>> config I2C_TEGRA_BPMP
>> tristate "NVIDIA Tegra BPMP I2C controller"
>> depends on TEGRA_BPMP
>> + default y if TEGRA_BPMP
>
> I think "if TEGRA_BPMP" in the line above implies "depends on
> TEGRA_BPMP", so it's redundant. "default y" should be equivalent. That
> said, I'm not sure if we really want to always enable this. There could
> be boards with a BPMP that don't use the I2C controller.
Initially, I had thought about putting a select for this under the
ARCH_TEGRA_186_SOC in drivers/soc/tegra/Kconfig. We could always do that
in the future if it turns out the BPMP does not have i2c on newer chips.
Cheers
Jon
--
nvpublic
prev parent reply other threads:[~2017-03-24 9:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-15 12:20 Jon Hunter
2017-03-20 14:05 ` Thierry Reding
2017-03-24 9:30 ` Jon Hunter [this message]
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=245d5500-5a99-cb76-f72d-16e2ebf3d415@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=thierry.reding@gmail.com \
--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
all inboxes | Powered by JetHome®