Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4370DC433EF for ; Mon, 13 Dec 2021 06:01:15 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232022AbhLMGBN (ORCPT ); Mon, 13 Dec 2021 01:01:13 -0500 Received: from muru.com ([72.249.23.125]:37936 "EHLO muru.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229452AbhLMGBM (ORCPT ); Mon, 13 Dec 2021 01:01:12 -0500 Received: from localhost (localhost [127.0.0.1]) by muru.com (Postfix) with ESMTPS id 736E3809F; Mon, 13 Dec 2021 06:01:53 +0000 (UTC) Date: Mon, 13 Dec 2021 08:01:09 +0200 From: Tony Lindgren To: Merlijn Wajer Cc: Ivaylo Dimitrov , Dev Null , Sebastian Reichel , linux-omap@vger.kernel.org, Arnd Bergmann , Olof Johansson , soc@kernel.org, Rob Herring , =?utf-8?Q?Beno=C3=AEt?= Cousson , Kees Cook , Anton Vorontsov , Colin Cross , Tony Luck , linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [RFC PATCH 2/2] Droid3: add initial DTS Message-ID: References: <20211212230459.13579-1-merlijn@wizzup.org> <20211212230459.13579-3-merlijn@wizzup.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20211212230459.13579-3-merlijn@wizzup.org> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Merlijn Wajer [211212 23:00]: > @@ -35,7 +35,7 @@ reserved-memory { > * first 512K of that and just overwrite the rest and configure > * only 384K instead of 2M. > */ > - ramoops@a0080000 { > + ramoops0: ramoops@a0080000 { > compatible = "ramoops"; > reg = <0xa0080000 0x60000>; > record-size = <0x20000>; The stock kernel ramoops range might be different here because of less memory. If the stock kernel has it, it should be in the platform data somewhere in the stock kernel sources. Probably best to just leave it out for now. > +// Do don't know if pstore is supported, but the current config causes panics, > +// so delete the node for now > +/delete-node/ &ramoops0; Just leave this out too, I don't think we have the ramoops configured in the mainline kernel. Otherwise looks good to me. Regards, Tony