From: Krzysztof Kozlowski <k.kozlowski@samsung.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org
Cc: Kukjin Kim <kgene@kernel.org>, linux-samsung-soc@vger.kernel.org
Subject: Re: [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source
Date: Thu, 28 Jan 2016 17:11:06 +0900 [thread overview]
Message-ID: <56A9CD1A.8010800@samsung.com> (raw)
In-Reply-To: <5671F88F.7050802@samsung.com>
On 17.12.2015 08:49, Krzysztof Kozlowski wrote:
> On 21.10.2015 19:10, Sudeep Holla wrote:
>> Though the keyboard and other driver will continue to support the legacy
>> "gpio-key,wakeup", "linux-keypad,wakeup" boolean property to enable the
>> wakeup source, "wakeup-source" is the new standard binding.
>>
>> This patch replaces all the legacy wakeup properties with the unified
>> "wakeup-source" property in order to avoid any futher copy-paste
>> duplication.
>>
>> Cc: Kukjin Kim <kgene@kernel.org>
>> Cc: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>> Cc: linux-samsung-soc@vger.kernel.org
>> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
>> ---
>> arch/arm/boot/dts/exynos3250-monk.dts | 6 +++---
>> arch/arm/boot/dts/exynos3250-rinato.dts | 6 +++---
>> arch/arm/boot/dts/exynos4210-origen.dts | 10 +++++-----
>> arch/arm/boot/dts/exynos4210-smdkv310.dts | 2 +-
>> arch/arm/boot/dts/exynos4210-trats.dts | 2 +-
>> arch/arm/boot/dts/exynos4210-universal_c210.dts | 4 ++--
>> arch/arm/boot/dts/exynos4412-odroid-common.dtsi | 2 +-
>> arch/arm/boot/dts/exynos4412-odroidx.dts | 2 +-
>> arch/arm/boot/dts/exynos4412-origen.dts | 2 +-
>> arch/arm/boot/dts/exynos4412-smdk4412.dts | 2 +-
>> arch/arm/boot/dts/exynos4412-trats2.dts | 4 ++--
>> arch/arm/boot/dts/exynos5250-arndale.dts | 12 ++++++------
>> arch/arm/boot/dts/exynos5250-snow.dts | 4 ++--
>> arch/arm/boot/dts/exynos5250-spring.dts | 4 ++--
>> arch/arm/boot/dts/exynos5420-arndale-octa.dts | 2 +-
>> arch/arm/boot/dts/exynos5420-peach-pit.dts | 4 ++--
>> arch/arm/boot/dts/exynos5800-peach-pi.dts | 4 ++--
>> 17 files changed, 36 insertions(+), 36 deletions(-)
>>
>> diff --git a/arch/arm/boot/dts/exynos3250-monk.dts b/arch/arm/boot/dts/exynos3250-monk.dts
>> index 540a0adf2be6..b77ea2163a0a 100644
>> --- a/arch/arm/boot/dts/exynos3250-monk.dts
>> +++ b/arch/arm/boot/dts/exynos3250-monk.dts
>> @@ -43,7 +43,7 @@
>> linux,code = <KEY_POWER>;
>> label = "power key";
>> debounce-interval = <10>;
>> - gpio-key,wakeup;
>> + wakeup-source;
>> };
>> };
>>
>> @@ -67,7 +67,7 @@
>> interrupt-parent = <&gpx1>;
>> interrupts = <5 0>;
>> reg = <0x25>;
>> - wakeup;
>> + wakeup-source;
>>
>> muic: max77836-muic {
>> compatible = "maxim,max77836-muic";
>> @@ -184,7 +184,7 @@
>> interrupt-parent = <&gpx0>;
>> interrupts = <7 0>;
>> reg = <0x66>;
>> - wakeup;
>> + wakeup-source;
>>
>> s2mps14_osc: clocks {
>> compatible = "samsung,s2mps14-clk";
>> diff --git a/arch/arm/boot/dts/exynos3250-rinato.dts b/arch/arm/boot/dts/exynos3250-rinato.dts
>> index 41a5fafb9aa9..7acd11d2d957 100644
>> --- a/arch/arm/boot/dts/exynos3250-rinato.dts
>> +++ b/arch/arm/boot/dts/exynos3250-rinato.dts
>> @@ -43,7 +43,7 @@
>> linux,code = <KEY_POWER>;
>> label = "power key";
>> debounce-interval = <10>;
>> - gpio-key,wakeup;
>> + wakeup-source;
>> };
>> };
>>
>> @@ -58,7 +58,7 @@
>> interrupt-parent = <&gpx1>;
>> interrupts = <5 0>;
>> reg = <0x25>;
>> - wakeup;
>> + wakeup-source;
>>
>> muic: max77836-muic {
>> compatible = "maxim,max77836-muic";
>> @@ -245,7 +245,7 @@
>> interrupt-parent = <&gpx0>;
>> interrupts = <7 0>;
>> reg = <0x66>;
>> - wakeup;
>> + wakeup-source;
>
> I think here and in Monk board these four "wakeup" properties are bogus,
> not parsed by driver. Instead wakeup is always initialized to true.
>
> Anyway fixing this is not part of this patch but instead this should be
> fixed in separate commit. Here everything looks good:
>
> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
This patch does not apply. Can you rebase it on linux-next or my next/dt
branch (git://git.kernel.org/pub/scm/linux/kernel/git/krzk/linux.git)?
I applied the 16/19 (s5pv210).
Best regards,
Krzysztof
next prev parent reply other threads:[~2016-01-28 8:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1445422216-29375-1-git-send-email-sudeep.holla@arm.com>
[not found] ` <1445422216-29375-1-git-send-email-sudeep.holla-5wv7dgnIgG8@public.gmane.org>
2015-10-21 10:10 ` [PATCH 12/19] ARM: dts: exynos: replace legacy *,wakeup property with wakeup-source Sudeep Holla
2015-12-15 16:35 ` Sudeep Holla
[not found] ` <56704141.8070308-5wv7dgnIgG8@public.gmane.org>
2015-12-15 23:32 ` Krzysztof Kozlowski
[not found] ` <5670A2F2.5060009-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2015-12-16 10:32 ` Sudeep Holla
2015-12-16 23:38 ` Krzysztof Kozlowski
2015-12-16 23:49 ` Krzysztof Kozlowski
2016-01-28 8:11 ` Krzysztof Kozlowski [this message]
[not found] ` <56A9CD1A.8010800-Sze3O3UU22JBDgjK7y7TUQ@public.gmane.org>
2016-01-28 15:59 ` [UPDATE] " Sudeep Holla
2016-01-29 0:11 ` Krzysztof Kozlowski
2015-10-21 10:10 ` [PATCH 16/19] ARM: dts: s5pv210: " Sudeep Holla
2015-12-15 16:37 ` Sudeep Holla
2015-12-16 23:52 ` Krzysztof Kozlowski
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=56A9CD1A.8010800@samsung.com \
--to=k.kozlowski@samsung.com \
--cc=devicetree@vger.kernel.org \
--cc=kgene@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=sudeep.holla@arm.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