13 Feb
2013
13 Feb
'13
12:34 p.m.
On Wed, Feb 13, 2013 at 08:37:15AM +0100, Takashi Iwai wrote:
Vinod Koul wrote:
On Wed, Feb 13, 2013 at 07:23:32AM +0100, Takashi Iwai wrote:
But this makes difficult to know which parameter is unavailable in this kernel, as already mentioned in the thread. You need to add another ioctl or add a mask in the struct. Or, take back to single key/value pairs, so user can see the -ENOENT or such error for non-existing parameters.
Right, but we have the API version.
But what if a driver doesn't support a particular metadata? Or would you mandate for every driver to support all metadata?
I tend to agree with Takashi here, it seems better if we can have drivers able to implement only a subset of features especially if the API does get extended.