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 Received: from gabe.freedesktop.org (gabe.freedesktop.org [131.252.210.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id A5E25C761A6 for ; Tue, 4 Apr 2023 16:36:44 +0000 (UTC) Received: from gabe.freedesktop.org (localhost [127.0.0.1]) by gabe.freedesktop.org (Postfix) with ESMTP id 25EE810E713; Tue, 4 Apr 2023 16:36:44 +0000 (UTC) Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by gabe.freedesktop.org (Postfix) with ESMTPS id 2A55E10E70F; Tue, 4 Apr 2023 16:36:42 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1680626202; x=1712162202; h=date:from:to:cc:subject:message-id:references: mime-version:content-transfer-encoding:in-reply-to; bh=9RHZYBOwNCmxW0n+VSk5Tp91iJJEX/1/7wfuZN6b2MQ=; b=WIRMFTqXzQnSfdGMdQRPd8h9sj8BHT8t52d5MDTZ1IyFMz568F9nQd1+ pyp34Gph+xVJ/woPGS8vjorY/WhAa7SOrB7ni5TJTi0wmHGy++NG5VXJD ddwEyQhSmUt5bPgEJ7LBgjvBu95L5HsrQUxa7UemsxsloF4zujwxvuvLY XTLeCABT4G1Zbs95+QWRLRm82Du9WZTrtOs/wOj7ooVKGtFJopRWGd0+c P6ILC06bXr0Thr/0XXONmNJDMIfnBaWrCfSka8bs+SjBENn25xcHLpAIT UJ/N1vqb57PFIjR5YsA3olnbSM0Y+WjYc2815nrDorTQp9stKSFc5iIaX Q==; X-IronPort-AV: E=McAfee;i="6600,9927,10670"; a="370056573" X-IronPort-AV: E=Sophos;i="5.98,318,1673942400"; d="scan'208";a="370056573" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Apr 2023 09:36:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6600,9927,10670"; a="686425869" X-IronPort-AV: E=Sophos;i="5.98,318,1673942400"; d="scan'208";a="686425869" Received: from vferra-mobl1.ger.corp.intel.com (HELO intel.com) ([10.252.53.196]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 04 Apr 2023 09:36:36 -0700 Date: Tue, 4 Apr 2023 18:36:09 +0200 From: Andi Shyti To: Nirmoy Das Message-ID: References: <20230404143100.10452-1-nirmoy.das@intel.com> <20230404143100.10452-2-nirmoy.das@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-15 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <20230404143100.10452-2-nirmoy.das@intel.com> Subject: Re: [Intel-gfx] [PATCH 2/5] drm/i915/display: Set I915_BO_ALLOC_USER for fb X-BeenThere: intel-gfx@lists.freedesktop.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Intel graphics driver community testing & development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Cc: Jani Nikula , intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org, Matthew Auld , Andrzej Hajda Errors-To: intel-gfx-bounces@lists.freedesktop.org Sender: "Intel-gfx" Hi Nirmoy, On Tue, Apr 04, 2023 at 04:30:57PM +0200, Nirmoy Das wrote: > Framebuffer is exposed to userspace so make sure we set > proper flags for it. Set I915_BO_PREALLOC for prealloced > fb so that ttm won't clear existing data. > > Cc: Matthew Auld > Cc: Andi Shyti > Cc: Andrzej Hajda > Cc: Ville Syrjälä > Cc: Jani Nikula > Cc: Imre Deak > Signed-off-by: Nirmoy Das Reviewed-by: Andi Shyti Thanks, Andi