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=-13.3 required=3.0 tests=BAYES_00,DKIMWL_WL_MED, DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_IN_DEF_DKIM_WL 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 47D1EC433B4 for ; Wed, 12 May 2021 12:34:26 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0AF7D613CA for ; Wed, 12 May 2021 12:34:25 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232514AbhELMfd (ORCPT ); Wed, 12 May 2021 08:35:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36050 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232519AbhELMfb (ORCPT ); Wed, 12 May 2021 08:35:31 -0400 Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id EC5F5C061574 for ; Wed, 12 May 2021 05:34:21 -0700 (PDT) Received: by mail-wm1-x329.google.com with SMTP id b19-20020a05600c06d3b029014258a636e8so2958943wmn.2 for ; Wed, 12 May 2021 05:34:21 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=L3AMrfm7KzdYjAx0MG/kXRzLEqn5TfDInWeiOnoS8A0=; b=wGwwVglhSHA1nu0sddt1O78EWcwn6fB5M95MBU2mYu8yxjZWRmVl4Xk2W/HBVliIQ+ VqbqZ4D3hgvRwEI1eQ0SgoEs1oOuTGok3UPrOy9fE4HVc/V0LQd182Ehxjlb7M/vBxJZ 1RejYqLqgKbdZ0/pTt6wEMHd7BbvNQfmn8aBdO+FGkEvHNyA9co4wkELQmNPARhE1beW 7DK+sIGytXjOYdOJ7HhZNAMAAGxlGbDm3fMt3ulRHEjA9g6MXUa/2FfQ2FELIpeebL8E ythDkvX3BJoH9pQYp67RthOVD/w/EfKqEQnDXyxRkx3Brks5/3IgR1ibdRT56edbosyD Ukpg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=L3AMrfm7KzdYjAx0MG/kXRzLEqn5TfDInWeiOnoS8A0=; b=FcIRrtmsok3xm8I4+48LWGOzPy8odTqg8BEnPFCS4VzzQd0QIus0FfNRhY10VNHB47 gDA0PT7lOvpMzRjac8sLWZzVYxBIT1Z3HSqWPKYTQLU2XP3RRQ3Ese54XgX6ds43B2d1 2B9f5QT0s+q8lYU0olTIC4mZvvhvbW8jRIi9Y75Rg2WWMLXd+mjQHkpLB+WkiGk/Qt/l RKjTClFsbzo33UoC+Lq85WQxSZSFkKBvdoELEppKH9nPmEaCx+JQGjuB5jXzEn8k0100 AUfHiFArtm96fhDAdc5BDhg5fWnU3fRmWnwSois6LzDzTp79e6Zf1o5bIvJUOV6v49ue dqfA== X-Gm-Message-State: AOAM531rrjQoFwytYlz9i7C52UKILY4Z5faAPlQIvy/UWvqjMy81nLvt 7bp6o9tQ/MdMJlkK3M29lyLIcg== X-Google-Smtp-Source: ABdhPJxaogDe/xKEAVJSwlt6+D1vz2gSm4YwiHq4FwR/U+34LWOpQZ6ZvVIPkXLGy3PggDAnBF3Vyw== X-Received: by 2002:a7b:cbc2:: with SMTP id n2mr38803203wmi.69.1620822860514; Wed, 12 May 2021 05:34:20 -0700 (PDT) Received: from google.com (105.168.195.35.bc.googleusercontent.com. [35.195.168.105]) by smtp.gmail.com with ESMTPSA id j10sm30643193wrt.32.2021.05.12.05.34.19 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 12 May 2021 05:34:20 -0700 (PDT) Date: Wed, 12 May 2021 12:34:17 +0000 From: Quentin Perret To: Alexandre TORGUE Cc: Florian Fainelli , Ard Biesheuvel , Rob Herring , Greg Kroah-Hartman , Sasha Levin , stable , Arnd Bergmann , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , Nicolas Boichat , Stephen Boyd , KarimAllah Ahmed , Android Kernel Team , Architecture Mailman List , Frank Rowand , linux-arm-kernel Subject: Re: [v5.4 stable] arm: stm32: Regression observed on "no-map" reserved memory region Message-ID: References: <001f8550-b625-17d2-85a6-98a483557c70@foss.st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org On Wednesday 12 May 2021 at 12:55:53 (+0200), Alexandre TORGUE wrote: > We saw that patches [1] and [2] cause issue on stable version (at least for > 5.4). As you said issue can be seen with above device tree and check in > /proc/iomem than gpu_reserved region is taken by the kernel as "System RAM". > > On v5.10 stream there are no issues seen taking patches [1]&[2] and the > reason is linked to patches [3]&[4] which have been introduced in v5.10.0. > Reverting them give me the same behavior than on stable version. Thanks for confirming. Given that the patches were not really fixes, I think reverting is still the best option. I've sent reverts to -stable for 5.4 and prior: https://lore.kernel.org/stable/20210512122853.3243417-1-qperret@google.com/ Cheers, Quentin