From: Bixuan Cui <cuibixuan@huawei.com>
To: <iommu@lists.linux-foundation.org>, <linux-kernel@vger.kernel.org>
Cc: <will@kernel.org>, <gregkh@linuxfoundation.org>,
<rafael@kernel.org>, <robin.murphy@arm.com>, <joro@8bytes.org>,
<jean-philippe@linaro.org>, <Jonathan.Cameron@huawei.com>,
<thunder.leizhen@huawei.com>, <maz@kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH -next v3 1/2] platform-msi: Save the msg context to desc in platform_msi_write_msg()
Date: Sat, 28 Aug 2021 14:39:14 +0800 [thread overview]
Message-ID: <20210828063916.39633-1-cuibixuan@huawei.com> (raw)
Save the msg context to desc when the msi interrupt is requested.
The drivers can use it in special scenarios(such as resume).
Signed-off-by: Bixuan Cui <cuibixuan@huawei.com>
---
drivers/base/platform-msi.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/base/platform-msi.c b/drivers/base/platform-msi.c
index 3d6c8f9caf43..60962a224fcc 100644
--- a/drivers/base/platform-msi.c
+++ b/drivers/base/platform-msi.c
@@ -90,6 +90,9 @@ static void platform_msi_write_msg(struct irq_data *data, struct msi_msg *msg)
priv_data = desc->platform.msi_priv_data;
+ desc->msg.address_lo = msg->address_lo;
+ desc->msg.address_hi = msg->address_hi;
+ desc->msg.data = msg->data;
priv_data->write_msg(desc, msg);
}
--
2.17.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2021-08-28 6:45 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-28 6:39 Bixuan Cui [this message]
2021-08-28 6:39 ` [PATCH -next v3 2/2] iommu/arm-smmu-v3: Add suspend and resume support Bixuan Cui
2021-09-14 9:08 ` [PATCH -next v3 1/2] platform-msi: Save the msg context to desc in platform_msi_write_msg() Greg KH
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=20210828063916.39633-1-cuibixuan@huawei.com \
--to=cuibixuan@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=gregkh@linuxfoundation.org \
--cc=iommu@lists.linux-foundation.org \
--cc=jean-philippe@linaro.org \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rafael@kernel.org \
--cc=robin.murphy@arm.com \
--cc=thunder.leizhen@huawei.com \
--cc=will@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).