From: Pavel Fedin <p.fedin@samsung.com>
To: 'Krzysztof Kozlowski' <k.kozlowski@samsung.com>,
'Kukjin Kim' <kgene@kernel.org>,
arm@kernel.org, 'Arnd Bergmann' <arnd@arndb.de>,
'Olof Johansson' <olof@lixom.net>,
'Kevin Hilman' <khilman@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-samsung-soc@vger.kernel.org
Subject: RE: [GIT PULL 4/5] Late Samsung driver updates for v4.4
Date: Wed, 28 Oct 2015 11:00:45 +0300 [thread overview]
Message-ID: <000801d11156$c0e0c270$42a24750$@samsung.com> (raw)
In-Reply-To: <56307FEA.6090207@samsung.com>
Hello!
> The Exynos5410 in current form does not have suspend capability. During
> boot you should see in dmesg:
> Failed to find PMU node
> coming from mach-exynos/suspend.c.
Indeed. By the way, can this be a reason why reboot stopped working? It worked in v4.1. Isn't this a regression?
Ok, nevertheless, here is v3 of my patchset.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
WARNING: multiple messages have this Message-ID (diff)
From: p.fedin@samsung.com (Pavel Fedin)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL 4/5] Late Samsung driver updates for v4.4
Date: Wed, 28 Oct 2015 11:00:45 +0300 [thread overview]
Message-ID: <000801d11156$c0e0c270$42a24750$@samsung.com> (raw)
In-Reply-To: <56307FEA.6090207@samsung.com>
Hello!
> The Exynos5410 in current form does not have suspend capability. During
> boot you should see in dmesg:
> Failed to find PMU node
> coming from mach-exynos/suspend.c.
Indeed. By the way, can this be a reason why reboot stopped working? It worked in v4.1. Isn't this a regression?
Ok, nevertheless, here is v3 of my patchset.
Kind regards,
Pavel Fedin
Expert Engineer
Samsung Electronics Research center Russia
next prev parent reply other threads:[~2015-10-28 8:00 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-23 21:18 [GIT PULL 1/5] Late Samsung DT updates for v4.4 Kukjin Kim
2015-10-23 21:18 ` Kukjin Kim
2015-10-23 21:21 ` [GIT PULL 2/5] Late Samsung DT64 update " Kukjin Kim
2015-10-23 21:21 ` Kukjin Kim
2015-10-26 1:18 ` Olof Johansson
2015-10-26 1:18 ` Olof Johansson
2015-10-23 21:23 ` [GIT PULL 3/5] Late Samsung SoC updates " Kukjin Kim
2015-10-23 21:23 ` Kukjin Kim
2015-10-26 1:19 ` Olof Johansson
2015-10-26 1:19 ` Olof Johansson
2015-10-23 21:26 ` [GIT PULL 4/5] Late Samsung driver " Kukjin Kim
2015-10-23 21:26 ` Kukjin Kim
2015-10-28 7:37 ` Krzysztof Kozlowski
2015-10-28 7:37 ` Krzysztof Kozlowski
2015-10-28 7:49 ` Pavel Fedin
2015-10-28 7:49 ` Pavel Fedin
2015-10-28 7:57 ` Krzysztof Kozlowski
2015-10-28 7:57 ` Krzysztof Kozlowski
2015-10-28 8:00 ` Pavel Fedin [this message]
2015-10-28 8:00 ` Pavel Fedin
2015-10-28 8:05 ` Krzysztof Kozlowski
2015-10-28 8:05 ` Krzysztof Kozlowski
2015-10-28 9:02 ` Pavel Fedin
2015-10-28 9:02 ` Pavel Fedin
2015-10-31 2:12 ` Olof Johansson
2015-10-31 2:12 ` Olof Johansson
2015-10-23 21:27 ` [GIT PULL 5/5] Late Samsung defconfig " Kukjin Kim
2015-10-23 21:27 ` Kukjin Kim
2015-10-26 1:21 ` Olof Johansson
2015-10-26 1:21 ` Olof Johansson
2015-10-26 1:17 ` [GIT PULL 1/5] Late Samsung DT " Olof Johansson
2015-10-26 1:17 ` Olof Johansson
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='000801d11156$c0e0c270$42a24750$@samsung.com' \
--to=p.fedin@samsung.com \
--cc=arm@kernel.org \
--cc=arnd@arndb.de \
--cc=k.kozlowski@samsung.com \
--cc=kgene@kernel.org \
--cc=khilman@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/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.