Received: by 2002:a05:6a10:8c0a:0:0:0:0 with SMTP id go10csp375138pxb; Thu, 25 Feb 2021 05:05:35 -0800 (PST) X-Google-Smtp-Source: ABdhPJzP8w9W1NDtR/slOn1l88gVgC5bE+2VE6E7aOL+CF5oMDxkIOoPVxebUl8PS1UIOiavxYV+ X-Received: by 2002:a05:6402:78e:: with SMTP id d14mr2681071edy.171.1614258335540; Thu, 25 Feb 2021 05:05:35 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1614258335; cv=none; d=google.com; s=arc-20160816; b=Xbc2fSm8TM79YNhq8qfsR3brMjMOQ669Uv+hD1Fq9o5n5VWCLa1fkXEO6MvMAgGQDt s/KKL6UmCmD/SW2ZbXaV13bobIZDxXLt15vXCuOBPkEMfhCqRsfWaTUiykxLQbWJ1Qvx xo9OwHQp/B/xyQPupBqQ6RMORR8+lt7IF1Oen37dJRddv4CgPHqZudNRfPvy0oCPBPqb Klg86TW6kmTtB6+lsNG8DeU11QOw5+XUVYj8+sEEL1ZNBYob7nUNyPF7trVHBG2CPq08 w8FdH0BjHwtRq+4PB7izOwXrKloMX7xP9mRZ0t95Am0yEWVrSjXAn/BNbXOy37/Iyrq4 8zxA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=mgBjERR5FlWbd8YLt7hztUxH1RAllPzxXDW6CHF0J2E=; b=SXlGE6z4NEU5Nq60+uZ11sG4amvW5DKA6dH0Li32q3QgdUFpXYb8HhBJ3EviMp2ZTO KxMNS8uZXPxpeI8PabxzhkhqCKY8ypaaL+qpgpEADl25TgLIJBlI0ZvGJHJo+3501cXC kINtCvXEzZXxkeFnxdrs4TKVrVYuYHM9vNzL+vJBYzHTguUoVpl5e8OLhcd5GWa1LxZz 9geS0BcMUfmiyTw1ZT6/KvbRpsBN3iczsb7ajHkhdKAKN6cwV+iqZWNMAWDB3ujz82Sf hLyoCdR1zXv8BHTK3vZSReO30a6rXkqwAshs8TeeEnGq1a1Vfu/7d++ACaBhSUzLYzjR vdyw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="lC9MrLm/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id g19si3263230ejr.741.2021.02.25.05.05.11; Thu, 25 Feb 2021 05:05:35 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=k20201202 header.b="lC9MrLm/"; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230498AbhBYNAX (ORCPT + 99 others); Thu, 25 Feb 2021 08:00:23 -0500 Received: from mail.kernel.org ([198.145.29.99]:53788 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229498AbhBYNAO (ORCPT ); Thu, 25 Feb 2021 08:00:14 -0500 Received: by mail.kernel.org (Postfix) with ESMTPSA id 6A01764EFA; Thu, 25 Feb 2021 12:59:29 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1614257972; bh=sVUg7LiguqcAc8O/ICFWYVfi3WzvdjvcCH+R66oxjlk=; h=From:To:Cc:Subject:Date:From; b=lC9MrLm/fRZoB0WLRNBw/KxUmlpZgIY8aDrybkAQuCAHogZHj5NKB4MZ4fkRPZEN8 kZfN8GEMe0l80eC1zj+/kDnKvIZaDIdOukn0640F1YTbeusEFccn1IU67uiF4BK9mY 7qwv04zcrXkLFhgx8fZ7HpFSD68c7URzRttq29JNf+aK17lNWyiwhrrMq2s7zaz246 sQxuTNqXDM6gYAObki0QGn4Gj+h25t6t6+6vt4kPwcWQCxaVb5JaTJ++2zTR3+6pn5 WxAeoXlCzLbN8vmcldJaRSUL9SR3dgl5LqAq4GSzWYITJko9ijyRTui/XB/FOZepoz ZrcSaMf4VWqXA== From: Will Deacon To: linux-kernel@vger.kernel.org Cc: Will Deacon , Max Uvarov , Rob Herring , Ard Biesheuvel , Marc Zyngier , Doug Anderson , Tyler Hicks , Frank Rowand , Arnd Bergmann , Palmer Dabbelt , Greg Kroah-Hartman , Catalin Marinas , kernel-team@android.com, linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org Subject: [PATCH 0/2] Fix CMDLINE_EXTEND handling for FDT "bootargs" Date: Thu, 25 Feb 2021 12:59:19 +0000 Message-Id: <20210225125921.13147-1-will@kernel.org> X-Mailer: git-send-email 2.20.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi folks, We recently [1] enabled support for CMDLINE_EXTEND on arm64, however when I started looking at replacing Android's out-of-tree implementation [2] with the upstream version, I noticed that the two behave significantly differently: Android follows the Kconfig help text of appending the bootloader arguments to the kernel command line, whereas upstream appends the kernel command line to the bootloader arguments. That is, except for the EFI stub, which follows the documented behaviour. I think the documented behaviour is more useful, so this patch series reworks the FDT code to follow that and updates the very recently merged arm64 idreg early command-line parsing as well. I'd like to take the first patch as a fix via the arm64 tree. Cheers, Will [1] https://lore.kernel.org/r/160650434702.20875.12520970127987518808.b4-ty@arm.com [2] https://android-review.googlesource.com/c/kernel/common/+/841045 --->8 Cc: Max Uvarov Cc: Rob Herring Cc: Ard Biesheuvel Cc: Marc Zyngier Cc: Doug Anderson Cc: Tyler Hicks Cc: Frank Rowand Cc: Arnd Bergmann Cc: Palmer Dabbelt Cc: Greg Kroah-Hartman Cc: Catalin Marinas Cc: Cc: Cc: Will Deacon (2): arm64: cpufeatures: Fix handling of CONFIG_CMDLINE for idreg overrides of/fdt: Append bootloader arguments when CMDLINE_EXTEND=y arch/arm64/kernel/idreg-override.c | 44 +++++++++++--------- drivers/of/fdt.c | 64 ++++++++++++++++++------------ 2 files changed, 64 insertions(+), 44 deletions(-) -- 2.30.1.766.gb4fecdf3b7-goog