Received: by 2002:a25:8b12:0:0:0:0:0 with SMTP id i18csp4296553ybl; Mon, 26 Aug 2019 08:21:36 -0700 (PDT) X-Google-Smtp-Source: APXvYqzA4fZ0CX0ZNp6ZuF5XWS0OmJKwMV3sisvPdBzE5/ZDpX9KjwtUEOXcnQ55zS4MU5MQNTkL X-Received: by 2002:a62:27c5:: with SMTP id n188mr11138282pfn.58.1566832896572; Mon, 26 Aug 2019 08:21:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1566832896; cv=none; d=google.com; s=arc-20160816; b=MageWrVLvPqGCpdmzcuJj+vSHl7MA1MKTTQpo2LFWaS4Lfe5W9qv0MnDDZj+wr961i h6UIzlLhmMwVOzqKJlwcHqP802ExHW60fc6jaEjB2ou+imSkWUn0v84JFZ2mrMeSwx9L 2PgLrXFfV8YkTj6xi0hTdGtlLlTw0P69BF61HGyDA/N2BZl1qgA5X/L9FHFcwoaK8gES 9F6VEiNg2HMglmv759pvxy3MXpHqXMa73KyCH+K7GNDK8EVnWNmi9fR7jCn5YnuH/vvm 650VU1jtOLhx2KHTy5VaqT0Mt/h7O0BLAHe4jUtqWJGdgebEBjXKL4ngG6yvh59PKZDl 9MSQ== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:user-agent:in-reply-to :content-disposition:mime-version:references:message-id:subject:cc :to:from:date; bh=6ayANk92QLfq2EKz5FByhSa9axUTry70vrny7rqQZ94=; b=k+FVg9KQzz8HmaIlLL2cfYZ9IT4zWMcw9q/6yPIvIH3ZuUTeKc+4Pp6CTJu5FhtMAV BKicETBWXFaF6kXFMl7UQdaKnJtoYO8lODNJIvKieDN4ieQZgmkRRVpA0jUpeMsWyOaY zo3V4N481YDSqs5ilXrcmc2mPqusQuu7oUrSEXhR2O6pHKB2iMKFoqpViPRi/ahBFSHA BLdqcbr5yYbI40uBD8/xzMdcaIvFpC4/YfPqmbXKeLtFxuajIXZ7Kh4X/leptLypFuZl 0A98Ab8U9oSb00pXWVwawR5DGEiosXYWMFJ9bqRbzP3Ht6crKOVxC6hNc8DBxUjK8GzE /EpA== 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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id i18si10451875pfq.58.2019.08.26.08.21.21; Mon, 26 Aug 2019 08:21:36 -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; dmarc=fail (p=NONE sp=NONE dis=NONE) header.from=iki.fi Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1732220AbfHZOFs (ORCPT + 99 others); Mon, 26 Aug 2019 10:05:48 -0400 Received: from retiisi.org.uk ([95.216.213.190]:47992 "EHLO hillosipuli.retiisi.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730914AbfHZOFs (ORCPT ); Mon, 26 Aug 2019 10:05:48 -0400 Received: from valkosipuli.localdomain (valkosipuli.retiisi.org.uk [IPv6:2a01:4f9:c010:4572::80:2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by hillosipuli.retiisi.org.uk (Postfix) with ESMTPS id 8BCBD634C87; Mon, 26 Aug 2019 17:05:36 +0300 (EEST) Received: from sailus by valkosipuli.localdomain with local (Exim 4.92) (envelope-from ) id 1i2Fcm-0000Q9-D9; Mon, 26 Aug 2019 17:05:36 +0300 Date: Mon, 26 Aug 2019 17:05:36 +0300 From: Sakari Ailus To: Stu Hsieh Cc: CK Hu , Tomasz Figa , Mauro Carvalho Chehab , Rob Herring , Mark Rutland , Matthias Brugger , Linux Media Mailing List , devicetree@vger.kernel.org, Linux Kernel Mailing List , "list@263.net:IOMMU DRIVERS , Joerg Roedel ," , "moderated list:ARM/Mediatek SoC support" , srv_heupstream Subject: Re: [PATCH v4 01/14] dt-bindings: Add binding for MT2712 MIPI-CSI2 Message-ID: <20190826140536.GE826@valkosipuli.retiisi.org.uk> References: <1559643115-15124-1-git-send-email-stu.hsieh@mediatek.com> <1559643115-15124-2-git-send-email-stu.hsieh@mediatek.com> <1560134057.28527.5.camel@mtksdaap41> <1560153073.31854.6.camel@mtksdaap41> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Jun 10, 2019 at 04:58:02PM +0900, Tomasz Figa wrote: > On Mon, Jun 10, 2019 at 4:51 PM CK Hu wrote: > > > > Hi, Tomasz: > > > > On Mon, 2019-06-10 at 12:32 +0900, Tomasz Figa wrote: > > > Hi CK, Stu, > > > > > > On Mon, Jun 10, 2019 at 11:34 AM CK Hu wrote: > > > > > > > > Hi, Stu: > > > > > > > > "mediatek,mt2712-mipicsi" and "mediatek,mt2712-mipicsi-common" have many > > > > common part with "mediatek,mt8183-seninf", and I've a discussion in [1], > > > > so I would like these two to be merged together. > > > > > > > > [1] https://patchwork.kernel.org/patch/10979131/ > > > > > > > > > > Thanks CK for spotting this. > > > > > > I also noticed that the driver in fact handles two hardware blocks at > > > the same time - SenInf and CamSV. Unless the architecture is very > > > different from MT8183, I'd suggest splitting it. > > > > > > On a general note, the MT8183 SenInf driver has received several > > > rounds of review comments already, but I couldn't find any comments > > > posted for this one. > > > > > > Given the two aspects above and also based on my quick look at code > > > added by this series, I'd recommend adding MT2712 support on top of > > > the MT8183 series. > > > > In [1], "mediatek,mt8183-seninf" use one device to control multiple csi > > instance, so it duplicate many register definition. In [2], one > > "mediatek,mt2712-mipicsi" device control one csi instance, so there are > > multiple device and the register definition does not duplicate. > > I guess we didn't catch that in the review yet. It should be fixed. > > > You > > recommend adding MT2712 support on top of the MT8183 series, do you mean > > that "mediatek,mt2712-mipicsi" should use one device to control multiple > > csi instance and duplicate the register setting? > > There are some aspects of MT8183 series that are done better than the > MT2712 series, but apparently there are also some better aspects in > MT2712. We should take the best aspects of both series. :) Stu: Are the two devices similar enough or not; does this look like a feasible approach to you? -- Sakari Ailus