From patchwork Fri Jan 15 11:45:42 2021 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Quentin Perret X-Patchwork-Id: 1426931 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=pass (sender SPF authorized) smtp.mailfrom=vger.kernel.org (client-ip=23.128.96.18; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=pass (p=reject dis=none) header.from=google.com Authentication-Results: ozlabs.org; dkim=pass (2048-bit key; unprotected) header.d=google.com header.i=@google.com header.a=rsa-sha256 header.s=20161025 header.b=quv2i1zk; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by ozlabs.org (Postfix) with ESMTP id 4DHKCC4C60z9sS8 for ; Fri, 15 Jan 2021 22:46:31 +1100 (AEDT) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726182AbhAOLqa (ORCPT ); Fri, 15 Jan 2021 06:46:30 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:57044 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726091AbhAOLqa (ORCPT ); Fri, 15 Jan 2021 06:46:30 -0500 Received: from mail-qv1-xf4a.google.com (mail-qv1-xf4a.google.com [IPv6:2607:f8b0:4864:20::f4a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 281C6C061757 for ; Fri, 15 Jan 2021 03:45:50 -0800 (PST) Received: by mail-qv1-xf4a.google.com with SMTP id m8so7356573qvt.14 for ; Fri, 15 Jan 2021 03:45:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=sender:date:message-id:mime-version:subject:from:to:cc; bh=A1L5LiBXauTNSiThdiKpn8PiuSiEsdxg7IXuLjvuJiE=; b=quv2i1zkZlwy1Dp26TdFDlOdkrMzdCjPwdHofP6/kJ8sMM2YlaOx2CUK+C+xMaeCcC wiYqUlER9Y68k4CGt/pkNbnTPZXwJgl2hgUIw186/H7EkDLChdsSYp7hntFw2G2bBwj6 HsbKZHCLS94PSlGncDsBfIm5UMR66O9MSlyJGCzIWh3g/MUjuL7aQlG2HuOYLMEdRaVY jnsXXd1Lu3RKEwzbNeQAz4JpIRigk4R00jCj7TS3SheFiAe3c7E3IuXkBf5lZ+xsuj8+ USW7iakliYd2dlHltzTIbqAJj5pNmWuRZ/FZnUQG5VdnzWI18o/BJS/RrAxFTXTAWJuH dnqA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:message-id:mime-version:subject:from :to:cc; bh=A1L5LiBXauTNSiThdiKpn8PiuSiEsdxg7IXuLjvuJiE=; b=rtirHVzV3hJjDMCFk+AaGtVQrz5MmMVUhHx0537VUuYHdKo5CzYjrZWZ/YSrUwGfQ3 tpmh26CQpy8FqXPEjE9B2svgE3Ji2cqlVO/JE2gDM4tbj2XnCVpp65ckdaPfS9Zf/6L/ Tn79UCk827ZwPkn80BeFj0U0UO0cNCA0rSfzYh3erkrWpbnBKsD36cA2iJNrWH/eS0ML KLkd+IrT+oOg1fbQCi3Xv9MP3ONysQHWiz5fHSlEqk4Y8XM/7cTtw6j3YqvHRLa6gyx0 ELrMvczeRTFL18O1jmddJbWxLXE1pamEnAaUJcpRvvZCwr3rTaq3WCPLLIQAIU45gtWD xnjQ== X-Gm-Message-State: AOAM532f2n9oIb7WI8iKQC1QSjmgugo+OzH3bjC2wv2Xd1ZsldHp9gKv 5ZH4/wvH2lkD5enrf4zW7WYaQUQHEHje X-Google-Smtp-Source: ABdhPJzmRzMTYsK6JufS+gg1o2UjoLxakUX7PNu5dhXrEwOvB0uPXPmlthwFWXtHETHU1JpMEW26vrHLVvFe Sender: "qperret via sendgmr" X-Received: from r2d2-qp.c.googlers.com ([fda3:e722:ac3:cc00:28:9cb1:c0a8:1652]) (user=qperret job=sendgmr) by 2002:a0c:99c8:: with SMTP id y8mr11358708qve.35.1610711148511; Fri, 15 Jan 2021 03:45:48 -0800 (PST) Date: Fri, 15 Jan 2021 11:45:42 +0000 Message-Id: <20210115114544.1830068-1-qperret@google.com> Mime-Version: 1.0 X-Mailer: git-send-email 2.30.0.284.gd98b1dd5eaa7-goog Subject: [PATCH 0/2] fdt: A couple of no-map fixes From: Quentin Perret To: robh+dt@kernel.org, frowand.list@gmail.com Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, drinkcat@chromium.org, swboyd@chromium.org, f.fainelli@gmail.com, karahmed@amazon.de, kernel-team@android.com Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org In the context of a KVM/arm64 thread [1], it became apparent that the difference in behaviour of EFI and DT with respect to no-map regions was something worth fixing. Rob pointed out in that thread that a couple of patches in this area had been sent but still needed to be integrated together, which is basically what this series attempts to do. - Patch 01 is a generic fix that should make sense on its own; - Patch 02 allows the kernel to have a saner behaviour with a broken DT. This one had a small rebase conflict (caused by patch 01). I tested it in qemu and everything is looking good, the error message shows up in dmesg when it should. Thanks, Quentin [1] https://lore.kernel.org/kvmarm/20210108121524.656872-1-qperret@google.com/ KarimAllah Ahmed (1): fdt: Properly handle "no-map" field in the memory region Nicolas Boichat (1): of/fdt: Make sure no-map does not remove already reserved regions drivers/of/fdt.c | 12 ++++++++++-- 1 file changed, 10 insertions(+), 2 deletions(-)