CanInterface: add set_can_params method to set multiple parameters

[Urist-McGit]

This new method allows to set multiple CAN-specific parameters at once instead of over multiple netlink messages.

This is also required for some more obscure devices which might not accept some parameter configurations split over multiple netlink messages.

[fpagliughi]

This does seem like a good idea - to be able to set multiple parameters in a single call. But I'm wondering about maintaining another data structure so similar to InterfaceCanParams. Maybe, but I'm not totally convinced. Should we consider one structure and use a read/modify/write pattern similar to other Linux kernel API's? Or consider another way to structure the data? Shouldn't we also have a builder (pattern) for the parameters to be set?

But if we do go with what you suggest - a separate struct of all optional, settable parameters,

• Did we get all of them?
• Don't we want a matching getter?
• Shouldn't we be able to initialize from InterfaceCanParams?
• Should we reconsider the name? SetCanParams reads like a verb. And these are specifically the interface parameters. So, SettableInterfaceCanParams? Although that is a bit long.