From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752744AbdFVIDA (ORCPT ); Thu, 22 Jun 2017 04:03:00 -0400 Received: from regular1.263xmail.com ([211.150.99.137]:55750 "EHLO regular1.263xmail.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752630AbdFVIC6 (ORCPT ); Thu, 22 Jun 2017 04:02:58 -0400 X-263anti-spam: BIG:0; X-MAIL-GRAY: 0 X-MAIL-DELIVERY: 1 X-ADDR-CHECKED4: 1 X-ABS-CHECKED: 1 X-SKE-CHECKED: 1 X-ANTISPAM-LEVEL: 2 X-RL-SENDER: mark.yao@rock-chips.com X-FST-TO: linux-arm-kernel@lists.infradead.org X-SENDER-IP: 58.22.7.114 X-LOGIN-NAME: mark.yao@rock-chips.com X-UNIQUE-TAG: X-ATTACHMENT-NUM: 0 X-DNS-TYPE: 0 Subject: Re: [PATCH v3.1 1/3] drm/rockchip: dw_hdmi: add RK3399 HDMI support To: Heiko Stuebner References: <1496992236-10634-1-git-send-email-mark.yao@rock-chips.com> <1498115845-7177-1-git-send-email-mark.yao@rock-chips.com> <1751555.73cFbViMXZ@phil> Cc: Mark Rutland , devicetree@vger.kernel.org, David Airlie , linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, linux-rockchip@lists.infradead.org, Rob Herring , linux-arm-kernel@lists.infradead.org From: Mark yao Message-ID: <594B79A4.1000509@rock-chips.com> Date: Thu, 22 Jun 2017 16:02:44 +0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.3.0 MIME-Version: 1.0 In-Reply-To: <1751555.73cFbViMXZ@phil> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 2017年06月22日 15:31, Heiko Stuebner wrote: >> + >> >+/** >> >+ * struct rockchip_hdmi_chip_data - splite the grf setting of kind of chips >> >+ * @lcdsel_grf_reg: grf register offset of lcdc select >> >+ * @lcdsel_big: reg value of selecting vop big for HDMI >> >+ * @lcdsel_lit: reg value of selecting vop little for HDMI >> >+ */ >> >+struct rockchip_hdmi_chip_data { >> >+ u32 lcdsel_grf_reg; > How do you plan on handling the rk3368 (with only one VOP and thus > no selection happening)? I'd just make the above an int, so we could > set it to -1 for that case. (value 0 is after all a valid reg). It's a problem handling on rk3368, using -1 to judge means that we need initial the lcdsel_grf_reg to -1 on rk3368 platform, we need always add a platform data to handle it, seems not good enough. Since the hdmi chip data only use for vop selection, maybe we can judge with checking hdmi->chip_data == NULL for the case. Mark. > > Heiko > > -- Ｍark Yao