From: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
To: Changhuang Liang <changhuang.liang@starfivetech.com>
Cc: <conor+dt@kernel.org>, <devarsht@ti.com>,
<devicetree@vger.kernel.org>, <jai.luthra@linux.dev>,
<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-media@vger.kernel.org>, <mchehab@kernel.org>,
<mripard@kernel.org>, <r-donadkar@ti.com>, <robh@kernel.org>,
<u-kumar1@ti.com>, <vaishnav.a@ti.com>
Subject: Re: [PATCH v2 2/2] media: cadence: csi2rx: Enable csi2rx_err_irq interrupt and add support for VIDIOC_LOG_STATUS
Date: Fri, 21 Feb 2025 10:43:27 +0530 [thread overview]
Message-ID: <907975b4-9a0b-4e4d-85cb-625c8a61f149@ti.com> (raw)
In-Reply-To: <20250219030226.535893-1-changhuang.liang@starfivetech.com>
Hi Changhuang,
Thanks for the review.
On 19/02/25 08:32, Changhuang Liang wrote:
>> Enable the csi2rx_err_irq interrupt to record any errors during streaming
>> and also add support for VIDIOC_LOG_STATUS ioctl. The VIDIOC_LOG_STATUS
>> ioctl can be invoked from user space to retrieve the device status,
>> including details about any errors.
>>
>> Signed-off-by: Yemike Abhilash Chandra <y-abhilashchandra@ti.com>
>> ---
>
> [...]
>
>> @@ -665,7 +752,7 @@ static int csi2rx_probe(struct platform_device *pdev)
>> {
>> struct csi2rx_priv *csi2rx;
>> unsigned int i;
>> - int ret;
>> + int irq, ret;
>>
>> csi2rx = kzalloc(sizeof(*csi2rx), GFP_KERNEL);
>> if (!csi2rx)
>> @@ -703,6 +790,19 @@ static int csi2rx_probe(struct platform_device *pdev)
>> if (ret)
>> goto err_cleanup;
>>
>> + irq = platform_get_irq_byname_optional(to_platform_device(csi2rx->dev), "error");
>
> Can use the "pdev" directly ?
Yes, will correct this in v3.
Thanks and Regards,
Yemike Abhilash Chandra.
>
>> + if (irq < 0) {
>> + dev_dbg(csi2rx->dev, "Optional interrupt not defined, proceeding without it\n");
>> + } else {
>> + ret = devm_request_irq(csi2rx->dev, irq, csi2rx_irq_handler, 0,
>> + "csi2rx-irq", csi2rx);
>> + if (ret) {
>> + dev_err(csi2rx->dev, "Unable to request interrupt: %d\n", ret);
>> + return ret;
>> + }
>> + }
>> +
>> ret = v4l2_subdev_init_finalize(&csi2rx->subdev);
>> if (ret)
>> goto err_cleanup;
>> --
>> 2.34.1
>>
prev parent reply other threads:[~2025-02-21 5:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-17 13:00 [PATCH v2 0/2] Enable support for error detection in CSI2RX Yemike Abhilash Chandra
2025-02-17 13:00 ` [PATCH v2 1/2] dt-bindings: media: cdns,csi2rx.yaml: Add optional interrupts for cdns-csi2rx Yemike Abhilash Chandra
2025-02-18 8:32 ` Jai Luthra
2025-02-18 9:35 ` 回复: " Changhuang Liang
2025-02-18 15:37 ` Jai Luthra
2025-02-21 5:01 ` Yemike Abhilash Chandra
2025-02-18 8:38 ` Krzysztof Kozlowski
2025-02-17 13:00 ` [PATCH v2 2/2] media: cadence: csi2rx: Enable csi2rx_err_irq interrupt and add support for VIDIOC_LOG_STATUS Yemike Abhilash Chandra
2025-02-18 8:09 ` Jai Luthra
2025-02-21 5:11 ` Yemike Abhilash Chandra
2025-02-19 3:02 ` Changhuang Liang
2025-02-21 5:13 ` Yemike Abhilash Chandra [this message]
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=907975b4-9a0b-4e4d-85cb-625c8a61f149@ti.com \
--to=y-abhilashchandra@ti.com \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devarsht@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jai.luthra@linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=mripard@kernel.org \
--cc=r-donadkar@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--cc=vaishnav.a@ti.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