From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.7 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_PASS,UNPARSEABLE_RELAY,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5E591C43382 for ; Thu, 27 Sep 2018 00:59:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0DED821566 for ; Thu, 27 Sep 2018 00:59:45 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org 0DED821566 Authentication-Results: mail.kernel.org; dmarc=none (p=none dis=none) header.from=magewell.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727064AbeI0HPU (ORCPT ); Thu, 27 Sep 2018 03:15:20 -0400 Received: from out20-15.mail.aliyun.com ([115.124.20.15]:49724 "EHLO out20-15.mail.aliyun.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726378AbeI0HPU (ORCPT ); Thu, 27 Sep 2018 03:15:20 -0400 X-Alimail-AntiSpam: AC=CONTINUE;BC=0.0777384|-1;CH=green;FP=0|0|0|0|0|-1|-1|-1;HT=e02c03290;MF=yong.deng@magewell.com;NM=1;PH=DS;RN=23;RT=23;SR=0;TI=SMTPD_---.CwIwi7p_1538009962; Received: from John(mailfrom:yong.deng@magewell.com fp:SMTPD_---.CwIwi7p_1538009962) by smtp.aliyun-inc.com(10.147.41.187); Thu, 27 Sep 2018 08:59:23 +0800 Date: Thu, 27 Sep 2018 08:59:23 +0800 From: Yong To: Laurent Pinchart Cc: maxime.ripard@bootlin.com, Mauro Carvalho Chehab , Rob Herring , Mark Rutland , Chen-Yu Tsai , "David S. Miller" , Greg Kroah-Hartman , Andrew Morton , Arnd Bergmann , Hans Verkuil , Geert Uytterhoeven , Jacob Chen , Neil Armstrong , Thierry Reding , Philipp Zabel , Todor Tomov , Sakari Ailus , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-sunxi@googlegroups.com Subject: Re: [PATCH v11 1/2] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI) Message-Id: <20180927085923.cf24d7e2fba7f38637aff7c4@magewell.com> In-Reply-To: <1568838.d8CnAYTeDB@avalon> References: <1537951204-24672-1-git-send-email-yong.deng@magewell.com> <7197338.mhOH8fQaEM@avalon> <20180926103547.5ubb6xjkl7xngmfg@flea> <1568838.d8CnAYTeDB@avalon> X-Mailer: Sylpheed 3.7.0 (GTK+ 2.24.30; i686-pc-mingw32) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, On Wed, 26 Sep 2018 13:38:08 +0300 Laurent Pinchart wrote: > Hi Maxime, > > On Wednesday, 26 September 2018 13:35:47 EEST maxime.ripard@bootlin.com wrote: > > On Wed, Sep 26, 2018 at 01:19:34PM +0300, Laurent Pinchart wrote: > > > > +Endpoint node properties for CSI1 > > > > +--------------------------------- > > > > > > Should you list the CSI0 properties as well ? As the driver in patch 2/2 > > > doesn't support the CSI-2 interface I assume you have left out CSI0 for > > > now, but it should still be listed in the bindings. I'm fine with fixing > > > this as a follow-up patch to avoid missing the v4.20 merge window, but if > > > you end up resubmitting the series, could you please address the problem > > > ? > > > > That driver is not available, and the documentation isn't either, so > > there's no easy way to tell which properties are going to be needed > > before doing the actual work of reverse engineering it and writing a > > driver for it. Unfortunately... > > While DT bindings should be independent from driver implementations, I agree > it's difficult to develop good bindings without hardware documentation and > without at least one working driver implementation. > > How about just explicitly stating that these bindings don't support CSI0 yet ? OK. Thanks, Yong From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yong Subject: Re: [PATCH v11 1/2] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI) Date: Thu, 27 Sep 2018 08:59:23 +0800 Message-ID: <20180927085923.cf24d7e2fba7f38637aff7c4@magewell.com> References: <1537951204-24672-1-git-send-email-yong.deng@magewell.com> <7197338.mhOH8fQaEM@avalon> <20180926103547.5ubb6xjkl7xngmfg@flea> <1568838.d8CnAYTeDB@avalon> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1568838.d8CnAYTeDB@avalon> Sender: linux-kernel-owner@vger.kernel.org To: Laurent Pinchart Cc: maxime.ripard@bootlin.com, Mauro Carvalho Chehab , Rob Herring , Mark Rutland , Chen-Yu Tsai , "David S. Miller" , Greg Kroah-Hartman , Andrew Morton , Arnd Bergmann , Hans Verkuil , Geert Uytterhoeven , Jacob Chen , Neil Armstrong , Thierry Reding , Philipp Zabel , Todor Tomov , Sakari Ailus , linux-media@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.orgl List-Id: devicetree@vger.kernel.org Hi, On Wed, 26 Sep 2018 13:38:08 +0300 Laurent Pinchart wrote: > Hi Maxime, > > On Wednesday, 26 September 2018 13:35:47 EEST maxime.ripard@bootlin.com wrote: > > On Wed, Sep 26, 2018 at 01:19:34PM +0300, Laurent Pinchart wrote: > > > > +Endpoint node properties for CSI1 > > > > +--------------------------------- > > > > > > Should you list the CSI0 properties as well ? As the driver in patch 2/2 > > > doesn't support the CSI-2 interface I assume you have left out CSI0 for > > > now, but it should still be listed in the bindings. I'm fine with fixing > > > this as a follow-up patch to avoid missing the v4.20 merge window, but if > > > you end up resubmitting the series, could you please address the problem > > > ? > > > > That driver is not available, and the documentation isn't either, so > > there's no easy way to tell which properties are going to be needed > > before doing the actual work of reverse engineering it and writing a > > driver for it. Unfortunately... > > While DT bindings should be independent from driver implementations, I agree > it's difficult to develop good bindings without hardware documentation and > without at least one working driver implementation. > > How about just explicitly stating that these bindings don't support CSI0 yet ? OK. Thanks, Yong From mboxrd@z Thu Jan 1 00:00:00 1970 From: yong.deng@magewell.com (Yong) Date: Thu, 27 Sep 2018 08:59:23 +0800 Subject: [PATCH v11 1/2] dt-bindings: media: Add Allwinner V3s Camera Sensor Interface (CSI) In-Reply-To: <1568838.d8CnAYTeDB@avalon> References: <1537951204-24672-1-git-send-email-yong.deng@magewell.com> <7197338.mhOH8fQaEM@avalon> <20180926103547.5ubb6xjkl7xngmfg@flea> <1568838.d8CnAYTeDB@avalon> Message-ID: <20180927085923.cf24d7e2fba7f38637aff7c4@magewell.com> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org Hi, On Wed, 26 Sep 2018 13:38:08 +0300 Laurent Pinchart wrote: > Hi Maxime, > > On Wednesday, 26 September 2018 13:35:47 EEST maxime.ripard at bootlin.com wrote: > > On Wed, Sep 26, 2018 at 01:19:34PM +0300, Laurent Pinchart wrote: > > > > +Endpoint node properties for CSI1 > > > > +--------------------------------- > > > > > > Should you list the CSI0 properties as well ? As the driver in patch 2/2 > > > doesn't support the CSI-2 interface I assume you have left out CSI0 for > > > now, but it should still be listed in the bindings. I'm fine with fixing > > > this as a follow-up patch to avoid missing the v4.20 merge window, but if > > > you end up resubmitting the series, could you please address the problem > > > ? > > > > That driver is not available, and the documentation isn't either, so > > there's no easy way to tell which properties are going to be needed > > before doing the actual work of reverse engineering it and writing a > > driver for it. Unfortunately... > > While DT bindings should be independent from driver implementations, I agree > it's difficult to develop good bindings without hardware documentation and > without at least one working driver implementation. > > How about just explicitly stating that these bindings don't support CSI0 yet ? OK. Thanks, Yong