From: Heiko Stuebner <heiko@sntech.de>
To: Eddie Cai <eddie.cai.linux@gmail.com>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
linux@armlinux.org.uk, linux-kernel@vger.kernel.org,
linux-rockchip@lists.infradead.org, robh+dt@kernel.org,
Eddie Cai <eddie.cai@rock-chips.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ARM: dts: rockchip: add dts for RK3288-Tinker board
Date: Thu, 19 Jan 2017 10:58:19 +0100 [thread overview]
Message-ID: <40159140.kOHBSj8v8b@phil> (raw)
In-Reply-To: <1484791919-4665-3-git-send-email-eddie.cai@rock-chips.com>
Hi Eddie,
Am Donnerstag, 19. Januar 2017, 10:11:59 CET schrieb Eddie Cai:
> This patch add basic support for RK3288-Tinker board. We can boot in to
> rootfs with this patch.
>
> Signed-off-by: Eddie Cai <eddie.cai@rock-chips.com>
looks good in general, just some small question down below.
[...]
> + /*
> + * NOTE: vcc_sd isn't hooked up on v1.0 boards where power comes from
> + * vcc_io directly. Those boards won't be able to power cycle SD cards
> + * but it shouldn't hurt to toggle this pin there anyway.
> + */
just to clarify, later board will have that pin connected, right?
> + vcc_sd: sdmmc-regulator {
> + compatible = "regulator-fixed";
> + gpio = <&gpio7 11 GPIO_ACTIVE_LOW>;
> + pinctrl-names = "default";
> + pinctrl-0 = <&sdmmc_pwr>;
> + regulator-name = "vcc_sd";
> + regulator-min-microvolt = <3300000>;
> + regulator-max-microvolt = <3300000>;
> + startup-delay-us = <100000>;
> + vin-supply = <&vcc_io>;
> + };
> +};
[...]
> +&hdmi {
> + #address-cells = <1>;
> + #size-cells = <0>;
> + #sound-dai-cells = <0>;
> + ddc-i2c-bus = <&i2c5>;
> + status = "okay";
> + /* Don't use vopl for HDMI */
> + ports {
> + hdmi_in: port {
> + /delete-node/ endpoint@1;
> + };
what is the reason for this? You enable both VOPs below and the linux display
subsystem should be able to select an appropriate VOP for output just fine on
its own. So there should be no reason for capping the hdmi's connection to one
of the vops.
> + };
> +};
[...]
> +&usb_host0_ehci {
> + no-relinquish-port;
This seems like an unused/undocumented property
> + status = "okay";
> +};
[...]
> +&vopl {
> + status = "okay";
> + /* Don't use vopl for HDMI */
> + vopl_out: port {
> + /delete-node/ endpoint@0;
> + };
see comment at the hdmi node
> +};
Thanks
Heiko
next prev parent reply other threads:[~2017-01-19 9:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-19 2:11 [PATCH 0/2] Add support for RK3288 Tinker board Eddie Cai
[not found] ` <1484791919-4665-1-git-send-email-eddie.cai-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-19 2:11 ` [PATCH 1/2] dt-bindings: add Asus " Eddie Cai
[not found] ` <1484791919-4665-2-git-send-email-eddie.cai-TNX95d0MmH7DzftRWevZcw@public.gmane.org>
2017-01-21 20:42 ` Rob Herring
2017-01-22 1:06 ` Eddie Cai(蔡枫)
2017-01-19 2:11 ` [PATCH 2/2] ARM: dts: rockchip: add dts for RK3288-Tinker board Eddie Cai
2017-01-19 9:58 ` Heiko Stuebner [this message]
2017-01-20 6:42 ` Eddie Cai
2017-01-20 7:10 ` Eddie Cai
2017-01-20 8:12 ` Heiko Stuebner
2017-01-20 8:31 ` Eddie Cai
2017-01-20 2:29 ` Shawn Lin
2017-01-20 7:07 ` Eddie Cai
2017-01-20 7:48 ` Shawn Lin
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=40159140.kOHBSj8v8b@phil \
--to=heiko@sntech.de \
--cc=devicetree@vger.kernel.org \
--cc=eddie.cai.linux@gmail.com \
--cc=eddie.cai@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=linux@armlinux.org.uk \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.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;
as well as URLs for NNTP newsgroup(s).