From: patchwork-bot+linux-arm-msm@kernel.org
To: Carl Huang <cjhuang@codeaurora.org>
Cc: linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH v3] mhi: use irq_flags if controller driver configures it
Date: Mon, 01 Mar 2021 19:59:45 +0000 [thread overview]
Message-ID: <161462878513.6187.1357336605257034749.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20210104101128.8217-1-cjhuang@codeaurora.org>
Hello:
This patch was applied to qcom/linux.git (refs/heads/for-next):
On Mon, 4 Jan 2021 18:11:28 +0800 you wrote:
> If controller driver has specified the irq_flags, mhi uses this specified
> irq_flags. Otherwise, mhi uses default irq_flags.
>
> The purpose of this change is to support one MSI vector for QCA6390.
> MHI will use one same MSI vector too in this scenario.
>
> In case of one MSI vector, IRQ_NO_BALANCING is needed when irq handler
> is requested. The reason is if irq migration happens, the msi_data may
> change too. However, the msi_data is already programmed to QCA6390
> hardware during initialization phase. This msi_data inconsistence will
> result in crash in kernel.
>
> [...]
Here is the summary with links:
- [v3] mhi: use irq_flags if controller driver configures it
https://git.kernel.org/qcom/c/cdce2663ffb8
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2021-03-01 20:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 10:11 [PATCH v3] mhi: use irq_flags if controller driver configures it Carl Huang
2021-01-04 17:03 ` Manivannan Sadhasivam
2021-01-13 7:40 ` Kalle Valo
2021-01-21 7:52 ` Manivannan Sadhasivam
2021-01-26 10:14 ` Kalle Valo
2021-01-26 15:42 ` Manivannan Sadhasivam
2021-03-01 19:59 ` 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=161462878513.6187.1357336605257034749.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-arm-msm@kernel.org \
--cc=cjhuang@codeaurora.org \
--cc=linux-arm-msm@vger.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