lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Mon, 9 Nov 2020 09:37:51 +0100
From:   Alexandre Torgue <alexandre.torgue@...com>
To:     Sakari Ailus <sakari.ailus@...ux.intel.com>
CC:     Hugues Fruchet <hugues.fruchet@...com>,
        Mauro Carvalho Chehab <mchehab@...nel.org>,
        Hans Verkuil <hverkuil@...all.nl>,
        Rob Herring <robh+dt@...nel.org>, <devicetree@...r.kernel.org>,
        <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>, <linux-media@...r.kernel.org>,
        <linux-stm32@...md-mailman.stormreply.com>,
        Alain Volmat <alain.volmat@...com>,
        Yannick Fertre <yannick.fertre@...com>,
        Philippe CORNU <philippe.cornu@...com>
Subject: Re: [PATCH v5 0/4] DCMI BT656 parallel bus mode support

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.

Regards
alex

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ