From: Alim Akhtar <alim.akhtar@samsung.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Krzysztof Kozlowski <k.kozlowski@samsung.com>
Cc: olof@lixom.net, linux-arm-kernel@lists.infradead.org,
arnd@arndb.de, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] arm64: defconfig: Enable samsung MFD and related configs
Date: Thu, 04 Feb 2016 09:32:14 +0530 [thread overview]
Message-ID: <56B2CD46.6070607@samsung.com> (raw)
In-Reply-To: <20151106163743.GA7637@e104818-lin.cambridge.arm.com>
On 11/06/2015 10:07 PM, Catalin Marinas wrote:
> On Fri, Nov 06, 2015 at 02:47:12PM +0900, Krzysztof Kozlowski wrote:
>> 2015-11-06 14:27 GMT+09:00 Alim Akhtar <alim.akhtar@samsung.com>:
>>> Exynos7 based espresso board uses S2MPS15, a multifunction device.
>>> This patch enables S2MPS1X regulator, pmic-clk and rtc drivers utilized by
>>> the same.
>>>
>>> Signed-off-by: Alim Akhtar <alim.akhtar@samsung.com>
>>> ---
>>> Changes since v1:
>>> * updated the comment message to describe which platfrom uses it.
>>> * enable COMMON_CLK_S2MPS11 which is needed to enable pmic-clk block.
>>>
>>> arch/arm64/configs/defconfig | 4 ++++
>>> 1 file changed, 4 insertions(+)
>>
>> Reviewed-by: Krzysztof Kozlowski <k.kozlowski@samsung.com>
>>
>> Catalin,
>>
>> Are you usually taking such arm64 defconfig changes or should they go
>> through arm-soc?
>
> Usually arm-soc but I don't mind either way.
>
Looks like this patch is not merged...because of this 4.5-rc1 on
exynos7-esspreso does not boot to user space.
Do I need to resend this patch?
Regards,
Alim
next prev parent reply other threads:[~2016-02-04 4:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-06 5:27 [PATCH v2] arm64: defconfig: Enable samsung MFD and related configs Alim Akhtar
2015-11-06 5:47 ` Krzysztof Kozlowski
2015-11-06 16:37 ` Catalin Marinas
2016-02-04 4:02 ` Alim Akhtar [this message]
2016-02-05 1:36 ` 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=56B2CD46.6070607@samsung.com \
--to=alim.akhtar@samsung.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=k.kozlowski@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).