- 29 Jul, 2015 15 commits
-
-
Viresh Kumar authored
Signed-off-by:
Viresh Kumar <viresh.kumar@linaro.org> Signed-off-by:
Greg Kroah-Hartman <gregkh@google.com>
-
Viresh Kumar authored
The svc connection needs to be ready before creating the URBs, otherwise the svc version request might come in before the AP was ready to parse them. Signed-off-by:
-
Greg Kroah-Hartman authored
The function is only called locally, so mark it static to make sparse happy. Tested-by:
-
Greg Kroah-Hartman authored
The callback is never used anymore, so remove it from struct greybus_host_driver as well as from the es1 and es2 drivers. Tested-by:
-
Greg Kroah-Hartman authored
The function is gone, remove it from the header file as well. Tested-by:
-
Perry Hung authored
The AP needs to be able to specify L4 CPort flags and traffic class parameters on a connection-by-connection basis. Extend the connection create operation to accept these. Since there's no policy to decide these, fix them at TC0 with end-to-end-flow control, controlled segment dropping, and CPort safety valve enabled. Tested-by:
Perry Hung <perry@leaflabs.com> Signed-off-by:
-
Perry Hung authored
Ask the SVC to do all the necessary bits for creating a new connection. This is skipped for the initial SVC connection. Tested-by:
-
Perry Hung authored
Upon receiving a hotplug request, we need to prepare the routing table to allow packets to flow between the AP interface and the newly detected interface. Tested-by:
-
Perry Hung authored
Implement the SVC Protocol Route Create Operation. Tested-by:
-
Viresh Kumar authored
Its not used anymore as we have more sophisticated svc protocol in place, lets get rid of earlier code. Signed-off-by:
-
Greg Kroah-Hartman authored
We have switched over to use the "new" svc messages, no more need to have a special USB endpoint to handle them, they come through the normal CPort messages. Based on a patch from Viresh. Tested-by:
-
Greg Kroah-Hartman authored
We have switched over to use the "new" svc messages, no more need to have a special USB endpoint to handle them, they come through the normal CPort messages. Based on a patch from Viresh. Tested-by:
-
Viresh Kumar authored
Initially we fixed it to Cport 2, but its changed to Cport 0 now. Lets switch that in code as well. Signed-off-by:
-
Viresh Kumar authored
All bits and pieces are in place now. Lets start using svc protocol instead of stuff present in ap.c. Signed-off-by:
-
Greg Kroah-Hartman authored
The firmware for the svc changes isn't quite ready, so revert the whole set of patches in one hunk to get things back to a working state for the other firmware developers. The svc patches will be added back in a separate branch. Signed-off-by:
-
- 28 Jul, 2015 6 commits
-
-
Bryan O'Donoghue authored
The depth of the kfifo used to log the latency data for user-space can be moved upwards or downward by way of a module parameter. The user may still specify a test set that's larger than the number of kfifo elements we have available. If the user specifies more iterations than can be logged give a warning as feedback and continue with the test. Signed-off-by:
Bryan O'Donoghue <bryan.odonoghue@linaro.org> Signed-off-by:
-
Bryan O'Donoghue authored
The current loopback code provides the minimum, maximum and average latency values for a given test set. It would be highly useful for user-space to have access to each one of the latency metrics in order to graph outliers. This patch adds a simple character device interface implmenting a read() interface that allows user-space to read out the saved latency metrics which have been stored in a kfifo for this purpose. A module parameter is provided to allow varying the depth of the kfifo in order to allow a user to capture potentially large data sets. This version sets the default depth for the kfifo at 8192 dwords. Signed-off-by:
-
Bryan O'Donoghue authored
Current code allows a sysfs callback and a kernel worker thread to write all over and act upon data that could be in the process of being updated by the other. This patch adds a reasonably coarse mutex to enscure sync between the two. Signed-off-by:
-
Bryan O'Donoghue authored
It is of more interest to graphing system performance to base our timestamps on the time it takes a greybus_operation_sync() to complete. Higher level timestamping code is less accurate and not relevant to throughput and latency characterization. Signed-off-by:
-
Viresh Kumar authored
Its really part of initializing the host device and is required for every 'hd' that is created. Lets move the call to do basic initialization of svc connection to greybus_create_hd(). Also add a comment to specify why we need to do it that early. Signed-off-by:
-
Greg Kroah-Hartman authored
We forgot to free any ida internal structures that were used by this host controller structure when we free the memory for the controller. So fix that up by doing so in the release function. Signed-off-by:
-
- 27 Jul, 2015 14 commits
-
-
Viresh Kumar authored
Signed-off-by:
-
Viresh Kumar authored
The svc connection needs to be ready before creating the URBs, otherwise the svc version request might come in before the AP was ready to parse them. Signed-off-by:
-
Greg Kroah-Hartman authored
The function is only called locally, so mark it static to make sparse happy. Tested-by:
-
Greg Kroah-Hartman authored
The callback is never used anymore, so remove it from struct greybus_host_driver as well as from the es1 and es2 drivers. Tested-by:
-
Greg Kroah-Hartman authored
The function is gone, remove it from the header file as well. Tested-by:
-
Perry Hung authored
The AP needs to be able to specify L4 CPort flags and traffic class parameters on a connection-by-connection basis. Extend the connection create operation to accept these. Since there's no policy to decide these, fix them at TC0 with end-to-end-flow control, controlled segment dropping, and CPort safety valve enabled. Tested-by:
-
Perry Hung authored
Ask the SVC to do all the necessary bits for creating a new connection. This is skipped for the initial SVC connection. Tested-by:
-
Perry Hung authored
Upon receiving a hotplug request, we need to prepare the routing table to allow packets to flow between the AP interface and the newly detected interface. Tested-by:
-
Perry Hung authored
Implement the SVC Protocol Route Create Operation. Tested-by:
-
Viresh Kumar authored
Its not used anymore as we have more sophisticated svc protocol in place, lets get rid of earlier code. Signed-off-by:
-
Greg Kroah-Hartman authored
We have switched over to use the "new" svc messages, no more need to have a special USB endpoint to handle them, they come through the normal CPort messages. Based on a patch from Viresh. Tested-by:
-
Greg Kroah-Hartman authored
We have switched over to use the "new" svc messages, no more need to have a special USB endpoint to handle them, they come through the normal CPort messages. Based on a patch from Viresh. Tested-by:
-
Viresh Kumar authored
Initially we fixed it to Cport 2, but its changed to Cport 0 now. Lets switch that in code as well. Signed-off-by:
-
Viresh Kumar authored
All bits and pieces are in place now. Lets start using svc protocol instead of stuff present in ap.c. Signed-off-by:
-
- 25 Jul, 2015 1 commit
-
-
Viresh Kumar authored
SVC protocol isn't per interface, but per entire entire endo. And so svc cport id must be matched against hd_cport_id, not per-interface cport id. Fixes: 82edfac17e5f ("connection: don't send connected/disconnected events for SVC connection") Signed-off-by:
-
- 24 Jul, 2015 4 commits
-
-
Perry Hung authored
If a protocol was not successfully created, we can't drop the refcount on it. This might happen for example if the connection fails to bind a protocol. Silences a warning on cleanup. Signed-off-by:
-
Perry Hung authored
If an operation times out or otherwise returns an error, val->intval should not be set and an error-code should be returned. Fixes a panic on unload while receiving -ENOTCONN. Signed-off-by:
-
Viresh Kumar authored
Its not referenced by svc or any other code anymore, lets stop exposing it to rest of the files. Signed-off-by:
-
Viresh Kumar authored
Its not updated/used anymore, remove it. Also move back the struct gb_svc to svc.c as its not referenced by external users anymore. Signed-off-by:
-
