Devicetree
 help / color / mirror / Atom feed
From: Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>
To: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/2] media: i2c: Add Samsung S5KJN5 image sensor driver
Date: Fri, 31 Jul 2026 20:39:25 +0300	[thread overview]
Message-ID: <2fcdea3f-8588-40b6-9686-52756dd19d26@linaro.org> (raw)
In-Reply-To: <d5f579a7-b04b-4feb-8d6f-ae6e76e51f60@oss.qualcomm.com>

Hi Wenmeng,

On 7/31/26 11:24, Wenmeng Liu wrote:
> 
> Hi Vladimir,
> On 7/25/2026 3:22 PM, Vladimir Zapolskiy wrote:
>> Hi Wenmeng.
>>
>> On 7/24/26 12:50, Wenmeng Liu wrote:
>>> Add a V4L2 sub-device driver for the Samsung S5KJN5, a 50 MP GBRG 10-bit
>>
>> I believe "GBRG" detalization here will be incorrect, if you consider image
>> flips or odd crops.
>>
>>> RAW MIPI CSI-2 image sensor. The driver supports the 4096x3072 mode and
>>> exposes the standard controls (exposure, gain, vblank/hblank, test
>>> pattern).
>>>
>>> Signed-off-by: Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
>>> ---
>>>    MAINTAINERS                |    1 +
>>>    drivers/media/i2c/Kconfig  |   11 +
>>>    drivers/media/i2c/Makefile |    1 +
>>>    drivers/media/i2c/s5kjn5.c | 2835 ++++++++++++++++++++++++++++++++++
>>> ++++++++++
>>>    4 files changed, 2848 insertions(+)
>>>
>>> diff --git a/MAINTAINERS b/MAINTAINERS
>>> index
>>> 244c7ed5872aa0972a7b055d7e0b19d530820a08..6f6edae5de13efc0cda6c91ab8c9a40bfe2cbff9 100644
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -24195,6 +24195,7 @@ M:    Wenmeng Liu <wenmeng.liu@oss.qualcomm.com>
>>>    L:    linux-media@vger.kernel.org
>>>    S:    Supported
>>>    F:    Documentation/devicetree/bindings/media/i2c/samsung,s5kjn5.yaml
>>> +F:    drivers/media/i2c/s5kjn5.c
>>>    SAMSUNG S5P Security SubSystem (SSS) DRIVER
>>>    M:    Krzysztof Kozlowski <krzk@kernel.org>
>>> diff --git a/drivers/media/i2c/Kconfig b/drivers/media/i2c/Kconfig
>>> index
>>> 7ffccba897ae5637bd0cb913e1e04f9c7d0c89f5..06b5dbc32cab328df8d10da04d91a708bff6fdda 100644
>>> --- a/drivers/media/i2c/Kconfig
>>> +++ b/drivers/media/i2c/Kconfig
>>> @@ -824,6 +824,17 @@ config VIDEO_S5KJN1
>>>          To compile this driver as a module, choose M here: the
>>>          module will be called s5kjn1.
>>> +config VIDEO_S5KJN5
>>> +    tristate "Samsung S5KJN5 sensor support"
>>> +    depends on GPIOLIB
>>> +    select V4L2_CCI_I2C
>>> +    help
>>> +      This is a V4L2 sensor driver for Samsung S5KJN5 50MP GBRG
>>
>> Same comment as above, I believe "GBRG" should be either removed or
>> generalized to "Bayer" or "raw".
>>
>>> +      10-bit RAW MIPI CSI-2 camera sensor.
>>> +
>>> +      To compile this driver as a module, choose M here: the
>>> +      module will be called s5kjn5.
>>> +
>>>    config VIDEO_T4KA3
>>>        tristate "Toshiba T4KA3 sensor support"
>>>        depends on ACPI || COMPILE_TEST
>>> diff --git a/drivers/media/i2c/Makefile b/drivers/media/i2c/Makefile
>>> index
>>> d04bd5724552e88fc2ad39f9bbaf9b4ce1763939..45019ce20a6c34c8139b8247b6904c3abb1a8fe7 100644
>>> --- a/drivers/media/i2c/Makefile
>>> +++ b/drivers/media/i2c/Makefile
>>> @@ -133,6 +133,7 @@ obj-$(CONFIG_VIDEO_S5K3M5) += s5k3m5.o
>>>    obj-$(CONFIG_VIDEO_S5K5BAF) += s5k5baf.o
>>>    obj-$(CONFIG_VIDEO_S5K6A3) += s5k6a3.o
>>>    obj-$(CONFIG_VIDEO_S5KJN1) += s5kjn1.o
>>> +obj-$(CONFIG_VIDEO_S5KJN5) += s5kjn5.o
>>>    obj-$(CONFIG_VIDEO_SAA6588) += saa6588.o
>>>    obj-$(CONFIG_VIDEO_SAA6752HS) += saa6752hs.o
>>>    obj-$(CONFIG_VIDEO_SAA7110) += saa7110.o
>>> diff --git a/drivers/media/i2c/s5kjn5.c b/drivers/media/i2c/s5kjn5.c
>>> new file mode 100644
>>> index
>>> 0000000000000000000000000000000000000000..865db808aabcf7d910acbdab8126b9fa308ef875
>>> --- /dev/null
>>> +++ b/drivers/media/i2c/s5kjn5.c
>>> @@ -0,0 +1,2835 @@
>>> +// SPDX-License-Identifier: GPL-2.0
>>> +/*
>>> + * Samsung S5KJN5 50 MP GBRG 10-bit RAW MIPI CSI-2 sensor driver
>>
>> Same comment as above.
>>
>>> + *
>>> + * Copyright (c) Qualcomm Technologies, Inc. and/or its subsidiaries
>>> + */
>>> +
>>> +#include <linux/clk.h>
>>> +#include <linux/delay.h>
>>> +#include <linux/gpio/consumer.h>
>>> +#include <linux/i2c.h>
>>> +#include <linux/module.h>
>>> +#include <linux/pm_runtime.h>
>>> +#include <linux/regmap.h>
>>> +#include <linux/regulator/consumer.h>
>>> +#include <media/v4l2-cci.h>
>>> +#include <media/v4l2-ctrls.h>
>>> +#include <media/v4l2-device.h>
>>
>> Let me ask, which interface or declaration from media/v4l2-ctrls.h
>> is used in the driver? I have a feeling that it's unused.
>>
> 
> It is required. The driver call many interfaces form it, like
> v4l2_ctrl_new_int_menu/__v4l2_ctrl_handler_setup...

my bad, I stopped at media/v4l2-device.h above, and my question is about
this media/v4l2-device.h header actually, can you please double check,
if the driver uses anything from that header or not?

I wrongly copied a definitely used media/v4l2-ctrls.h to my question,
it was not my intention, sorry.

> And thanks a lot for the review. ACK for the rest, and I'll address them
> in the next revision.
> 

Thank you! I will try my best to review the driver without a great delay.

-- 
Best wishes,
Vladimir

  reply	other threads:[~2026-07-31 17:39 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-07-24  9:50 [PATCH v2 0/2] media: i2c: Add Samsung S5KJN5 image sensor Wenmeng Liu
2026-07-24  9:50 ` [PATCH v2 1/2] dt-bindings: " Wenmeng Liu
2026-07-24 14:12   ` Vladimir Zapolskiy
2026-07-31  8:15     ` Wenmeng Liu
2026-07-24  9:50 ` [PATCH v2 2/2] media: i2c: Add Samsung S5KJN5 image sensor driver Wenmeng Liu
2026-07-24 10:08   ` sashiko-bot
2026-07-25  7:22   ` Vladimir Zapolskiy
2026-07-31  8:24     ` Wenmeng Liu
2026-07-31 17:39       ` Vladimir Zapolskiy [this message]
2026-08-03  2:53         ` Wenmeng Liu
2026-07-25 10:14   ` Vladimir Zapolskiy

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=2fcdea3f-8588-40b6-9686-52756dd19d26@linaro.org \
    --to=vladimir.zapolskiy@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=robh@kernel.org \
    --cc=sakari.ailus@linux.intel.com \
    --cc=wenmeng.liu@oss.qualcomm.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