Received: by 2002:ac0:a5a6:0:0:0:0:0 with SMTP id m35-v6csp3496271imm; Wed, 5 Sep 2018 00:48:14 -0700 (PDT) X-Google-Smtp-Source: ANB0VdZja81yGa2/Bs8SufskuoSfhaQ/ZDpgNIhBiYt4hRpZzkU0//vTQQG22ZkpQsLe3MVaFBtq X-Received: by 2002:a63:24c:: with SMTP id 73-v6mr36010100pgc.252.1536133694813; Wed, 05 Sep 2018 00:48:14 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1536133694; cv=none; d=google.com; s=arc-20160816; b=pvRDvlr3rrqjfMzNlcoElqZQih+ISx/l1X0uj3N4ysdhyFVF3unle9a6KXIk0vGIXK rBeceyr+H8njgTn/cfR+tYRTxV3w4+SZcW3qr/oo6wj2FmsI76OcpPrM6m3GvkjJD24/ TLEVtWVgbLezmvOdzwxhkAjlLGGmbR+yRm2BBr+lQhj5O0Iyum/9hzjzzpv36wo6rh5L uBVaan2BSPSgAxxjddSzciiW5WpPa//yprVobpKpmz+jhqPhQSfWJu8r7vxa1KxyuSgT 7iJHJUgggLe+mioqsvLiu5ENL+2woXMqrv6CwXGCXjQ7jtOFhI3L9z2pzuPK7cahP8s1 6mFA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:message-id:from:cc:to:subject :content-transfer-encoding:mime-version:references:in-reply-to:date; bh=NwdlzvnWhDlvwM4xoMqPyBWmOiYaUBfr65dkTFM9Nbk=; b=QDU+OoHZvtbVm7jefV2xNyFW0V7cJQJjBJPdlNCAS8xfiJ9HC52qTgUZrMSyb7NTLf mZpHf/ZNoIxbuZk60jxErge8EEvp0/JqMzkMiSrLmOXWSDNdCvdUX4zXvr03TqK/BPfR Wypq8d73M6I17k5M6DzBNNtm6qvoDzHig7KwgvL6BqP0Sv0LMLhPC6n+Ju09HfT5eE4T DYBxXwW5QJNUY/isUJta5Fyp70Ramb9W2dnPYp9qRBtY1X8VdOySnnslm5GPop/Dmh14 GP+GuG5ELX5HWKt2eaYR4tFhK9w5kzm9oHIolpi8gV4YF9lSaI5s9oizsRWEJ1YRtIel PuoQ== 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 h2-v6si1323412pgk.330.2018.09.05.00.47.59; Wed, 05 Sep 2018 00:48:14 -0700 (PDT) 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 S1727657AbeIEMPu convert rfc822-to-8bit (ORCPT + 99 others); Wed, 5 Sep 2018 08:15:50 -0400 Received: from hermes.aosc.io ([199.195.250.187]:56664 "EHLO hermes.aosc.io" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727195AbeIEMPt (ORCPT ); Wed, 5 Sep 2018 08:15:49 -0400 Received: from localhost (localhost [127.0.0.1]) (Authenticated sender: icenowy@aosc.io) by hermes.aosc.io (Postfix) with ESMTPSA id B5EA9FFAF3; Wed, 5 Sep 2018 07:46:48 +0000 (UTC) Date: Wed, 05 Sep 2018 15:46:41 +0800 In-Reply-To: <20180905071435.lgsogpzmh5nw6bcy@flea> References: <20180903133434.58188-1-icenowy@aosc.io> <20180903133434.58188-2-icenowy@aosc.io> <20180905071435.lgsogpzmh5nw6bcy@flea> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8BIT Subject: Re: [PATCH 1/3] dt-bindings: change the A64 HDMI PHY binding to R40 To: linux-arm-kernel@lists.infradead.org, Maxime Ripard CC: devicetree@vger.kernel.org, Jernej Skrabec , linux-sunxi@googlegroups.com, linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org, Chen-Yu Tsai From: Icenowy Zheng Message-ID: <3D28A45F-D67D-4388-9FB7-2A2763955398@aosc.io> Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 于 2018年9月5日 GMT+08:00 下午3:14:35, Maxime Ripard 写到: >On Mon, Sep 03, 2018 at 09:34:32PM +0800, Icenowy Zheng wrote: >> By experiment, the A64 HDMi PHY doesn't support the PLL-VIDEO mux >> introduced in R40, although it has two PLL-VIDEOs. >> >> Change the A64 HDMI PHY binding to R40 one. >> >> This binding is introduced in v4.19, which is still in RC stage, so >we >> have change to fix it. >> >> Signed-off-by: Icenowy Zheng > >That doesn't make much sense. The A64 doesn't have any particular >reason to behave like the R40, and the R40 can definitely use a >different compatible if it has a different behaviour. But I don't see >*why* the A64 not behaving like the R40 is a justification to remove >the A64 compatible. Especially when the R40 was released later. > >Add a new compatible, and leave the A64 compatible alone. But the behavior of A64 compatible will change from double PLL to single PLL, because the A64 HDMI PHY is proven to have no double PLL. Should I then change the A64 compatible behavior and import R40 compatible at the same time? In addition maybe I can just drop A64 compatible, and let A64 use H3 one. Then I will add a R40 compatible to catch dual PLL behavior. > >Maxime