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=-5.3 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, USER_AGENT_SANE_1 autolearn=no 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 B68A8C5517A for ; Mon, 9 Nov 2020 23:46:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 593C721D40 for ; Mon, 9 Nov 2020 23:46:46 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730140AbgKIXqp (ORCPT ); Mon, 9 Nov 2020 18:46:45 -0500 Received: from mga03.intel.com ([134.134.136.65]:55405 "EHLO mga03.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727311AbgKIXqp (ORCPT ); Mon, 9 Nov 2020 18:46:45 -0500 IronPort-SDR: ARip3f3Q5s2qAx3piaL9nkJdSJITktv8PFawiWibhHy4MSOoq9BgAF86XsoHsdVp/IOu59V7Wm KphL295KnIhQ== X-IronPort-AV: E=McAfee;i="6000,8403,9800"; a="170001075" X-IronPort-AV: E=Sophos;i="5.77,464,1596524400"; d="scan'208";a="170001075" X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga005.jf.intel.com ([10.7.209.41]) by orsmga103.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Nov 2020 15:46:44 -0800 IronPort-SDR: 8yHss2GP6+rx8lVgQdr/uzPkKA29kGB2KjnH0jlk4TvqNbcBsIWE49xMSQn2O3Fv4/GjzKsE0J 28pYfrGVjMbA== X-IronPort-AV: E=Sophos;i="5.77,464,1596524400"; d="scan'208";a="541089940" Received: from paasikivi.fi.intel.com ([10.237.72.42]) by orsmga005-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 09 Nov 2020 15:46:41 -0800 Received: by paasikivi.fi.intel.com (Postfix, from userid 1000) id 89C3220867; Tue, 10 Nov 2020 01:46:38 +0200 (EET) Date: Tue, 10 Nov 2020 01:46:38 +0200 From: Sakari Ailus To: Alexandre Torgue Cc: Hugues Fruchet , Mauro Carvalho Chehab , Hans Verkuil , Rob Herring , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, linux-media@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, Alain Volmat , Yannick Fertre , Philippe CORNU Subject: Re: [PATCH v5 0/4] DCMI BT656 parallel bus mode support Message-ID: <20201109234638.GQ26150@paasikivi.fi.intel.com> References: <1604511132-4014-1-git-send-email-hugues.fruchet@st.com> <016661fc-e9dd-bd4a-f26d-00e54626f030@st.com> <20201106115308.GO26150@paasikivi.fi.intel.com> <027a0bb1-788e-dc73-a941-4d55c8ec5481@st.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <027a0bb1-788e-dc73-a941-4d55c8ec5481@st.com> User-Agent: Mutt/1.10.1 (2018-07-13) Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Mon, Nov 09, 2020 at 09:37:51AM +0100, Alexandre Torgue wrote: > Hi Sakari > > On 11/6/20 12:53 PM, Sakari Ailus wrote: > > Hi Alexandre, > > > > On Thu, Nov 05, 2020 at 10:26:37AM +0100, Alexandre Torgue wrote: > > > Hi Huges > > > > > > On 11/4/20 6:32 PM, Hugues Fruchet wrote: > > > > Add support of BT656 embedded synchronization bus. > > > > This mode allows to save hardware synchro lines hsync & vsync > > > > by replacing them with synchro codes embedded in data stream. > > > > Add "bus-type" property and make it required so that there is no > > > > ambiguity between parallel mode (bus-type=5) and BT656 mode (bus-type=6). > > > > > > > > =========== > > > > = history = > > > > =========== > > > > version 5: > > > > - Add revisited bindings and devicetree with explicit use of "bus-type" > > > > > > > > version 4: > > > > - Fix typo in commit message > > > > > > > > version 3: > > > > - Fix bus_width print to %u as per Sakari comment > > > > > > > > version 2: > > > > - As per Sakari remark, revisit commit message and document > > > > BT656 parallel bus mode in bindings > > > > > > > > version 1: > > > > - Initial submission > > > > > > > > Hugues Fruchet (4): > > > > media: stm32-dcmi: add support of BT656 bus > > > > media: dt-bindings: media: st,stm32-dcmi: add support of BT656 bus > > > > ARM: dts: stm32: set bus-type in DCMI endpoint for stm32mp157c-ev1 > > > > board > > > > ARM: dts: stm32: set bus-type in DCMI endpoint for stm32429i-eval > > > > board > > > > > > > > .../devicetree/bindings/media/st,stm32-dcmi.yaml | 38 ++++++++++++++++++++++ > > > > arch/arm/boot/dts/stm32429i-eval.dts | 1 + > > > > arch/arm/boot/dts/stm32mp157c-ev1.dts | 1 + > > > > drivers/media/platform/stm32/stm32-dcmi.c | 37 +++++++++++++++++++-- > > > > 4 files changed, 75 insertions(+), 2 deletions(-) > > > > > > > > > > I'll take DT patches on stm32-next tree. > > > > Just checking: that is only the two last patches in the set, or also the > > binding patch? > > Usually I let drivers/subsystem maintainer taking dt-bindings patches with > drivers patches. > (If binding changes come only with dts(i) patches I take them in my tree) > > -->So yes I'll take only the last two patches. Ack, thanks! -- Sakari Ailus