Received: by 2002:a25:ab43:0:0:0:0:0 with SMTP id u61csp2931818ybi; Mon, 10 Jun 2019 00:59:05 -0700 (PDT) X-Google-Smtp-Source: APXvYqxIFKXm8nrOqiHkKeaq6mXc2PFXTrklcxKNBFwP3VMb870/0qkoDDmhbFSAabyqnucQ5A12 X-Received: by 2002:a17:90a:21ac:: with SMTP id q41mr20337072pjc.31.1560153545249; Mon, 10 Jun 2019 00:59:05 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1560153545; cv=none; d=google.com; s=arc-20160816; b=fRgQrieme0fV1qYTmTKL40ti879VIXklh8nH1QlNmoSHO6brmZUeKCsQiOtAhr0GdX a3RiLK7ONFZloufLhsdIACSUXc9nO8U/zOi3vSHYqyASV/937fpjAY42TotdQDo0coSy N9KKwXXvC8xbA1skcAlFEFbDRzbWfFs62Hx9Od8yXvfBrnhsphrrab++756Hy6Q2VZXH V4BnACFaXaICJC1JQ97ukfmBYbcybN9y45sS+GinusGnGRZV2mdMKUShVXJ9epmm1RzZ e3WL475czZwOoPh9oanEj9p86R1wd4xVhtqE10Xw5DFjr5Cx5lqwiZYB69kZjaCna7+B Eibw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=jlJ7kEpQ8wNqI+qin5NIgLFKGHCVC1ANXb/nCDBzTgQ=; b=Dgkz3Sio16x5EOLI38rYjnc81U4uJZMipgFiU9NizioX5ea2bL3EAgrazdJSQbllm4 ZYyc2Zm0GBQK3xaNTNuOWMufPRRJnmhzHnuUuyJEGhCnqmNwbr9pjL8Fpq8CnbokSVNe fVtzVb6p8k/WJ/Zrq/E3ZNAvA2E2VbHe+IlPJ2mNgxYLjEnGt9VbXjLeFRkiyUzknSaw hJ3KLmJ8Iv3ENdkR+6CXpnj5g4k57W7uQ0H363x4eTxj5fObaVNlhdB14TmSCwe+zpbd iwJy28C52nFUEMYARY+k5CIvblf9MNIoo/4WWk3SYSmnCHNVHbSsrKAWbCY99YM4F9VF i/4w== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@chromium.org header.s=google header.b=kQL2AZP0; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y17si8665178plp.59.2019.06.10.00.58.50; Mon, 10 Jun 2019 00:59:05 -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; dkim=pass header.i=@chromium.org header.s=google header.b=kQL2AZP0; 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=pass (p=NONE sp=NONE dis=NONE) header.from=chromium.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388301AbfFJH6T (ORCPT + 99 others); Mon, 10 Jun 2019 03:58:19 -0400 Received: from mail-ed1-f66.google.com ([209.85.208.66]:33279 "EHLO mail-ed1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388261AbfFJH6S (ORCPT ); Mon, 10 Jun 2019 03:58:18 -0400 Received: by mail-ed1-f66.google.com with SMTP id h9so13244525edr.0 for ; Mon, 10 Jun 2019 00:58:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=jlJ7kEpQ8wNqI+qin5NIgLFKGHCVC1ANXb/nCDBzTgQ=; b=kQL2AZP0gBm+87LmnpAKPXsOFeHuskGZAqtDENXQ/pKLYBwGsN6NaE81wgpDmot6Hj 7fNmavFRolq1Db2Mq7AZ3WHlDhuOyRXBv8JepydsyiqQKVLjUCQlnmLmgvx6Du80Gl0A MCMu/Pgz4vY3DJg0rAisvrMPjvVdfTJGxc5OQ= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=jlJ7kEpQ8wNqI+qin5NIgLFKGHCVC1ANXb/nCDBzTgQ=; b=qQs1P2p8y6J6HzyFbu51O2ZAMxbMUg+YZ4G/aTuHDOiHFhnSehHZ43swaqdRnmcajC deWE4foT3Rq204fBVhEjB+L2heoJv9PzV3sX2FQ4PmRvvKHNDEcg8rLoU6VUSk7WBqPz AUxtsB4JGlEHKCChWUUZM4ypF7pgdFxYXJzOUWDJIU/e/3Oxov/mkcnjmmd4b0KT53Ao F8dOwjncV7gWyjbqCIGEnNef4EZwnljQ/ETt699UneKxWTYooEGtSbGnnQ/yWizsDS9V Oqs1FTGwIp+JtMDxzcJFI86UXvUxgcRhAxfWTGILBsLDf9TvN1nWlb59ZO1lZYpNlyys LNgA== X-Gm-Message-State: APjAAAW34Eyi+tHukhqfzLgAxx9WzJndh+tHpQKB4UWmBqJ7uBAjotqW 7ffhjCmNwxfqW0D6q1e6yCifIJuK7oBbkQ== X-Received: by 2002:a17:906:2acf:: with SMTP id m15mr58724587eje.31.1560153496027; Mon, 10 Jun 2019 00:58:16 -0700 (PDT) Received: from mail-wm1-f43.google.com (mail-wm1-f43.google.com. [209.85.128.43]) by smtp.gmail.com with ESMTPSA id u26sm2606130edf.91.2019.06.10.00.58.14 for (version=TLS1_3 cipher=AEAD-AES128-GCM-SHA256 bits=128/128); Mon, 10 Jun 2019 00:58:15 -0700 (PDT) Received: by mail-wm1-f43.google.com with SMTP id u8so7161996wmm.1 for ; Mon, 10 Jun 2019 00:58:14 -0700 (PDT) X-Received: by 2002:a7b:cd04:: with SMTP id f4mr13318912wmj.64.1560153493721; Mon, 10 Jun 2019 00:58:13 -0700 (PDT) MIME-Version: 1.0 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> In-Reply-To: <1560153073.31854.6.camel@mtksdaap41> From: Tomasz Figa Date: Mon, 10 Jun 2019 16:58:02 +0900 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v4 01/14] dt-bindings: Add binding for MT2712 MIPI-CSI2 To: CK Hu Cc: Stu Hsieh , 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 Content-Type: text/plain; charset="UTF-8" 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 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. :) Best regards, Tomasz > > [1] https://patchwork.kernel.org/patch/10979121/ > [2] https://patchwork.kernel.org/patch/10974573/ > > Regards, > CK > > > > > Best regards, > > Tomasz > >