From: Michael Riesch <michael.riesch@wolfvision.net>
To: Tommaso Merciai <tomm.merciai@gmail.com>,
Mehdi Djait <mehdi.djait@bootlin.com>
Cc: mchehab@kernel.org, heiko@sntech.de, hverkuil-cisco@xs4all.nl,
krzysztof.kozlowski+dt@linaro.org, robh+dt@kernel.org,
conor+dt@kernel.org, linux-media@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
thomas.petazzoni@bootlin.com, alexandre.belloni@bootlin.com,
maxime.chevallier@bootlin.com, paul.kocialkowski@bootlin.com
Subject: Re: [PATCH v11 2/3] media: rockchip: Add a driver for Rockchip's camera interface
Date: Wed, 22 Nov 2023 13:42:50 +0100 [thread overview]
Message-ID: <9570dc1c-a437-46d4-95e7-1f3dd399e458@wolfvision.net> (raw)
In-Reply-To: <ZVz58b0r4gtxyVQy@tom-HP-ZBook-Fury-15-G7-Mobile-Workstation>
Hi Tommaso,
On 11/21/23 19:41, Tommaso Merciai wrote:
> Hi Mehdi,
>
> On Thu, Nov 16, 2023 at 12:04:39PM +0100, Mehdi Djait wrote:
>> This introduces a V4L2 driver for the Rockchip CIF video capture controller.
>>
>> This controller supports multiple parallel interfaces, but for now only the
>> BT.656 interface could be tested, hence it's the only one that's supported
>> in the first version of this driver.
>>
>> This controller can be found on RK3066, PX30, RK1808, RK3128 and RK3288,
>> but for now it's only been tested on the PX30.
>>
>> CIF is implemented as a video node-centric driver.
>>
>> Most of this driver was written following the BSP driver from rockchip,
>> removing the parts that either didn't fit correctly the guidelines, or that
>> couldn't be tested.
>>
>> This basic version doesn't support cropping nor scaling and is only
>> designed with one SDTV video decoder being attached to it at any time.
>>
>> This version uses the "pingpong" mode of the controller, which is a
>> double-buffering mechanism.
>>
>> Signed-off-by: Mehdi Djait <mehdi.djait@bootlin.com>
>> ---
>> MAINTAINERS | 7 +
>> drivers/media/platform/rockchip/Kconfig | 1 +
>> drivers/media/platform/rockchip/Makefile | 1 +
>> drivers/media/platform/rockchip/cif/Kconfig | 13 +
>> drivers/media/platform/rockchip/cif/Makefile | 3 +
>> drivers/media/platform/rockchip/cif/capture.c | 1120 +++++++++++++++++
>> drivers/media/platform/rockchip/cif/capture.h | 21 +
>> drivers/media/platform/rockchip/cif/common.h | 129 ++
>> drivers/media/platform/rockchip/cif/dev.c | 302 +++++
>> drivers/media/platform/rockchip/cif/regs.h | 127 ++
>> 10 files changed, 1724 insertions(+)
>> create mode 100644 drivers/media/platform/rockchip/cif/Kconfig
>> create mode 100644 drivers/media/platform/rockchip/cif/Makefile
>> create mode 100644 drivers/media/platform/rockchip/cif/capture.c
>> create mode 100644 drivers/media/platform/rockchip/cif/capture.h
>> create mode 100644 drivers/media/platform/rockchip/cif/common.h
>> create mode 100644 drivers/media/platform/rockchip/cif/dev.c
>> create mode 100644 drivers/media/platform/rockchip/cif/regs.h
>
> Just a logigistic comment on my side for now, sorry :)
> What about use cif-* prefix in front of driver files?
>
> like:
>
> cif-capture.c
> cif-capture.h
> cif-common.h
> cif-dev.c
> cif-regs.h
What would be the rationale here?
IMHO the files are in a folder named cif, so adding this prefix seems
kind of redundant.
That said, if there is a good reason I could live with cif-*.{c,h} as
well, of course. My only request would be to agree on something ASAP.
> Thanks & Regards,
> Tommaso
> [...]
Best regards,
Michael
next prev parent reply other threads:[~2023-11-22 12:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 11:04 [PATCH v11 0/3] " Mehdi Djait
2023-11-16 11:04 ` [PATCH v11 1/3] media: dt-bindings: media: add bindings for Rockchip CIF Mehdi Djait
2023-11-16 12:26 ` Rob Herring
2023-11-16 17:58 ` Conor Dooley
2023-11-16 18:01 ` Conor Dooley
2023-11-17 12:15 ` Michael Riesch
2023-11-16 11:04 ` [PATCH v11 2/3] media: rockchip: Add a driver for Rockchip's camera interface Mehdi Djait
2023-11-17 0:52 ` kernel test robot
2023-11-17 22:25 ` Michael Riesch
2023-11-18 21:35 ` kernel test robot
2023-11-21 10:05 ` Michael Riesch
2023-11-21 18:41 ` Tommaso Merciai
2023-11-22 12:42 ` Michael Riesch [this message]
2023-11-22 13:19 ` Paul Kocialkowski
2023-11-22 14:02 ` Mehdi Djait
2023-11-22 13:33 ` Tommaso Merciai
2023-11-22 13:39 ` Michael Riesch
2023-11-29 15:34 ` Paul Kocialkowski
2023-11-16 11:04 ` [PATCH v11 3/3] arm64: dts: rockchip: Add the " Mehdi Djait
2023-11-17 12:18 ` Michael Riesch
2023-11-17 13:19 ` Paul Kocialkowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9570dc1c-a437-46d4-95e7-1f3dd399e458@wolfvision.net \
--to=michael.riesch@wolfvision.net \
--cc=alexandre.belloni@bootlin.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=mchehab@kernel.org \
--cc=mehdi.djait@bootlin.com \
--cc=paul.kocialkowski@bootlin.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@bootlin.com \
--cc=tomm.merciai@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®