From: Alyssa Rosenzweig <alyssa.rosenzweig@collabora.com>
To: Nicolas Boichat <drinkcat@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Nick Fan <nick.fan@mediatek.com>,
Boris Brezillon <boris.brezillon@collabora.com>,
Douglas Anderson <dianders@chromium.org>,
Dominik Behr <dbehr@chromium.org>,
Steven Price <steven.price@arm.com>
Subject: Re: [PATCH] arm64: dts: mt8183: Add node for the Mali GPU
Date: Thu, 19 Sep 2019 08:32:43 -0400 [thread overview]
Message-ID: <20190919123243.GA3457@kevin> (raw)
In-Reply-To: <CANMq1KD++==d0Mb6T2gKU1T7c_MaedswOYdxqEqEKKUL1bxgiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1371 bytes --]
> > 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".
> >
> > 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).
> > 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!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-09-19 12:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 8:15 [PATCH] arm64: dts: mt8183: Add node for the Mali GPU Nicolas Boichat
2019-09-05 9:09 ` Rob Herring
2019-09-05 9:49 ` Nicolas Boichat
2019-09-05 10:32 ` Rob Herring
2019-09-13 18:17 ` Alyssa Rosenzweig
2019-09-18 22:16 ` Nicolas Boichat
2019-09-19 12:32 ` Alyssa Rosenzweig [this message]
2019-09-23 14:33 ` Steven Price
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190919123243.GA3457@kevin \
--to=alyssa.rosenzweig@collabora.com \
--cc=boris.brezillon@collabora.com \
--cc=dbehr@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=drinkcat@chromium.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nick.fan@mediatek.com \
--cc=robh+dt@kernel.org \
--cc=steven.price@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).