Received: by 2002:a25:824b:0:0:0:0:0 with SMTP id d11csp1048193ybn; Wed, 25 Sep 2019 11:32:40 -0700 (PDT) X-Google-Smtp-Source: APXvYqxp6eXvw95gcN+ja+137s70RI1xsL9ioSuc75jtHiZsR1xgdQDvp2pnRJnp/iXh08dKYdab X-Received: by 2002:a17:906:90c1:: with SMTP id v1mr547249ejw.259.1569436360765; Wed, 25 Sep 2019 11:32:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1569436360; cv=none; d=google.com; s=arc-20160816; b=KU/9npVLwhBtmZczLXnAJp6Vg36t/attnNf1suvSidChTYWYP5cAGkRo2onDehfIY0 ScvLUypXecFib7jS/hxcOFQoAHbBaYYixb3/OpEjWw3n6yX64KHchtP4r3YTSVvIlxvS B8r90TW5tBNqMQAiHkEII/QQ9k4zJLzBAXgf+LdnxNrabYhCr+v32wt1SoWZ8/5/VQKN 65YZRSghGWezwUNCu7EuhW/E4/DUZ9xn/miBUpEyAwknhMDxex3+dIDncnBXkzoXFUCh rSAhd1gdZGHYdDH3RdIUmS3jDyYYFrHa6LpQPLBPHsf44uEO21GYK0GH6akOCalhcXck pulQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=id+RxdH9uOIZ369mgSZirPK2kdydWViubQDk+GNf1q8=; b=BqgEbxnfjMMBvltv+ZL936Y+dNvi7OmLCzlEKfIXsDhgiGfKaHhJ4zdujwYeKPwxVW OJiTRo7ilwte9EW9qC5qSWKMmjuqikAaA6WjBkKJqKgffeAGMFUKpWRCRuqOHKD8G2qy zywPObshO4u32ShiYLy/RYKVmHj+ScGdzsxki69F2lUKUV6wlo4w8ZujkLh/keNKRUU5 eQI4pYflLnWkcCl5l53GC7DsFwbQSiTTpEiWkxawrNx5U5G49VMA+bu/bVfcMcg/zgf+ as/0E6quoDVrD+ibEWdBh59YFyGssUl6MEvDLOthOHSePfQZdVuK+/VPgLzFvFUOsQCv +9EA== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id b26si211514eju.87.2019.09.25.11.32.12; Wed, 25 Sep 2019 11:32:40 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2437947AbfIWOd3 (ORCPT + 99 others); Mon, 23 Sep 2019 10:33:29 -0400 Received: from foss.arm.com ([217.140.110.172]:43344 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2437427AbfIWOd3 (ORCPT ); Mon, 23 Sep 2019 10:33:29 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 438731000; Mon, 23 Sep 2019 07:33:28 -0700 (PDT) Received: from [10.1.196.133] (e112269-lin.cambridge.arm.com [10.1.196.133]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id A8F293F59C; Mon, 23 Sep 2019 07:33:26 -0700 (PDT) Subject: Re: [PATCH] arm64: dts: mt8183: Add node for the Mali GPU To: Alyssa Rosenzweig , Nicolas Boichat Cc: Mark Rutland , devicetree@vger.kernel.org, Dominik Behr , "linux-kernel@vger.kernel.org" , Douglas Anderson , Rob Herring , "moderated list:ARM/Mediatek SoC support" , Boris Brezillon , Matthias Brugger , Nick Fan , "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE" References: <20190905081546.42716-1-drinkcat@chromium.org> <20190913181729.GB3115@kevin> <20190919123243.GA3457@kevin> From: Steven Price Message-ID: <3dfa9e3c-9a78-90d1-68c9-7b64a3d734e4@arm.com> Date: Mon, 23 Sep 2019 15:33:25 +0100 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190919123243.GA3457@kevin> Content-Type: text/plain; charset=windows-1252 Content-Language: en-GB Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 19/09/2019 13:32, Alyssa Rosenzweig wrote: >>> By the time MT8183 shows up in more concrete devices, it will, certainly >>> in kernel-space and likely in userspace as well. At present, the DDK can >>> be modified to run on top of the in-tree Mali drivers, i.e. "Bifrost on >>> mainline linux-next (+ page table/compatible patches), with blob >>> userspace". Actually most(?) Bifrost GPUs support the "legacy" 'LPAE-ish' page table format. So the only kernel change *required* is adding the compatible string (and any SoC-specific quirks). The support for "blob-on-Panfrost" is currently an experimental internal investigation. So I can't make any promises about it ever being released publicly. >>> While the open userspace isn't ready here quite yet, I would definitely >>> encourage upstream kernel for ChromeOS, since then there's no need to >>> maintain the out-of-tree GPU driver. >> >> That's an interesting idea, I had no idea, thanks for the info! >> >> Would that work with midgard as well? We have released hardware with >> RK3288/3399, so it might be nice to experiment with these first. > > Yes, the above would work with Midgard as well with no changes needed. > Ping Steven about thtat (CC'd). Indeed since it's the same kernel driver the same compatibility layer can be used to run Midgard DDK blob on Panfrost. Although given the progress that has already occurred with the Mesa Panfrost user space you might be able to simply switch to a completely open stack (available now). Again I'm afraid I'm not in a position to give any guarantees that my prototype blob-on-Panfrost work will actually be released or timescales of when. However since the current focus internally is on newer GPUs I'm less confident that there will be interest for Midgard DDK on Panfrost. Steve >>> More immediately, per Rob's review, it's important that the bindings >>> accepted upstream work with the in-tree Bifrost driver. Conceptually, >>> once Mesa supports Bifrost, if I install Debian on a MT8183 board, >>> everything should just work. I shouldn't need MT-specific changes / need >>> to change names for the DT. Regardless of which kernel driver you end up >>> using, minimally sharing the DT is good for everyone :-) >> >> Yes. I'll try to dig further with MTK, but this may take some time. > > Thank you! > > > _______________________________________________ > linux-arm-kernel mailing list > linux-arm-kernel@lists.infradead.org > http://lists.infradead.org/mailman/listinfo/linux-arm-kernel >