From mboxrd@z Thu Jan 1 00:00:00 1970 From: Sai Prakash Ranjan Subject: Re: Crash in msm serial on dragonboard with ftrace bootargs Date: Fri, 16 Nov 2018 16:19:48 +0530 Message-ID: <6ba6073e-c2ff-193c-3038-8329c06e325c@codeaurora.org> References: <472db11e-49a6-a1ee-e298-791ee1bbb10b@codeaurora.org> <20181016144123.24c47b38@gandalf.local.home> <7781815e-cba2-9e36-db6d-268298747876@codeaurora.org> <20181016150328.3450d718@gandalf.local.home> <20181017223334.29ca2837@vmware.local.home> <58d2474c-53cd-e6cb-2d25-db38d1a88da6@codeaurora.org> <20181018091706.62310b38@gandalf.local.home> <20181019041740.GB141835@joelaf.mtv.corp.google.com> <8a75f2d5-f1bd-504e-b545-ae2e2f61ca8f@codeaurora.org> <20181019095122.0f1c0946@gandalf.local.home> <9cafe321-87f6-98a3-3bda-c2f7a3d7fc67@codeaurora.org> <20181019111205.5c8e98e8@gandalf.local.home> <1e6cc1fa5263b9edfcf7567d3f9f65fd@codeaurora.org> <38099043-f5ed-6d81-bf94-13f61cfa8507@linaro.org> <8f65f83b-8cd9-5e35-c324-30b86390906e@codeaurora.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Viresh Kumar , srinivas.kandagatla@linaro.org Cc: Steven Rostedt , sboyd@kernel.org, joel@joelfernandes.org, bjorn.andersson@linaro.org, Andy Gross , David Brown , Jiri Slaby , Kees Cook , geliangtang@gmail.com, Greg Kroah-Hartman , gpramod@codeaurora.org, linux-arm-msm , "open list:ARM/QUALCOMM SUPPORT" , linux-serial@vger.kernel.org, Linux Kernel Mailing List , Rajendra Nayak , vivek.gautam@codeaurora.org, sibis@codeaurora.org List-Id: linux-arm-msm@vger.kernel.org On 11/16/2018 9:09 AM, Viresh Kumar wrote: > On Thu, Nov 15, 2018 at 4:23 PM Srinivas Kandagatla > wrote: > >> Yes, this is not the solution, but it proves that the hand-off between >> booloaders and kernel is the issue. >> >> In general there is wider issue with resources hand-off between >> bootloader and kernel. >> >> There has been some proposal in the past by Viresh for a new framework >> called boot-constriants (https://lkml.org/lkml/2017/12/14/440) which am >> not sure if its still actively looked at. But something similar should >> be the way to address such issues. > > It isn't dead code yet and I am waiting to gain few more use-cases > before I attempt > to convince Greg again :) > > Here is the code.. > > git://git.kernel.org/pub/scm/linux/kernel/git/vireshk/linux.git boot-constraint > > -- > viresh > Maybe you can take this earlycon issue as a usecase. I have added a boot constraint for earlycon on db410c and have sent a patch. Whenever you repitch boot-constraint, you can add that as well :) Thanks, Sai -- QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, hosted by The Linux Foundation