From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id F3143C2D0DC for ; Thu, 2 Jan 2020 17:09:58 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id D079220866 for ; Thu, 2 Jan 2020 17:09:58 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727728AbgABRJ6 (ORCPT ); Thu, 2 Jan 2020 12:09:58 -0500 Received: from muru.com ([72.249.23.125]:49878 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726125AbgABRJ5 (ORCPT ); Thu, 2 Jan 2020 12:09:57 -0500 Received: from atomide.com (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 418E08087; Thu, 2 Jan 2020 17:10:37 +0000 (UTC) Date: Thu, 2 Jan 2020 09:09:49 -0800 From: Tony Lindgren To: Pavel Machek Cc: kernel list , linux-arm-kernel , linux-omap@vger.kernel.org, sre@kernel.org, nekit1000@gmail.com, mpartap@gmx.net, merlijn@wizzup.org, martin_rysavy@centrum.cz Subject: Re: Droid 4 on 5.5-rc3 Message-ID: <20200102170949.GA16702@atomide.com> References: <20191228162929.GA29269@duo.ucw.cz> <20191228193622.GA13047@duo.ucw.cz> <20191230173507.GM35479@atomide.com> <20200101201132.GA9612@amd> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200101201132.GA9612@amd> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, * Pavel Machek [200101 20:12]: > I tried v5.5-rc4, and it does not boot either. I'm kexecing from > 5.3-rc2. Maybe there's Kconfig difference? This is my... I also tested with your .config and v5.4-rc4 boots just fine for me on two different droid4s. The regulator warning is there with built-in drivers that's probably related to deferred probe and should be fixed though. But wlan and mmc work meaning what you're seeing is not a regulator issue. Regards, Tony