From: "Csókás Bence" <csokas.bence@prolan.hu>
To: <Dharma.B@microchip.com>, <linux-arm-kernel@lists.infradead.org>,
<linux-iio@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <kamel.bouhara@bootlin.com>, <wbg@kernel.org>
Subject: Re: [PATCH v3 1/2] counter: microchip-tcb-capture: Add IRQ handling
Date: Mon, 10 Feb 2025 10:49:07 +0100 [thread overview]
Message-ID: <3f424600-33d3-403b-9df6-85f7cb97c9a6@prolan.hu> (raw)
In-Reply-To: <ed8b9d03-0f03-4872-b9e0-ab670e307450@microchip.com>
Hi,
On 2025. 02. 07. 9:12, Dharma.B@microchip.com wrote:
> can we have macros for the channel (3rd argument) for better clarity?
I myself have also thought about that, even about adding an uapi header.
Thoughts?
>> +static int mchp_tc_irq_enable(struct counter_device *const counter)
>
> Can we have it as mchp_tc_irq_init ?
Why, what's wrong with the current name? It requests IRQ servicing from
Linux, then writes the peripheral's Interrupt Enable Register.
>> +{
>> + struct mchp_tc_data *const priv = counter_priv(counter);
>> + int ret = devm_request_irq(counter->parent, priv->irq, mchp_tc_isr, 0,
>> + dev_name(counter->parent), counter);
>> +
>> + if (ret < 0)
>> + return ret;
>> +
>> + ret = regmap_write(priv->regmap, ATMEL_TC_REG(priv->channel[0], IER), ATMEL_TC_DEF_IRQS);
>> + if (ret < 0)
>> + return ret;
>> +
>> + ret = devm_add_action_or_reset(counter->parent, mchp_tc_irq_remove, priv);
>> + if (ret < 0)
>> + return ret;
>> +
>> + return 0;
>> +}
>> +
>> static void mchp_tc_clk_remove(void *ptr)
>> {
>> clk_disable_unprepare((struct clk *)ptr);
>> @@ -378,6 +438,13 @@ static int mchp_tc_probe(struct platform_device *pdev)
>> counter->num_signals = ARRAY_SIZE(mchp_tc_count_signals);
>> counter->signals = mchp_tc_count_signals;
>>
>> + priv->irq = of_irq_get(np->parent, 0);
>> + if (priv->irq > 0) {
>> + ret = mchp_tc_irq_enable(counter);
>
> missing error handling in irq retrieval (check for -EPROBE_DEFER).
Hmm, what should happen on `priv->irq == -EPROBE_DEFER`? `return
-EPROBE_DEFER`?
Bence
next prev parent reply other threads:[~2025-02-10 9:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20250205104957.95236-1-csokas.bence@prolan.hu>
2025-02-05 10:49 ` [PATCH v3 1/2] counter: microchip-tcb-capture: Add IRQ handling Bence Csókás
2025-02-05 10:50 ` [PATCH v3 0/2] microchip-tcb-capture: Add Capture, Compare, Overflow etc. events Bence Csókás
2025-02-06 17:32 ` Dharma.B
2025-02-07 8:12 ` [PATCH v3 1/2] counter: microchip-tcb-capture: Add IRQ handling Dharma.B
2025-02-10 9:49 ` Csókás Bence [this message]
2025-02-05 10:49 ` [PATCH v3 2/2] counter: microchip-tcb-capture: Add capture extensions for registers RA-RC Bence Csókás
2025-02-07 8:19 ` Dharma.B
2025-02-10 9:56 ` Csókás Bence
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=3f424600-33d3-403b-9df6-85f7cb97c9a6@prolan.hu \
--to=csokas.bence@prolan.hu \
--cc=Dharma.B@microchip.com \
--cc=kamel.bouhara@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=wbg@kernel.org \
/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.