linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Bixuan Cui <cuibixuan@huawei.com>
Cc: iommu@lists.linux-foundation.org, linux-kernel@vger.kernel.org,
	will@kernel.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: Re: [PATCH -next v3 1/2] platform-msi: Save the msg context to desc in platform_msi_write_msg()
Date: Tue, 14 Sep 2021 11:08:13 +0200	[thread overview]
Message-ID: <YUBmfXx5rVCrFVI/@kroah.com> (raw)
In-Reply-To: <20210828063916.39633-1-cuibixuan@huawei.com>

On Sat, Aug 28, 2021 at 02:39:14PM +0800, Bixuan Cui wrote:
> 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
> 

Acked-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

      parent reply	other threads:[~2021-09-14  9:08 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-28  6:39 [PATCH -next v3 1/2] platform-msi: Save the msg context to desc in platform_msi_write_msg() Bixuan Cui
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 ` Greg KH [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=YUBmfXx5rVCrFVI/@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=cuibixuan@huawei.com \
    --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).