All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+linux-arm-msm@kernel.org
To: Maulik Shah <mkshah@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH] pinctrl: qcom: Move clearing pending IRQ to .irq_request_resources callback
Date: Tue, 29 Dec 2020 20:15:30 +0000	[thread overview]
Message-ID: <160927293064.13751.12959767285380769665.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <1604561884-10166-1-git-send-email-mkshah@codeaurora.org>

Hello:

This patch was applied to qcom/linux.git (refs/heads/for-next):

On Thu,  5 Nov 2020 13:08:04 +0530 you wrote:
> When GPIOs that are routed to PDC are used as output they can still latch
> the IRQ pending at GIC. As a result the spurious IRQ was handled when the
> client driver change the direction to input to starts using it as IRQ.
> 
> Currently such erroneous latched IRQ are cleared with .irq_enable callback
> however if the driver continue to use GPIO as interrupt and invokes
> disable_irq() followed by enable_irq() then everytime during enable_irq()
> previously latched interrupt gets cleared.
> 
> [...]

Here is the summary with links:
  - pinctrl: qcom: Move clearing pending IRQ to .irq_request_resources callback
    https://git.kernel.org/qcom/c/71266d9d3936

You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



      parent reply	other threads:[~2020-12-29 20:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-05  7:38 [PATCH] pinctrl: qcom: Move clearing pending IRQ to .irq_request_resources callback Maulik Shah
2020-11-10 13:31 ` Linus Walleij
2020-11-10 21:28   ` Bjorn Andersson
2020-11-11 16:09 ` Doug Anderson
2020-12-29 20:15 ` patchwork-bot+linux-arm-msm [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=160927293064.13751.12959767285380769665.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+linux-arm-msm@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=mkshah@codeaurora.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.