Received: by 2002:ad5:474a:0:0:0:0:0 with SMTP id i10csp9446171imu; Wed, 5 Dec 2018 05:04:52 -0800 (PST) X-Google-Smtp-Source: AFSGD/VJjFPe1AgdvaYHTZ1nz/fVaj6tNGkLSarnB3gZGnfj/l67URd0hQ8WkqbnLEeWpXDpNCsi X-Received: by 2002:a17:902:280b:: with SMTP id e11mr24280638plb.269.1544015091854; Wed, 05 Dec 2018 05:04:51 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1544015091; cv=none; d=google.com; s=arc-20160816; b=y7DmIgnMjo7kYANsQhLqFMHWYImUrBDBjHg9O5f01jjgWuEFbMZUQPU/Nhv0KQ+0VL 4HAugYJyWGTWfRwCAmHc506q6ZoMpU/8SDWD8226Gj3UoLWj9QkI2bECVETb/cehZcYL 4iFLGfBiPL1YecB+oBQ+9Qa9st7cGsuSckbgMuGJ0rJHY48usri7UVt/VzBENpPR3aIl yfJVa8Bp8ffKWGOq1ELVyy6l4hXRZa1QxcBpwZrnJkK55lcJNScBkCMu6tBs7a22OTxE OVPcWpeBsYpcq66rQMZoa1Zr5pRoiXjqBye0Ye64VZUdwdKHYpAcFLtspRI9IZJeSTPp hSQw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-language :content-transfer-encoding:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=GEDRqtgdf8VoQazMG7hKMjeRjS8KaRTqD8TxqNsxMIA=; b=UEdIhvdtHTxJJWoi869aRR0qVZPOLChO6rjKDGCo56nHhTY5bVQeTW/fFdg0p0obzj 1gFjQ6z/wVC0BeL7jdlJnquZdObvxLKCknXXov5b7CB/V0t89IS325IaJ9ltHRCxGx3m LQFdQx1cslXfnHIWxTA/jlBJv8VBSUUk5CUXhLvyGqy/T6wKN6RTs+lX9PPgGYeDIypZ iKSjZmjbQjGapIcr6Tsk19HQaxF97NJtnbAjsydMYi7y5fTcINwqDemp5dXlg1HfHrfY e2yq4qnyGWde6I26orjAXTAKD7owRG9Bqj/iplzFCoXZEfL/jT4s4LfFGmmnpFf5hDvI Psiw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l8si16274289pgm.250.2018.12.05.05.04.33; Wed, 05 Dec 2018 05:04:51 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727777AbeLENDj (ORCPT + 99 others); Wed, 5 Dec 2018 08:03:39 -0500 Received: from relay1.mentorg.com ([192.94.38.131]:49895 "EHLO relay1.mentorg.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726937AbeLENDi (ORCPT ); Wed, 5 Dec 2018 08:03:38 -0500 Received: from nat-ies.mentorg.com ([192.94.31.2] helo=SVR-IES-MBX-04.mgc.mentorg.com) by relay1.mentorg.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-SHA384:256) id 1gUWq0-00024C-Mb from Akash_Gajjar@mentor.com ; Wed, 05 Dec 2018 05:03:36 -0800 Received: from [10.105.2.145] (137.202.0.90) by SVR-IES-MBX-04.mgc.mentorg.com (139.181.222.4) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 5 Dec 2018 13:03:31 +0000 Subject: Re: [PATCH 2/2] arm64: dts: rockchip: rockpro64 fix video output chain To: Oskari Lemmela , Rob Herring , Mark Rutland , Heiko Stuebner CC: , , , References: <20181201100817.20688-1-oskari@lemmela.net> <20181201100817.20688-3-oskari@lemmela.net> From: agajjar Message-ID: <09287391-d541-cddb-4168-55ca6fee3f16@mentor.com> Date: Wed, 5 Dec 2018 18:33:29 +0530 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.2 MIME-Version: 1.0 In-Reply-To: <20181201100817.20688-3-oskari@lemmela.net> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-Originating-IP: [137.202.0.90] X-ClientProxiedBy: svr-ies-mbx-01.mgc.mentorg.com (139.181.222.1) To SVR-IES-MBX-04.mgc.mentorg.com (139.181.222.4) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 12/1/2018 3:38 PM, Oskari Lemmela wrote: > Rockpro64 is not able boot if kernel is compiled with > CONFIG_DRM_ROCKCHIP=m > > Enable Rockpro64 board HDMI output to fix issue. Hi Oskari, Could you please describe this issue in detail. I am not able to reproduce this issue if CONFIG_DRM_ROCKCHIP is compile in or as a loadable module at the same time hdmi node is present or not. > Signed-off-by: Oskari Lemmela > --- > arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts | 7 +++++++ > 1 file changed, 7 insertions(+) > > diff --git a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts > index 5bd4d69914bd..be78172abc09 100644 > --- a/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts > +++ b/arch/arm64/boot/dts/rockchip/rk3399-rockpro64.dts > @@ -205,6 +205,13 @@ > status = "okay"; > }; > > +&hdmi { > + ddc-i2c-bus = <&i2c3>; > + pinctrl-names = "default"; > + pinctrl-0 = <&hdmi_cec>; > + status = "okay"; > +}; > + > &i2c0 { > clock-frequency = <400000>; > i2c-scl-rising-time-ns = <168>;