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=-3.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED,USER_AGENT_GIT 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 215ACC5DF64 for ; Wed, 6 Nov 2019 10:00:05 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id F14652173B for ; Wed, 6 Nov 2019 10:00:04 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1731766AbfKFKAE (ORCPT ); Wed, 6 Nov 2019 05:00:04 -0500 Received: from mx2.suse.de ([195.135.220.15]:51484 "EHLO mx1.suse.de" rhost-flags-OK-OK-OK-FAIL) by vger.kernel.org with ESMTP id S1731731AbfKFKAC (ORCPT ); Wed, 6 Nov 2019 05:00:02 -0500 X-Virus-Scanned: by amavisd-new at test-mx.suse.de Received: from relay2.suse.de (unknown [195.135.220.254]) by mx1.suse.de (Postfix) with ESMTP id 42CCAAFE3; Wed, 6 Nov 2019 10:00:01 +0000 (UTC) From: Nicolas Saenz Julienne To: catalin.marinas@arm.com, linux-kernel@vger.kernel.org Cc: Nicolas Saenz Julienne , devicetree@vger.kernel.org, bcm-kernel-feedback-list@broadcom.com, linux-rpi-kernel@lists.infradead.org, linux-arm-kernel@lists.infradead.org Subject: [PATCH v2 0/2] arm64: Fix CMA/crashkernel reservation Date: Wed, 6 Nov 2019 10:59:43 +0100 Message-Id: <20191106095945.22933-1-nsaenzjulienne@suse.de> X-Mailer: git-send-email 2.23.0 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org As pointed out by Qian Cai[1] the series enabling ZONE_DMA in arm64 breaks CMA/crashkernel reservations on large devices, as it changed its default placement. After discussing it with Catalin Marinas we're restoring the old behavior. The Raspberry Pi 4, being the only device that needs CMA and crashkernel in ZONE_DMA will explicitly do so trough it's device tree. [1] https://lkml.org/lkml/2019/10/21/725 --- Changes since v1: - Move CMA area registration into bcm2711.dtsi Nicolas Saenz Julienne (2): ARM: dts: bcm2711: force CMA into first GB of memory arm64: mm: reserve CMA and crashkernel in ZONE_DMA32 arch/arm/boot/dts/bcm2711.dtsi | 20 ++++++++++++++++++++ arch/arm64/mm/init.c | 4 ++-- 2 files changed, 22 insertions(+), 2 deletions(-) -- 2.23.0