On 04/24/2014 09:52 PM, Greg KH wrote: > On Mon, Apr 14, 2014 at 01:46:11PM +0200, Robert Baldyga wrote: >> This patchset adds many improvements to extcon class driver and extcon >> provider drivers. It changes extcon API to faster and safer by replaceing >> function taking extcon and cable names with functions working with >> structures representing this objects. > > What is "faster" exactly? How did you measure this? What benchmarks > can be run to test this claim? > Most of new API functions are O(1), because they take as argument pointer to struct extcon_cable, and operates on it. In contrast, previous API functions needed to compare given cable name with name of each cable specified in extcon controller. This solution was also prone to errors - when you make typo in extcon name or cable name it will not be detected at compilation time. The new API uses names only at initialization, and after that each function takes pointer to struct extcon_cable. The old API is also fragile because defined list of cables could be different in each extcon provider (the same cable could have different name in each extcon provider), so using different extcon providers with different drivers would need doing modifications in drivers. Best regards Robert Baldyga Samsung R&D Institute Poland -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
