From: Russell King - ARM Linux <linux@armlinux.org.uk>
To: Lucas Stach <l.stach@pengutronix.de>
Cc: dri-devel@lists.freedesktop.org
Subject: Re: [PATCH 1/2] drm/etnaviv: fail probe if core or bus clock are absent
Date: Mon, 29 Aug 2016 11:51:28 +0100 [thread overview]
Message-ID: <20160829105128.GD1041@n2100.armlinux.org.uk> (raw)
In-Reply-To: <1472467640.2775.4.camel@pengutronix.de>
On Mon, Aug 29, 2016 at 12:47:20PM +0200, Lucas Stach wrote:
> Core, bus and shader are all module input clocks. If the SoC integration
> provides the same clock for all inputs, the DT should reflect this by
> supplying the same clock for all 3 inputs.
You're making an assertion that we don't know is true. There is no
evidence that the GC600 has three input clocks. Just because iMX
Vivante GPUs have three clocks does not mean that all Vivante IP has
three clock inputs.
--
RMK's Patch system: http://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up
according to speedtest.net.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
prev parent reply other threads:[~2016-08-29 10:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-26 15:49 [PATCH 1/2] drm/etnaviv: fail probe if core or bus clock are absent Lucas Stach
2016-08-26 15:49 ` [PATCH 1/2] net: fec: don't ack masked interrupt events Lucas Stach
2016-08-26 15:53 ` Lucas Stach
2016-08-26 16:18 ` Russell King - ARM Linux
2016-08-26 15:49 ` [PATCH 2/2] drm/etnaviv: fold various clock enable/disable functions into top ones Lucas Stach
2016-08-26 15:49 ` [PATCH 2/2] net: fec: optimize IRQ handler Lucas Stach
2016-08-26 16:10 ` [PATCH 1/2] drm/etnaviv: fail probe if core or bus clock are absent Russell King - ARM Linux
2016-08-29 10:47 ` Lucas Stach
2016-08-29 10:51 ` Russell King - ARM Linux [this message]
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=20160829105128.GD1041@n2100.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=dri-devel@lists.freedesktop.org \
--cc=l.stach@pengutronix.de \
/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