summaryrefslogtreecommitdiff
path: root/common/test_util.c
diff options
context:
space:
mode:
authorRandall Spangler <rspangler@chromium.org>2013-08-01 09:55:58 -0700
committerChromeBot <chrome-bot@google.com>2013-08-02 13:05:56 -0700
commitc6dfa7e03b4c672e1031b4af9230b9da77e50f1a (patch)
tree63c6a1472c0d7884bb6952d828198cc86d56a035 /common/test_util.c
parent0d3bdc690e7ab3ed0ab190b0529e95c2bbba4e7e (diff)
downloadchrome-ec-c6dfa7e03b4c672e1031b4af9230b9da77e50f1a.tar.gz
Host commands don't set the response pointer
Remove support for allowing host command handlers to set the response pointer. This is just one more thing that can break (and did, on SPI protocol V2). No commands other than the trivial read-memory-map command in host_command.c and flash read made use of this capability, and the savings in performance was negligible. BUG=chrome-os-partner:21576 BRANCH=none TEST=boot pit; still boots Change-Id: I0a9bcf57dbea7155318fc389d7b47d3742a1a00a Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/64236
Diffstat (limited to 'common/test_util.c')
-rw-r--r--common/test_util.c8
1 files changed, 1 insertions, 7 deletions
diff --git a/common/test_util.c b/common/test_util.c
index 10e718399f..c133ac9d24 100644
--- a/common/test_util.c
+++ b/common/test_util.c
@@ -70,7 +70,6 @@ int test_send_host_command(int command, int version, const void *params,
int params_size, void *resp, int resp_size)
{
struct host_cmd_handler_args args;
- int rv;
args.version = version;
args.command = command;
@@ -80,12 +79,7 @@ int test_send_host_command(int command, int version, const void *params,
args.response_max = resp_size;
args.response_size = 0;
- rv = host_command_process(&args);
-
- if (args.response != resp)
- memcpy(resp, args.response, args.response_size);
-
- return rv;
+ return host_command_process(&args);
}
#endif /* TASK_HAS_HOSTCMD */