From: Stefan Wahren <info-saaNCTdWVBT7BZbvpMY5sg@public.gmane.org>
To: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
Cc: dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: Re: [PATCH v2 1/7] drm/vc4: Add devicetree bindings for VC4.
Date: Wed, 19 Aug 2015 22:38:35 +0200 [thread overview]
Message-ID: <55D4E94B.8080103@lategoodbye.de> (raw)
In-Reply-To: <1439934848-7196-2-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
Hi Eric,
Am 18.08.2015 um 23:54 schrieb Eric Anholt:
> VC4 is the GPU (display and 3D) subsystem present on the 2835 and some
> other Broadcom SoCs.
>
> This binding follows the model of msm, imx, sti, and others, where
> there is a subsystem node for the whole GPU, with nodes for the
> individual HW components within it.
>
> Signed-off-by: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
> ---
>
> v2: Extend the commit message, fix several nits from Stephen Warren.
>
> .../devicetree/bindings/gpu/brcm,bcm-vc4.txt | 79 ++++++++++++++++++++++
> 1 file changed, 79 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/gpu/brcm,bcm-vc4.txt
>
> diff --git a/Documentation/devicetree/bindings/gpu/brcm,bcm-vc4.txt b/Documentation/devicetree/bindings/gpu/brcm,bcm-vc4.txt
> new file mode 100644
> index 0000000..1b9fedc
> --- /dev/null
> +++ b/Documentation/devicetree/bindings/gpu/brcm,bcm-vc4.txt
> @@ -0,0 +1,79 @@
> +Broadcom VC4 GPU
> +
> +The VC4 device present on the Raspberry Pi includes a display system
> +with HDMI output and the HVS scaler for compositing display planes.
> +
> +Required properties for VC4:
> +- compatible: Should be "brcm,vc4"
> +- crtcs: List of phandles of pixelvalve scanout engines
> +- hvss: List of phandles of HVS video scalers
> +- encoders: List of phandles of output encoders (HDMI, SDTV)
> +
> +Required properties for Pixel Valve:
> +- compatible: Should be "brcm,vc4-pixelvalve"
> +- reg: Physical base address and length of the PV's registers
> +- interrupts: The interrupt number
> + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt
> +
> +Required properties for HVS:
> +- compatible: Should be "brcm,vc4-hvs"
> +- reg: Physical base address and length of the HVS's registers
> +- interrupts: The interrupt number
> + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt
> +
> +Required properties for HDMI
> +- compatible: Should be "brcm,vc4-hdmi"
> +- reg: Physical base address and length of the two register ranges
> + ("HDMI" and "HD", in that order)
> +- interrupts: The interrupt numbers
> + See bindings/interrupt-controller/brcm,bcm2835-armctrl-ic.txt
> +- ddc: phandle of the I2C controller used for DDC EDID probing
> +- crtc: phandle to the pixelvalve CRTC the HDMI encoder is attached to
> +
> +Optional properties for HDMI:
> +- hpd-gpio: The GPIO pin for HDMI hotplug detect (if it doesn't appear
> + as an interrupt/status bit in the HDMI controller
> + itself). See bindings/pinctrl/brcm,bcm2835-gpio.txt
> +
> +Example:
> +pv0: brcm,vc4-pixelvalve@7e206000 {
AFAIK the DT node name should describe the function and usually don't
have a vendor prefix. Here some possible suggestions without deeper
knowledge of the hardware function:
pv0: pixelvalve
> + compatible = "brcm,vc4-pixelvalve";
> + reg = <0x7e206000 0x100>;
> + interrupts = <2 13>; /* pwa2 */
> +};
> +
> +pv1: brcm,vc4-pixelvalve@7e207000 {
pv1: pixelvalve
> + compatible = "brcm,vc4-pixelvalve";
> + reg = <0x7e207000 0x100>;
> + interrupts = <2 14>; /* pwa1 */
> +};
> +
> +pv2: brcm,vc4-pixelvalve@7e807000 {
pv2: pixelvalve
> + compatible = "brcm,vc4-pixelvalve";
> + reg = <0x7e807000 0x100>;
> + interrupts = <2 10>; /* pixelvalve */
> +};
> +
> +hvs: brcm,hvs@7e400000 {
hvs: hvs
> + compatible = "brcm,vc4-hvs";
> + reg = <0x7e400000 0x6000>;
> + interrupts = <2 1>;
> +};
> +
> +hdmi: brcm,vc4-hdmi@7e902000 {
hdmi: hdmi
> + compatible = "brcm,vc4-hdmi";
> + reg = <0x7e902000 0x600>,
> + <0x7e808000 0x100>;
> + interrupts = <2 8>, <2 9>;
> + ddc = <&i2c2>;
> + hpd-gpio = <&gpio 46 GPIO_ACTIVE_HIGH>;
> + crtc = <&pv2>;
> +};
> +
> +vc4: vc4@0x7e4c0000 {
vc4: gpu
Regards
Stefan
> + compatible = "brcm,vc4";
> +
> + crtcs = <&pv0>, <&pv1>, <&pv2>;
> + encoders = <&hdmi>;
> + hvss = <&hvs>;
> +};
>
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2015-08-19 20:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-18 21:54 Raspberry Pi KMS-only driver V2 Eric Anholt
2015-08-18 21:54 ` [PATCH v2 1/7] drm/vc4: Add devicetree bindings for VC4 Eric Anholt
[not found] ` <1439934848-7196-2-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-08-19 20:38 ` Stefan Wahren [this message]
2015-08-26 9:44 ` Luc Verhaegen
2015-08-18 21:54 ` [PATCH v2 3/7] drm/vc4: Add KMS support for Raspberry Pi Eric Anholt
2015-08-19 21:37 ` Stefan Wahren
2015-08-25 8:44 ` Daniel Vetter
[not found] ` <1439934848-7196-1-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-08-18 21:54 ` [PATCH v2 2/7] MAINTAINERS: Add myself for the new VC4 (RPi GPU) graphics driver Eric Anholt
2015-08-18 21:54 ` [PATCH v2 4/7] drm/vc4: Use the fbdev_cma helpers Eric Anholt
2015-08-18 21:54 ` [PATCH v2 5/7] drm/vc4: Allow vblank to be disabled Eric Anholt
2015-08-18 21:54 ` [PATCH v2 6/7] ARM: bcm2835: Add the DDC I2C controller to the device tree Eric Anholt
[not found] ` <1439934848-7196-7-git-send-email-eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
2015-08-26 2:02 ` Stephen Warren
2015-08-18 21:54 ` [PATCH v2 7/7] ARM: bcm2835: Add VC4 " Eric Anholt
2015-08-26 2:04 ` Stephen Warren
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=55D4E94B.8080103@lategoodbye.de \
--to=info-saanctdwvbt7bzbvpmy5sg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=dri-devel-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org \
--cc=eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org \
--cc=linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
/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