[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAMty3ZBcBAHTk5eQU99rRqYm7tQAjtuEaTT_q6J5FYmY=ybvOA@mail.gmail.com>
Date: Mon, 16 Oct 2017 23:43:29 +0530
From: Jagan Teki <jagan@...rulasolutions.com>
To: Heiko Stübner <heiko@...ech.de>
Cc: Jagan Teki <jagannadh.teki@...il.com>,
linux-arm-kernel <linux-arm-kernel@...ts.infradead.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>,
Russell King <linux@...linux.org.uk>,
Michael Trimarchi <michael@...rulasolutions.com>,
linux-rockchip@...ts.infradead.org,
linux-kernel <linux-kernel@...r.kernel.org>,
devicetree <devicetree@...r.kernel.org>
Subject: Re: [PATCH 9/9] ARM: multi_v7_defconfig: Statically build RTC_DRV_RK808
On Mon, Oct 16, 2017 at 11:32 PM, Heiko Stübner <heiko@...ech.de> wrote:
> Hi,
>
> Am Montag, 16. Oktober 2017, 17:46:27 CEST schrieb Jagan Teki:
>> RTC_DRV_RK808 need to have build statically for the platforms
>> do use MFB_RK808 so replace module with statical link.
>
> why would you need this to be compiled on? MFD_RK808 will happily
> just create the platform-devices which are then bound to the RTC
> driver later once the module is ready.
Yeah, that can be true but seems like rk808 need rtc at the
beginning(like boot time) because we observed the boot hang even with
gmac (like one with HDMI [1]) eventually booting continue only when it
linked statically.
[1] https://lkml.org/lkml/2017/9/4/224
thanks!
--
Jagan Teki
Senior Linux Kernel Engineer | Amarula Solutions
U-Boot, Linux | Upstream Maintainer
Hyderabad, India.
Powered by blists - more mailing lists