From: Sudeep Holla <sudeep.holla@arm.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
devicetree@vger.kernel.org, Liviu Dudau <liviu.dudau@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Steven Price <steven.price@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm64: dts: juno: add GPU subsystem
Date: Tue, 1 Oct 2019 15:34:07 +0100 [thread overview]
Message-ID: <20191001143350.GA404@bogus> (raw)
In-Reply-To: <2a3b2fe1-b08a-bc21-6f3b-4a595b51463c@arm.com>
On Tue, Oct 01, 2019 at 01:45:30PM +0100, Robin Murphy wrote:
> On 01/10/2019 09:59, Sudeep Holla wrote:
> > On Mon, Sep 30, 2019 at 12:46:33PM -0500, Rob Herring wrote:
> > > On Mon, Sep 30, 2019 at 10:25 AM Robin Murphy <robin.murphy@arm.com> wrote:
> > > >
> > > > Since we now have bindings for Mali Midgard GPUs, let's use them to
> > > > describe Juno's GPU subsystem, if only because we can. Juno sports a
> > > > Mali-T624 integrated behind an MMU-400 (as a gesture towards
> > > > virtualisation), in their own dedicated power domain with DVFS
> > > > controlled by the SCP.
> > > >
> > > > CC: Liviu Dudau <liviu.dudau@arm.com>
> > > > CC: Sudeep Holla <sudeep.holla@arm.com>
> > > > CC: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> > > > ---
> > > > .../bindings/gpu/arm,mali-midgard.yaml | 5 +++-
> > > > arch/arm64/boot/dts/arm/juno-base.dtsi | 27 +++++++++++++++++++
> > > > 2 files changed, 31 insertions(+), 1 deletion(-)
> > >
> > > Reviewed-by: Rob Herring <robh@kernel.org>
> >
> > If you plan to take it along with driver change,
> >
> > Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> >
> > If not, please let us know. I can take it for v5.5
>
> The driver change is debatable and not strictly necessary, so it probably
> makes more sense to take this one through the VExpress tree on its own. I
> wouldn't suggest flipping the status to "enabled" just yet, but it seems
Sure, make sense.
> worth putting the basic description in place as a jumping-off point for
> folks to hack on (e.g. it's another 'interesting' case for devfreq OPP
> stuff).
IIUC, the devfreq support in panfrost driver should work fine with SCPI
as it has clock provider for GPU DVFS.
With SCMI, we don't want to hook to clock framework, but I am yet to come
up with a sane generic way to add SCMI devfreq and integrate it with the
panfrost devfreq.
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
WARNING: multiple messages have this Message-ID (diff)
From: Sudeep Holla <sudeep.holla@arm.com>
To: Robin Murphy <robin.murphy@arm.com>
Cc: Rob Herring <robh@kernel.org>,
Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
Tomeu Vizoso <tomeu.vizoso@collabora.com>,
devicetree@vger.kernel.org, Liviu Dudau <liviu.dudau@arm.com>,
dri-devel <dri-devel@lists.freedesktop.org>,
Steven Price <steven.price@arm.com>,
Sudeep Holla <sudeep.holla@arm.com>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 1/2] arm64: dts: juno: add GPU subsystem
Date: Tue, 1 Oct 2019 15:34:07 +0100 [thread overview]
Message-ID: <20191001143350.GA404@bogus> (raw)
In-Reply-To: <2a3b2fe1-b08a-bc21-6f3b-4a595b51463c@arm.com>
On Tue, Oct 01, 2019 at 01:45:30PM +0100, Robin Murphy wrote:
> On 01/10/2019 09:59, Sudeep Holla wrote:
> > On Mon, Sep 30, 2019 at 12:46:33PM -0500, Rob Herring wrote:
> > > On Mon, Sep 30, 2019 at 10:25 AM Robin Murphy <robin.murphy@arm.com> wrote:
> > > >
> > > > Since we now have bindings for Mali Midgard GPUs, let's use them to
> > > > describe Juno's GPU subsystem, if only because we can. Juno sports a
> > > > Mali-T624 integrated behind an MMU-400 (as a gesture towards
> > > > virtualisation), in their own dedicated power domain with DVFS
> > > > controlled by the SCP.
> > > >
> > > > CC: Liviu Dudau <liviu.dudau@arm.com>
> > > > CC: Sudeep Holla <sudeep.holla@arm.com>
> > > > CC: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
> > > > Signed-off-by: Robin Murphy <robin.murphy@arm.com>
> > > > ---
> > > > .../bindings/gpu/arm,mali-midgard.yaml | 5 +++-
> > > > arch/arm64/boot/dts/arm/juno-base.dtsi | 27 +++++++++++++++++++
> > > > 2 files changed, 31 insertions(+), 1 deletion(-)
> > >
> > > Reviewed-by: Rob Herring <robh@kernel.org>
> >
> > If you plan to take it along with driver change,
> >
> > Acked-by: Sudeep Holla <sudeep.holla@arm.com>
> >
> > If not, please let us know. I can take it for v5.5
>
> The driver change is debatable and not strictly necessary, so it probably
> makes more sense to take this one through the VExpress tree on its own. I
> wouldn't suggest flipping the status to "enabled" just yet, but it seems
Sure, make sense.
> worth putting the basic description in place as a jumping-off point for
> folks to hack on (e.g. it's another 'interesting' case for devfreq OPP
> stuff).
IIUC, the devfreq support in panfrost driver should work fine with SCPI
as it has clock provider for GPU DVFS.
With SCMI, we don't want to hook to clock framework, but I am yet to come
up with a sane generic way to add SCMI devfreq and integrate it with the
panfrost devfreq.
--
Regards,
Sudeep
next prev parent reply other threads:[~2019-10-01 14:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 15:24 [PATCH 1/2] arm64: dts: juno: add GPU subsystem Robin Murphy
2019-09-30 15:24 ` Robin Murphy
2019-09-30 15:24 ` [PATCH 2/2] drm/panfrost: Use coherent pagetable walk on Juno Robin Murphy
2019-09-30 15:24 ` Robin Murphy
2019-09-30 16:26 ` Steven Price
2019-09-30 16:26 ` Steven Price
2019-09-30 17:52 ` Rob Herring
2019-09-30 17:52 ` Rob Herring
2019-09-30 17:54 ` Robin Murphy
2019-09-30 17:54 ` Robin Murphy
2019-09-30 17:27 ` [PATCH 1/2] arm64: dts: juno: add GPU subsystem Liviu Dudau
2019-09-30 17:27 ` Liviu Dudau
2019-09-30 17:46 ` Rob Herring
2019-09-30 17:46 ` Rob Herring
2019-10-01 8:59 ` Sudeep Holla
2019-10-01 8:59 ` Sudeep Holla
2019-10-01 12:45 ` Robin Murphy
2019-10-01 12:45 ` Robin Murphy
2019-10-01 14:34 ` Sudeep Holla [this message]
2019-10-01 14:34 ` Sudeep Holla
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=20191001143350.GA404@bogus \
--to=sudeep.holla@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=liviu.dudau@arm.com \
--cc=lorenzo.pieralisi@arm.com \
--cc=robh@kernel.org \
--cc=robin.murphy@arm.com \
--cc=steven.price@arm.com \
--cc=tomeu.vizoso@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.