Hi Hans, On 12/13/2011 01:18 PM, Hans Verkuil wrote: >> are you going to carry on with the control range update patches ? >> I'd like to push the alpha colour control for v3.3 but it depends >> on the controls framework updates now. > > Good question. I am not sure whether this is something we actually want. It > would make applications much harder to write if the range of a control can > suddenly change. > > On the other hand, it might be a good solution for a harder problem which is > as yet unsolved: if you have multiple inputs, and each input has a different > set of controls (e.g. one input is a SDTV receiver, the other is a HDTV > receiver), then you can have the situation where e.g. the contrast control is > present for both inputs, but with a different range. Switching inputs would > then generate a control event telling the app that the range changed. > > But this may still be overkill... Hmm, it doesn't look like an overkill to me. I'm certain there will be use cases where control range update is needed. Maybe we could specify in the API in what circumstances the control range update is allowed for drivers. So not all applications need to handle the related events. Nevertheless I won't be pushing on this, not to mess around in the whole API because of some embedded systems requirements. So I'm going to update the range for alpha control manually in the driver for the time being. > > In other words, I don't know. Not helpful, I agree. That was helpful anyway :-) Thanks. -- Regards, Sylwester -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
