From: Jack Zhu <jack.zhu@starfivetech.com>
To: Mauro Carvalho Chehab <mchehab@kernel.org>,
Robert Foss <rfoss@kernel.org>, Todor Tomov <todor.too@gmail.com>,
<bryan.odonoghue@linaro.org>, Rob Herring <robh+dt@kernel.org>,
"Krzysztof Kozlowski" <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Hans Verkuil <hverkuil-cisco@xs4all.nl>
Cc: <linux-media@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-staging@lists.linux.dev>,
<jack.zhu@starfivetech.com>, <changhuang.liang@starfivetech.com>
Subject: [PATCH v10 7/8] media: staging: media: starfive: camss: Add interrupt handling
Date: Sun, 8 Oct 2023 16:51:53 +0800 [thread overview]
Message-ID: <20231008085154.6757-8-jack.zhu@starfivetech.com> (raw)
In-Reply-To: <20231008085154.6757-1-jack.zhu@starfivetech.com>
Parse interrupt resources and register interrupt handlers.
Signed-off-by: Jack Zhu <jack.zhu@starfivetech.com>
---
.../staging/media/starfive/camss/stf-camss.c | 21 +++++++++++++++++++
1 file changed, 21 insertions(+)
diff --git a/drivers/staging/media/starfive/camss/stf-camss.c b/drivers/staging/media/starfive/camss/stf-camss.c
index f083bc0e6e97..373467322885 100644
--- a/drivers/staging/media/starfive/camss/stf-camss.c
+++ b/drivers/staging/media/starfive/camss/stf-camss.c
@@ -35,6 +35,12 @@ static const char * const stfcamss_resets[] = {
"rst_isp_top_axi",
};
+static const struct stf_isr_data stf_isrs[] = {
+ {"wr_irq", stf_wr_irq_handler},
+ {"isp_irq", stf_isp_irq_handler},
+ {"line_irq", stf_line_irq_handler},
+};
+
static int stfcamss_get_mem_res(struct stfcamss *stfcamss)
{
struct platform_device *pdev = to_platform_device(stfcamss->dev);
@@ -160,6 +166,21 @@ static int stfcamss_probe(struct platform_device *pdev)
stfcamss->dev = dev;
+ for (i = 0; i < ARRAY_SIZE(stf_isrs); ++i) {
+ int irq;
+
+ irq = platform_get_irq(pdev, i);
+ if (irq < 0)
+ return irq;
+
+ ret = devm_request_irq(stfcamss->dev, irq, stf_isrs[i].isr, 0,
+ stf_isrs[i].name, stfcamss);
+ if (ret) {
+ dev_err(dev, "request irq failed: %d\n", ret);
+ return ret;
+ }
+ }
+
stfcamss->nclks = ARRAY_SIZE(stfcamss->sys_clk);
for (i = 0; i < stfcamss->nclks; ++i)
stfcamss->sys_clk[i].id = stfcamss_clocks[i];
--
2.34.1
next prev parent reply other threads:[~2023-10-08 8:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-08 8:51 [PATCH v10 0/8] Add StarFive Camera Subsystem driver Jack Zhu
2023-10-08 8:51 ` [PATCH v10 1/8] media: dt-bindings: Add JH7110 Camera Subsystem Jack Zhu
2023-10-08 8:51 ` [PATCH v10 2/8] media: admin-guide: Add starfive_camss.rst for Starfive " Jack Zhu
2023-10-08 8:51 ` [PATCH v10 3/8] media: staging: media: starfive: camss: Add core driver Jack Zhu
2023-10-08 8:51 ` [PATCH v10 4/8] media: staging: media: starfive: camss: Add video driver Jack Zhu
2023-10-08 8:51 ` [PATCH v10 5/8] media: staging: media: starfive: camss: Add ISP driver Jack Zhu
2023-10-08 8:51 ` [PATCH v10 6/8] media: staging: media: starfive: camss: Add capture driver Jack Zhu
2023-10-08 8:51 ` Jack Zhu [this message]
2023-10-08 8:51 ` [PATCH v10 8/8] media: staging: media: starfive: camss: Register devices Jack Zhu
2023-10-16 10:09 ` [PATCH v10 0/8] Add StarFive Camera Subsystem driver Jack Zhu
2023-10-16 11:40 ` Hans Verkuil
2023-10-18 2:37 ` Jack Zhu
2023-10-18 8:48 ` Jack Zhu
2023-10-18 8:50 ` Hans Verkuil
2023-10-18 9:25 ` Jack Zhu
2023-10-18 9:31 ` Hans Verkuil
2023-10-18 9:52 ` Jack Zhu
2023-10-18 9:56 ` Hans Verkuil
2023-10-19 9:02 ` Hans Verkuil
2023-10-18 3:11 ` Jack Zhu
2023-10-18 7:12 ` Hans Verkuil
2023-10-18 11:49 ` Laurent Pinchart
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=20231008085154.6757-8-jack.zhu@starfivetech.com \
--to=jack.zhu@starfivetech.com \
--cc=bryan.odonoghue@linaro.org \
--cc=changhuang.liang@starfivetech.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=hverkuil-cisco@xs4all.nl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rfoss@kernel.org \
--cc=robh+dt@kernel.org \
--cc=todor.too@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.