From: Tero Kristo <t-kristo@ti.com>
To: "Andrew F. Davis" <afd@ti.com>, Nishanth Menon <nm@ti.com>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] firmware: ti_sci: Always request response from firmware
Date: Tue, 11 Jun 2019 20:31:15 +0300 [thread overview]
Message-ID: <034a2922-1ee2-53b8-04ed-a05a66fda066@ti.com> (raw)
In-Reply-To: <20190528155510.373-1-afd@ti.com>
On 28/05/2019 18:55, Andrew F. Davis wrote:
> TI-SCI firmware will only respond to messages when the
> TI_SCI_FLAG_REQ_ACK_ON_PROCESSED flag is set. Most messages already do
> this, set this for the ones that do not.
>
> This will be enforced in future firmware that better match the TI-SCI
> specifications, this patch will not break users of existing firmware.
>
> Fixes: aa276781a64a ("firmware: Add basic support for TI System Control Interface (TI-SCI) protocol")
> Signed-off-by: Andrew F. Davis <afd@ti.com>
> Acked-by: Nishanth Menon <nm@ti.com>
> Tested-by: Alejandro Hernandez <ajhernandez@ti.com>
> ---
>
> Changes from v1:
> - Rebased on v5.2-rc2
Thanks, queuing up for 5.3.
-Tero
>
> drivers/firmware/ti_sci.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/firmware/ti_sci.c b/drivers/firmware/ti_sci.c
> index ef93406ace1b..36ce11a67235 100644
> --- a/drivers/firmware/ti_sci.c
> +++ b/drivers/firmware/ti_sci.c
> @@ -466,9 +466,9 @@ static int ti_sci_cmd_get_revision(struct ti_sci_info *info)
> struct ti_sci_xfer *xfer;
> int ret;
>
> - /* No need to setup flags since it is expected to respond */
> xfer = ti_sci_get_one_xfer(info, TI_SCI_MSG_VERSION,
> - 0x0, sizeof(struct ti_sci_msg_hdr),
> + TI_SCI_FLAG_REQ_ACK_ON_PROCESSED,
> + sizeof(struct ti_sci_msg_hdr),
> sizeof(*rev_info));
> if (IS_ERR(xfer)) {
> ret = PTR_ERR(xfer);
> @@ -596,9 +596,9 @@ static int ti_sci_get_device_state(const struct ti_sci_handle *handle,
> info = handle_to_ti_sci_info(handle);
> dev = info->dev;
>
> - /* Response is expected, so need of any flags */
> xfer = ti_sci_get_one_xfer(info, TI_SCI_MSG_GET_DEVICE_STATE,
> - 0, sizeof(*req), sizeof(*resp));
> + TI_SCI_FLAG_REQ_ACK_ON_PROCESSED,
> + sizeof(*req), sizeof(*resp));
> if (IS_ERR(xfer)) {
> ret = PTR_ERR(xfer);
> dev_err(dev, "Message alloc failed(%d)\n", ret);
>
--
Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki. Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2019-06-11 17:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-28 15:55 Andrew F. Davis
2019-06-11 17:31 ` Tero Kristo [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=034a2922-1ee2-53b8-04ed-a05a66fda066@ti.com \
--to=t-kristo@ti.com \
--cc=afd@ti.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=ssantosh@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
all inboxes | Powered by JetHome®