- 12 Aug, 2015 27 commits
-
-
Bryan O'Donoghue authored
In order to facilitate grabbing a timestamp that doesn't include greybus overhead, this patch adds a timestamp right before usb_submit_urb() for both es1.c and es2.c. Long term the timestmaping of messages like this probably wants to go away but, for the moment it may have some use to the firmware people instrumenting the performance of the system. Signed-off-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@google.com>
-
Bryan O'Donoghue authored
For the ES2 test activity it may be beneficial to have a performance metric that doesn't include any of the greybus stack malloc, workqueues etc. In order to faciltate, this patch adds a simple kfifo structure to hold two timestamp values. One timestamp will represent the last reasonable point a greybus outbound timestamp can be taken, the other timestamp will represent the first reasonable point an inbound timestamp can be taken. In order to facilitate this model, tracking the timestamps in the connection structure appears to be the best place to keep store of this data. Signed-off-by:
-
Bryan O'Donoghue authored
On device_add() failure in gb_connection_create_range() we jump to err_remove_ida. Instead we should be jumping to err_free_connection, so change the flow to accomodate. Signed-off-by:
-
Viresh Kumar authored
Some of the parameters are not really required, drop them. Signed-off-by:
Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by:
-
Viresh Kumar authored
No more users now, drop it. Signed-off-by:
-
Viresh Kumar authored
These weren't preserved earlier, save them in the connection structure instead of creating its own fields.. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This is done from a common place now, no need to replicate it. Signed-off-by:
-
Viresh Kumar authored
This can (should) be done from a common place as its required for most of the protocols. Do it. Signed-off-by:
-
Viresh Kumar authored
Save major/minor number supported by the module inside connection structure, as this can be used later. Signed-off-by:
-
Viresh Kumar authored
Some request numbers (like invalid and get_version) are same across all protocols. Create common macros for them. Signed-off-by:
-
Viresh Kumar authored
Its possible for connection_init() to fail, in such cases the disconnected event must be sent to the module. It is missing currently, fix it. Signed-off-by:
-
Viresh Kumar authored
!= was used in place of <, while comparing expected and actual payload size. The module may be running a higher version of the protocol and might have some extra fields (towards the end) in the structure, and the AP needs to ignore them. This also updates the print (expected-payload-size < actual-payload-size), when the size doesn't match for requests received by the module. This gives more details required for debugging. Signed-off-by:
-
Viresh Kumar authored
This increases readability a bit more, as it tells which value is actual size and which one is expected size. Signed-off-by:
-
Viresh Kumar authored
Its handled by the firmware driver now, drop the FIXME comment from svc code. Signed-off-by:
-
- 11 Aug, 2015 13 commits
-
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
We already have macros for these, use them instead of writing fixed values. Signed-off-by:
-
Viresh Kumar authored
Minor spell fix. Signed-off-by:
-
Viresh Kumar authored
!= was used in place of <, while comparing expected and actual payload size. The module may be running a higher version of the protocol and might have some extra fields (towards the end) in the structure, and the AP needs to ignore them. This also updates the print (expected-payload-size < actual-payload-size), when the size doesn't match for requests received by the module. This gives more details required for debugging. Signed-off-by:
-
Viresh Kumar authored
Print (expected-payload-size actual-payload-size), when the size doesn't match for requests received by the module. This gives more details required for debugging the issue. Signed-off-by:
Alex Elder <elder@linaro.org> Signed-off-by:
-
Viresh Kumar authored
Print (expected-payload-size actual-payload-size), when the size doesn't match for requests received by the module. This gives more details required for debugging the issue. Signed-off-by:
-
