From: Greg KH <gregkh@linuxfoundation.org>
To: richard.gong@linux.intel.com
Cc: robh+dt@kernel.org, mark.rutland@arm.com, dinguyen@kernel.org,
atull@kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, sen.li@intel.com,
Richard Gong <richard.gong@intel.com>
Subject: Re: [PATCHv4 2/4] firmware: add Intel Stratix10 remote system update driver
Date: Tue, 28 May 2019 16:22:24 -0700 [thread overview]
Message-ID: <20190528232224.GA29225@kroah.com> (raw)
In-Reply-To: <1559074833-1325-3-git-send-email-richard.gong@linux.intel.com>
On Tue, May 28, 2019 at 03:20:31PM -0500, richard.gong@linux.intel.com wrote:
> +/**
> + * rsu_send_msg() - send a message to Intel service layer
> + * @priv: pointer to rsu private data
> + * @command: RSU status or update command
> + * @arg: the request argument, the bitstream address or notify status
> + * @callback: function pointer for the callback (status or update)
> + *
> + * Start an Intel service layer transaction to perform the SMC call that
> + * is necessary to get RSU boot log or set the address of bitstream to
> + * boot after reboot.
> + *
> + * Returns 0 on success or -ETIMEDOUT on error.
> + */
> +static int rsu_send_msg(struct stratix10_rsu_priv *priv,
> + enum stratix10_svc_command_code command,
> + unsigned long arg,
> + void (*callback)(struct stratix10_svc_client *client,
> + struct stratix10_svc_cb_data *data))
> +{
> + struct stratix10_svc_client_msg msg;
> + int ret;
> +
> + mutex_lock(&priv->lock);
> + reinit_completion(&priv->completion);
> + priv->client.receive_cb = callback;
> +
> + msg.command = command;
> + if (arg)
> + msg.arg[0] = arg;
> +
> + ret = stratix10_svc_send(priv->chan, &msg);
meta-question, can you send messages that are on the stack and not in
DMA-able memory? Or should this be a dynamicly created variable so you
know it can work properly with DMA?
And how big is that structure, will it mess with stack sizes?
thanks,
greg k-h
next prev parent reply other threads:[~2019-05-28 23:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 20:20 [PATCHv4 0/4] add Intel Stratix10 remote system update driver richard.gong
2019-05-28 20:20 ` [PATCHv4 1/4] firmware: stratix10-svc: extend svc to support RSU notify and WD features richard.gong
2019-05-28 20:20 ` [PATCHv4 2/4] firmware: add Intel Stratix10 remote system update driver richard.gong
2019-05-28 23:15 ` Greg KH
2019-05-29 14:15 ` Richard Gong
2019-05-28 23:22 ` Greg KH [this message]
2019-05-29 14:55 ` Richard Gong
2019-06-03 15:57 ` A potential broken at platform driver? Richard Gong
2019-06-03 15:57 ` Richard Gong
2019-06-03 18:02 ` Greg KH
2019-06-03 23:08 ` Richard Gong
2019-06-04 14:28 ` Greg KH
2019-06-04 10:33 ` Romain Izard
2019-06-04 14:28 ` Greg KH
2019-06-04 16:13 ` Richard Gong
2019-06-04 17:03 ` Greg KH
2019-06-11 14:10 ` Richard Gong
2019-06-11 15:47 ` Greg KH
2019-05-28 23:24 ` [PATCHv4 2/4] firmware: add Intel Stratix10 remote system update driver Greg KH
2019-05-29 15:12 ` Richard Gong
2019-05-28 20:20 ` [PATCHv4 3/4] firmware: rsu: document sysfs interface richard.gong
2019-05-28 23:19 ` Greg KH
2019-05-29 15:33 ` Richard Gong
2019-05-28 20:20 ` [PATCHv4 4/4] MAINTAINERS: add maintainer for Intel Stratix10 FW drivers richard.gong
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=20190528232224.GA29225@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=atull@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=richard.gong@intel.com \
--cc=richard.gong@linux.intel.com \
--cc=robh+dt@kernel.org \
--cc=sen.li@intel.com \
/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.