linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Scott Branden <scott.branden@broadcom.com>
To: Eric Anholt <eric@anholt.net>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Rob Herring <robh+dt@kernel.org>,
	Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com,
	Ray Jui <rjui@broadcom.com>,
	Scott Branden <sbranden@broadcom.com>,
	Jon Mason <jonmason@broadcom.com>
Subject: Re: [PATCH] ARM: dts: bcm-cygnus: Add 911360's V3D device.
Date: Thu, 20 Apr 2017 14:38:57 -0700	[thread overview]
Message-ID: <e949b0d2-5cc9-e301-e069-8d61110b3a04@broadcom.com> (raw)
In-Reply-To: <20170418233234.13374-1-eric@anholt.net>

Looks good - thanks for getting the V3D open source code going on this SoC!

On 17-04-18 04:32 PM, Eric Anholt wrote:
> This loads the VC4 driver on the 911360_entphn platform (with the
> corresponding series sent to dri-devel), which is supported by master
> of the Mesa tree.
>
> Signed-off-by: Eric Anholt <eric@anholt.net>
Acked-by: Scott Branden <scott.branden@broadcom.com>
> ---
>  arch/arm/boot/dts/bcm-cygnus.dtsi      | 13 +++++++++++++
>  arch/arm/boot/dts/bcm911360_entphn.dts |  8 ++++++++
>  2 files changed, 21 insertions(+)
>
> diff --git a/arch/arm/boot/dts/bcm-cygnus.dtsi b/arch/arm/boot/dts/bcm-cygnus.dtsi
> index f52750c6d3ed..907a5e843364 100644
> --- a/arch/arm/boot/dts/bcm-cygnus.dtsi
> +++ b/arch/arm/boot/dts/bcm-cygnus.dtsi
> @@ -406,6 +406,19 @@
>  			status = "disabled";
>  		};
>
> +		v3d: v3d@180a2000 {
> +			compatible = "brcm,cygnus-v3d";
> +			reg = <0x180a2000 0x1000>;
> +			clocks = <&mipipll BCM_CYGNUS_MIPIPLL_CH2_V3D>;
> +			clock-names = "v3d_clk";
> +			interrupts = <GIC_SPI 182 IRQ_TYPE_LEVEL_HIGH>;
> +			status = "disabled";
> +		};
> +
> +		vc4: gpu {
> +			compatible = "brcm,cygnus-vc4";
> +		};
> +
>  		adc: adc@180a6000 {
>  			compatible = "brcm,iproc-static-adc";
>  			#io-channel-cells = <1>;
> diff --git a/arch/arm/boot/dts/bcm911360_entphn.dts b/arch/arm/boot/dts/bcm911360_entphn.dts
> index 8b3800f46288..037621c13290 100644
> --- a/arch/arm/boot/dts/bcm911360_entphn.dts
> +++ b/arch/arm/boot/dts/bcm911360_entphn.dts
> @@ -57,6 +57,14 @@
>  	};
>  };
>
> +&v3d {
> +	assigned-clocks =
> +		<&mipipll BCM_CYGNUS_MIPIPLL>,
> +		<&mipipll BCM_CYGNUS_MIPIPLL_CH2_V3D>;
> +	assigned-clock-rates = <525000000>, <300000000>;
> +	status = "okay";
> +};
> +
>  &uart3 {
>  	status = "okay";
>  };
>

  reply	other threads:[~2017-04-20 21:39 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-18 23:32 [PATCH] ARM: dts: bcm-cygnus: Add 911360's V3D device Eric Anholt
2017-04-20 21:38 ` Scott Branden [this message]
2017-04-25 19:08 ` Florian Fainelli

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=e949b0d2-5cc9-e301-e069-8d61110b3a04@broadcom.com \
    --to=scott.branden@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=eric@anholt.net \
    --cc=f.fainelli@gmail.com \
    --cc=jonmason@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=rjui@broadcom.com \
    --cc=robh+dt@kernel.org \
    --cc=sbranden@broadcom.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).