From: Mirela Rabulea <mirela.rabulea@nxp.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: mchehab@kernel.org, sakari.ailus@linux.intel.com,
hverkuil-cisco@xs4all.nl,
laurent.pinchart+renesas@ideasonboard.com, robh@kernel.org,
krzk+dt@kernel.org, bryan.odonoghue@linaro.org,
laurentiu.palcu@nxp.com, robert.chiras@nxp.com,
linux-media@vger.kernel.org, linux-kernel@vger.kernel.org,
LnxRevLi@nxp.com, kieran.bingham@ideasonboard.com,
hdegoede@redhat.com, dave.stevenson@raspberrypi.com,
mike.rudenko@gmail.com, alain.volmat@foss.st.com,
devicetree@vger.kernel.org, conor+dt@kernel.org,
alexander.stein@ew.tq-group.com, umang.jain@ideasonboard.com,
zhi.mao@mediatek.com, festevam@denx.de,
julien.vuillaumier@nxp.com, alice.yuan@nxp.com
Subject: Re: Re: [PATCH v3 4/4] media: ox05b1s: Add support for Omnivision OS08A20 raw sensor
Date: Mon, 3 Feb 2025 10:43:50 +0200 [thread overview]
Message-ID: <56fe323f-ee09-4a60-ab57-be2baab3af30@nxp.com> (raw)
In-Reply-To: <20250124-bizarre-cherry-mayfly-9f2bce@krzk-bin>
Hi Krzysztof,
thanks again for feedback.
On 24.01.2025 10:09, Krzysztof Kozlowski wrote:
> On Fri, Jan 24, 2025 at 02:12:43AM +0200, Mirela Rabulea wrote:
>> @@ -758,6 +914,9 @@ static int ox05b1s_read_chip_id(struct ox05b1s *sensor)
>> }
>>
>> switch (chip_id) {
>> + case 0x530841:
>> + camera_name = "os08a20";
>> + break;
> Ah, so here I see missing second device support.
>
> It is still confusing to see that you use here some sort of
> autodetection, but in the same time not.
The two sensors that I included in this driver have some similarities,
but also differences, for which I used the platform data. I made
separate patches for the two sensors, such that it is visible how much
is common/different. The chip_id reading is for validating that the
sensor that is actually attached matches the device tree. It happens to
me sometimes, that I switch the sensors, but forget to switch the dtb,
and it helps to see which sensor is actually attached. Also, it helps a
lot when the evaluation board is in some remote lab and I am unsure what
sensor is attached to it.
I saw most sensor drivers have some kind of identification of the sensor
module by the means of reading the chip_id register. Some examples with
multiple compatibles supported and chip_id validation: imx296, ov9650,
ov772x.
Please let me know what you suggest further.
For your other comments, I did prepare more structures to become const,
hope I did not miss any, it will be in the next version.
Thanks,
Mirela
>
>
>> case 0x580542:
>> camera_name = "ox05b1s";
>> break;
>> @@ -900,6 +1059,24 @@ static void ox05b1s_remove(struct i2c_client *client)
>> static DEFINE_RUNTIME_DEV_PM_OPS(ox05b1s_pm_ops, ox05b1s_runtime_suspend,
>> ox05b1s_runtime_resume, NULL);
>>
>> +static const struct ox05b1s_plat_data os08a20_data = {
>> + .name = "os08a20",
>> + .chip_id = 0x530841,
>> + .native_width = 3872, /* 16 dummy + 3840 active pixels + 16 dummy */
>> + .native_height = 2192, /* 16 dummy + 2160 active lines + 16 dummy */
>> + .active_top = 16,
>> + .active_left = 16,
>> + .active_width = 3840,
>> + .active_height = 2160,
>> + .supported_modes = os08a20_supported_modes,
>> + .default_mode_index = 0,
>> + .supported_codes = os08a20_supported_codes,
>> + .hdr_modes = os08a20_hdr_modes,
>> + .hdr_modes_count = ARRAY_SIZE(os08a20_hdr_modes),
>> + .set_hdr_mode = os08a20_set_hdr_mode,
>> +
>> +};
>> +
>> static const struct ox05b1s_plat_data ox05b1s_data = {
>> .name = "ox05b1s",
>> .chip_id = 0x580542,
>> @@ -912,9 +1089,16 @@ static const struct ox05b1s_plat_data ox05b1s_data = {
>> .supported_modes = ox05b1s_supported_modes,
>> .default_mode_index = 0,
>> .supported_codes = ox05b1s_supported_codes,
>> + .hdr_modes = NULL,
>> + .hdr_modes_count = 0,
>> + .set_hdr_mode = NULL,
>> };
>>
>> static const struct of_device_id ox05b1s_of_match[] = {
>> + {
>> + .compatible = "ovti,os08a20",
>> + .data = &os08a20_data,
> And here static configuration of model, not autodetection.
>
>
> Best regards,
> Krzysztof
>
next prev parent reply other threads:[~2025-02-03 8:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 0:12 [PATCH v3 0/4] media: i2c: Add OX05B1S camera sensor driver Mirela Rabulea
2025-01-24 0:12 ` [PATCH v3 1/4] dt-bindings: media: i2c: Add OX05B1S sensor Mirela Rabulea
2025-01-24 8:02 ` Krzysztof Kozlowski
2025-01-24 0:12 ` [PATCH v3 2/4] media: ox05b1s: Add omnivision OX05B1S raw sensor driver Mirela Rabulea
2025-01-24 6:56 ` Christophe JAILLET
2025-01-24 8:07 ` Krzysztof Kozlowski
2025-02-03 13:32 ` Laurent Pinchart
2025-02-03 13:45 ` Markus Elfring
2025-01-24 0:12 ` [PATCH v3 3/4] MAINTAINERS: Add entry for OX05B1S " Mirela Rabulea
2025-01-24 0:12 ` [PATCH v3 4/4] media: ox05b1s: Add support for Omnivision OS08A20 raw sensor Mirela Rabulea
2025-01-24 7:03 ` Christophe JAILLET
2025-01-24 8:09 ` Krzysztof Kozlowski
2025-02-03 8:43 ` Mirela Rabulea [this message]
2025-02-03 11:36 ` Krzysztof Kozlowski
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=56fe323f-ee09-4a60-ab57-be2baab3af30@nxp.com \
--to=mirela.rabulea@nxp.com \
--cc=LnxRevLi@nxp.com \
--cc=alain.volmat@foss.st.com \
--cc=alexander.stein@ew.tq-group.com \
--cc=alice.yuan@nxp.com \
--cc=bryan.odonoghue@linaro.org \
--cc=conor+dt@kernel.org \
--cc=dave.stevenson@raspberrypi.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@denx.de \
--cc=hdegoede@redhat.com \
--cc=hverkuil-cisco@xs4all.nl \
--cc=julien.vuillaumier@nxp.com \
--cc=kieran.bingham@ideasonboard.com \
--cc=krzk+dt@kernel.org \
--cc=krzk@kernel.org \
--cc=laurent.pinchart+renesas@ideasonboard.com \
--cc=laurentiu.palcu@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mike.rudenko@gmail.com \
--cc=robert.chiras@nxp.com \
--cc=robh@kernel.org \
--cc=sakari.ailus@linux.intel.com \
--cc=umang.jain@ideasonboard.com \
--cc=zhi.mao@mediatek.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