From: Kevin Hilman <khilman@kernel.org>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: Tyler Baker <tyler.baker@linaro.org>,
linux-arm-kernel@lists.infradead.org, arm@kernel.org,
linux-samsung-soc@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>,
'Olof Johansson' <olof@lixom.net>
Subject: Re: [PATCH] ARM: multi_v7_defconfig: fix failure setting CPU voltage by enabling dependent I2C controller
Date: Wed, 19 Nov 2014 09:40:07 -0800 [thread overview]
Message-ID: <7hbno3w0lk.fsf@deeprootsystems.com> (raw)
In-Reply-To: <546C4BA1.6090701@samsung.com> (Kukjin Kim's message of "Wed, 19 Nov 2014 16:49:53 +0900")
Kukjin Kim <kgene.kim@samsung.com> writes:
> On 11/19/14 04:10, Tyler Baker wrote:
>
> Hi,
>
> + Arnd, Olof and Kevin
>
>> This patch fixes a long standing issue introduced during the 3.16 merge window.
>> Shortly after the merge, exynos5250-based arndale boards began to produce the
>> following errors:
>>
>> kern.err kernel: exynos-cpufreq exynos-cpufreq: failed to set cpu voltage
>> kern.err kernel: cpufreq: __target_index: Failed to change cpu frequency: -22
>>
>> Further analysis revealed that the S5M8767 voltage regulator used on the
>> exynos5250-based arndale board utilizes the S3C2410 I2C controller. If the
>> S3C2410 I2C controller driver is not enabled, the S5M8767 voltage regulator
>> fails to probe. Therefore a dependency exists between these two drivers.
>> In the exynos_defconfig both CONFIG_REGULATOR_S5M8767 and CONFIG_I2C_S3C2410
>> options are enabled, and no errors are produced. However, in the
>> multi_v7_defconfig only the CONFIG_REGULATOR_S5M8767 option is enabled and the
>> errors are present. So let's enable the CONFIG_I2C_S3C2410 option in the
>> multi_v7_defconfig to allow the S5M8767 voltage regulator to probe.
>>
>> Signed-off-by: Tyler Baker <tyler.baker@linaro.org>
>
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
Applied to arm-soc/fixes, which is merged into arm-soc/for-next.
Thanks,
Kevin
WARNING: multiple messages have this Message-ID (diff)
From: khilman@kernel.org (Kevin Hilman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: multi_v7_defconfig: fix failure setting CPU voltage by enabling dependent I2C controller
Date: Wed, 19 Nov 2014 09:40:07 -0800 [thread overview]
Message-ID: <7hbno3w0lk.fsf@deeprootsystems.com> (raw)
In-Reply-To: <546C4BA1.6090701@samsung.com> (Kukjin Kim's message of "Wed, 19 Nov 2014 16:49:53 +0900")
Kukjin Kim <kgene.kim@samsung.com> writes:
> On 11/19/14 04:10, Tyler Baker wrote:
>
> Hi,
>
> + Arnd, Olof and Kevin
>
>> This patch fixes a long standing issue introduced during the 3.16 merge window.
>> Shortly after the merge, exynos5250-based arndale boards began to produce the
>> following errors:
>>
>> kern.err kernel: exynos-cpufreq exynos-cpufreq: failed to set cpu voltage
>> kern.err kernel: cpufreq: __target_index: Failed to change cpu frequency: -22
>>
>> Further analysis revealed that the S5M8767 voltage regulator used on the
>> exynos5250-based arndale board utilizes the S3C2410 I2C controller. If the
>> S3C2410 I2C controller driver is not enabled, the S5M8767 voltage regulator
>> fails to probe. Therefore a dependency exists between these two drivers.
>> In the exynos_defconfig both CONFIG_REGULATOR_S5M8767 and CONFIG_I2C_S3C2410
>> options are enabled, and no errors are produced. However, in the
>> multi_v7_defconfig only the CONFIG_REGULATOR_S5M8767 option is enabled and the
>> errors are present. So let's enable the CONFIG_I2C_S3C2410 option in the
>> multi_v7_defconfig to allow the S5M8767 voltage regulator to probe.
>>
>> Signed-off-by: Tyler Baker <tyler.baker@linaro.org>
>
> Acked-by: Kukjin Kim <kgene.kim@samsung.com>
Applied to arm-soc/fixes, which is merged into arm-soc/for-next.
Thanks,
Kevin
next prev parent reply other threads:[~2014-11-19 17:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-18 19:10 [PATCH] ARM: multi_v7_defconfig: fix failure setting CPU voltage by enabling dependent I2C controller Tyler Baker
2014-11-18 19:10 ` Tyler Baker
2014-11-19 7:49 ` Kukjin Kim
2014-11-19 7:49 ` Kukjin Kim
2014-11-19 17:40 ` Kevin Hilman [this message]
2014-11-19 17:40 ` Kevin Hilman
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=7hbno3w0lk.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
--cc=tyler.baker@linaro.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.