| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Wed, 1 May 2019 13:47:45 +0100
From: Robin Murphy <robin.murphy@....com>
To: Jagan Teki <jagan@...rulasolutions.com>,
Heiko Stuebner <heiko@...ech.de>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>
Cc: devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-rockchip@...ts.infradead.org,
linux-amarula@...rulasolutions.com,
linux-arm-kernel@...ts.infradead.org
Subject: Re: [DO NOT MERGE] [PATCH 2/2] arm64: rockchip: rk3399: nanopc-t4:
Enable FriendlyELEC HD702E eDP panel
On 01/05/2019 13:14, Jagan Teki wrote:
> FriendlyELEC HD702E is one of optional LCD panel for
> NanoPC T4 eDP interface.
>
> It features 800x1280 resolutions, with built in GT9271 captive
> touchscreen and adjustable backlight via PWM.
>
> eDP panel connections are:
> - VCC3V3_SYS: 3.3V panel power supply
> - GPIO4_C2: PWM0_BL pin
> - GPIO4_D5_LCD_BL_EN: Backlight enable pin
> - VCC12V0_SYS: 12V backlight power supply
> - Touchscreen connected via I2C4
> - GPIO1_C4_TP_INT: touchscreen interrupt pin
> - GPIO1_B5_TP_RST: touchscreen reset pin
>
> Add support for it.
>
> Signed-off-by: Jagan Teki <jagan@...rulasolutions.com>
> ---
> Note: we need to disable hdmi-cec pinctrl to work with
> edp-hpd since both share same pin, otherwise we can
> encounter below error during bootup
> [ 1.047726] rockchip-pinctrl pinctrl: pin gpio4-23 already requested by ff940000.hdmi; cannot claim for ff970000.edp
> [ 1.048655] rockchip-pinctrl pinctrl: pin-151 (ff970000.edp) status -22
> [ 1.049235] rockchip-pinctrl pinctrl: could not request pin 151 (gpio4-23) from group edp-hpd on device rockchip-pinctrl
> [ 1.050191] rockchip-dp ff970000.edp: Error applying setting, reverse things back
> [ 1.050867] rockchip-dp: probe of ff970000.edp failed with error -22
Hmm, AFAICS that pin is exclusively wired to the HDMI connector and not
used for the eDP interface, so really it's the fault of rk3399.dtsi for
trying to claim it unconditionally. Ideally we'd pull those pinctrl
properties out into the board DTs which do actually need them, but the
quick and easy approach would be to add some "/delete-property/ ..."
workarounds to the &edp node here.
> .../boot/dts/rockchip/rk3399-nanopc-t4.dts | 82 +++++++++++++++++++
> 1 file changed, 82 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts b/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
> index 931c3dbf1b7d..b652d960946f 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
> +++ b/arch/arm64/boot/dts/rockchip/rk3399-nanopc-t4.dts
> @@ -46,6 +46,48 @@
> };
> };
>
> + backlight: backlight {
> + compatible = "pwm-backlight";
> + brightness-levels = <
> + 0 1 2 3 4 5 6 7
> + 8 9 10 11 12 13 14 15
> + 16 17 18 19 20 21 22 23
> + 24 25 26 27 28 29 30 31
> + 32 33 34 35 36 37 38 39
> + 40 41 42 43 44 45 46 47
> + 48 49 50 51 52 53 54 55
> + 56 57 58 59 60 61 62 63
> + 64 65 66 67 68 69 70 71
> + 72 73 74 75 76 77 78 79
> + 80 81 82 83 84 85 86 87
> + 88 89 90 91 92 93 94 95
> + 96 97 98 99 100 101 102 103
> + 104 105 106 107 108 109 110 111
> + 112 113 114 115 116 117 118 119
> + 120 121 122 123 124 125 126 127
> + 128 129 130 131 132 133 134 135
> + 136 137 138 139 140 141 142 143
> + 144 145 146 147 148 149 150 151
> + 152 153 154 155 156 157 158 159
> + 160 161 162 163 164 165 166 167
> + 168 169 170 171 172 173 174 175
> + 176 177 178 179 180 181 182 183
> + 184 185 186 187 188 189 190 191
> + 192 193 194 195 196 197 198 199
> + 200 201 202 203 204 205 206 207
> + 208 209 210 211 212 213 214 215
> + 216 217 218 219 220 221 222 223
> + 224 225 226 227 228 229 230 231
> + 232 233 234 235 236 237 238 239
> + 240 241 242 243 244 245 246 247
> + 248 249 250 251 252 253 254 255>;
This looks trivial enough that I wonder whether it might still work to
just omit it? Not that I know anything about backlights, but I had the
impression (from mailing list traffic, I guess) that the driver gained
the ability to provide a reasonable default behaviour at some point.
Robin.
> + default-brightness-level = <200>;
> + enable-gpios = <&gpio4 RK_PD5 GPIO_ACTIVE_HIGH>; /* GPIO4_D5_LCD_BL_EN */
> + pwms = <&pwm0 0 25000 0>;
> + power-supply = <&vcc12v0_sys>;
> + status = "okay";
> + };
> +
> ir-receiver {
> compatible = "gpio-ir-receiver";
> gpios = <&gpio0 RK_PA6 GPIO_ACTIVE_LOW>;
> @@ -64,6 +106,18 @@
> fan-supply = <&vcc12v0_sys>;
> pwms = <&pwm1 0 50000 0>;
> };
> +
> + panel {
> + compatible ="friendlyarm,hd702e";
> + backlight = <&backlight>;
> + power-supply = <&vcc3v3_sys>;
> +
> + port {
> + panel_in_edp: endpoint {
> + remote-endpoint = <&edp_out_panel>;
> + };
> + };
> + };
> };
>
> &cpu_thermal {
> @@ -94,6 +148,23 @@
> };
> };
>
> +&edp {
> + status = "okay";
> +
> + ports {
> + edp_out: port@1 {
> + reg = <1>;
> + #address-cells = <1>;
> + #size-cells = <0>;
> +
> + edp_out_panel: endpoint@0 {
> + reg = <0>;
> + remote-endpoint = <&panel_in_edp>;
> + };
> + };
> + };
> +};
> +
> &gpu_thermal {
> trips {
> gpu_warm: gpu_warm {
> @@ -130,6 +201,17 @@
> };
> };
>
> +&i2c4 {
> + touchscreen@5d {
> + compatible = "goodix,gt911";
> + reg = <0x5d>;
> + interrupt-parent = <&gpio1>;
> + interrupts = <RK_PC4 IRQ_TYPE_EDGE_FALLING>;
> + irq-gpio = <&gpio1 RK_PC4 GPIO_ACTIVE_HIGH>; /* GPIO1_C4_TP_INT */
> + reset-gpio = <&gpio1 RK_PB5 GPIO_ACTIVE_LOW>; /* GPIO1_B5_TP_RST */
> + };
> +};
> +
> &sdhci {
> mmc-hs400-1_8v;
> mmc-hs400-enhanced-strobe;
>
Powered by blists - more mailing lists