From: Neil Armstrong <neil.armstrong@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Linus Walleij <linus.walleij@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-gpio@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] pinctrl: qcom: handle intr_target_reg wakeup_present/enable bits
Date: Fri, 27 Oct 2023 15:28:23 +0200 [thread overview]
Message-ID: <85b5ea04-a0d8-4c31-abb6-8778dcb8a9be@linaro.org> (raw)
In-Reply-To: <vtr3s7fyrionospnmzvm2xl2plsue2jlrc3tjifqua3ihucxao@6hxi3i22bwxs>
On 26/10/2023 04:10, Bjorn Andersson wrote:
> On Wed, Oct 25, 2023 at 09:33:52AM +0200, Neil Armstrong wrote:
>> New platforms uses a new set of bits to control the wakeirq
>> delivery to the PDC block.
>>
>> The intr_wakeup_present_bit indicates if the GPIO supports
>> wakeirq and intr_wakeup_enable_bit enables wakeirq delivery
>> to the PDC block.
>>
>> While the name seems to imply this only enables wakeup events,
>> it is required to allow interrupts events to the PDC block.
>>
>> Enable this bit in the irq resource request/free if:
>> - gpio is in wakeirq map
>> - has the intr_wakeup_present_bit
>> - the intr_wakeup_enable_bit is set
>>
>> Signed-off-by: Neil Armstrong <neil.armstrong@linaro.org>
>> ---
>> drivers/pinctrl/qcom/pinctrl-msm.c | 32 ++++++++++++++++++++++++++++++++
>> drivers/pinctrl/qcom/pinctrl-msm.h | 5 +++++
>> 2 files changed, 37 insertions(+)
>>
>> diff --git a/drivers/pinctrl/qcom/pinctrl-msm.c b/drivers/pinctrl/qcom/pinctrl-msm.c
>> index 395040346d0f..2489a9ac8455 100644
>> --- a/drivers/pinctrl/qcom/pinctrl-msm.c
>> +++ b/drivers/pinctrl/qcom/pinctrl-msm.c
>> @@ -1196,6 +1196,7 @@ static int msm_gpio_irq_reqres(struct irq_data *d)
>> {
>> struct gpio_chip *gc = irq_data_get_irq_chip_data(d);
>> struct msm_pinctrl *pctrl = gpiochip_get_data(gc);
>> + const struct msm_pingroup *g = &pctrl->soc->groups[d->hwirq];
>> int ret;
>>
>> if (!try_module_get(gc->owner))
>> @@ -1221,6 +1222,24 @@ static int msm_gpio_irq_reqres(struct irq_data *d)
>> */
>> irq_set_status_flags(d->irq, IRQ_DISABLE_UNLAZY);
>>
>> + /*
>> + * If the wakeup_enable bit is present and marked as available for the
>> + * requested GPIO, it should be enabled when the GPIO is marked as
>> + * wake irq in order to allow the interrupt event to be transfered to
>> + * the PDC HW.
>> + * While the name implies only the wakeup event, it's also required for
>> + * the interrupt event.
>> + */
>> + if (test_bit(d->hwirq, pctrl->skip_wake_irqs) && g->intr_wakeup_present_bit) {
>> + u32 intr_cfg;
>> +
>> + intr_cfg = msm_readl_intr_cfg(pctrl, g);
>> + if (intr_cfg & BIT(g->intr_wakeup_present_bit)) {
>> + intr_cfg |= BIT(g->intr_wakeup_enable_bit);
>> + msm_writel_intr_cfg(intr_cfg, pctrl, g);
>
> If I understand correctly, the two modified functions are hooked
> straight into the irq_chip, which would imply that nothing prevent
> concurrent execution of this and the other accessors of intr_cfg.
>
> If I'm reading this correctly, I think we should perform this
> read-modify-write under the spinlock.
Yes exact, thanks for pointing this.
Neil
>
> Regards,
> Bjorn
>
>> + }
>> + }
>> +
>> return 0;
>> out:
>> module_put(gc->owner);
>> @@ -1230,6 +1249,19 @@ static int msm_gpio_irq_reqres(struct irq_data *d)
>> static void msm_gpio_irq_relres(struct irq_data *d)
>> {
>> struct gpio_chip *gc = irq_data_get_irq_chip_data(d);
>> + struct msm_pinctrl *pctrl = gpiochip_get_data(gc);
>> + const struct msm_pingroup *g = &pctrl->soc->groups[d->hwirq];
>> +
>> + /* Disable the wakeup_enable bit if it has been set in msm_gpio_irq_reqres() */
>> + if (test_bit(d->hwirq, pctrl->skip_wake_irqs) && g->intr_wakeup_present_bit) {
>> + u32 intr_cfg;
>> +
>> + intr_cfg = msm_readl_intr_cfg(pctrl, g);
>> + if (intr_cfg & BIT(g->intr_wakeup_present_bit)) {
>> + intr_cfg &= ~BIT(g->intr_wakeup_enable_bit);
>> + msm_writel_intr_cfg(intr_cfg, pctrl, g);
>> + }
>> + }
>>
>> gpiochip_unlock_as_irq(gc, d->hwirq);
>> module_put(gc->owner);
>> diff --git a/drivers/pinctrl/qcom/pinctrl-msm.h b/drivers/pinctrl/qcom/pinctrl-msm.h
>> index 4968d08a384d..63852ed70295 100644
>> --- a/drivers/pinctrl/qcom/pinctrl-msm.h
>> +++ b/drivers/pinctrl/qcom/pinctrl-msm.h
>> @@ -58,6 +58,9 @@ struct pinctrl_pin_desc;
>> * @intr_enable_bit: Offset in @intr_cfg_reg for enabling the interrupt for this group.
>> * @intr_status_bit: Offset in @intr_status_reg for reading and acking the interrupt
>> * status.
>> + * @intr_wakeup_present_bit: Offset in @intr_target_reg specifying the GPIO can generate
>> + * wakeup events.
>> + * @intr_wakeup_enable_bit: Offset in @intr_target_reg to enable wakeup events for the GPIO.
>> * @intr_target_bit: Offset in @intr_target_reg for configuring the interrupt routing.
>> * @intr_target_width: Number of bits used for specifying interrupt routing target.
>> * @intr_target_kpss_val: Value in @intr_target_bit for specifying that the interrupt from
>> @@ -100,6 +103,8 @@ struct msm_pingroup {
>> unsigned intr_status_bit:5;
>> unsigned intr_ack_high:1;
>>
>> + unsigned intr_wakeup_present_bit:5;
>> + unsigned intr_wakeup_enable_bit:5;
>> unsigned intr_target_bit:5;
>> unsigned intr_target_width:5;
>> unsigned intr_target_kpss_val:5;
>>
>> --
>> 2.34.1
>>
next prev parent reply other threads:[~2023-10-27 13:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-25 7:33 [PATCH 0/3] pinctrl: qcom: Introduce Pinctrl/GPIO for SM8650 Neil Armstrong
2023-10-25 7:33 ` [PATCH 1/3] dt-bindings: pinctrl: document the SM8650 Top Level Mode Multiplexer Neil Armstrong
2023-10-25 8:10 ` Krzysztof Kozlowski
2023-10-25 7:33 ` [PATCH 2/3] pinctrl: qcom: handle intr_target_reg wakeup_present/enable bits Neil Armstrong
2023-10-25 8:16 ` Krzysztof Kozlowski
2023-10-26 2:10 ` Bjorn Andersson
2023-10-27 13:28 ` Neil Armstrong [this message]
2023-10-25 7:33 ` [PATCH 3/3] pinctrl: qcom: Introduce the SM8650 Top Level Mode Multiplexer driver Neil Armstrong
2023-10-25 8:11 ` 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=85b5ea04-a0d8-4c31-abb6-8778dcb8a9be@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).