On Sat, Dec 5, 2009 at 12:30 PM, Mauro Carvalho Chehab <mchehab@xxxxxxxxxxxxx> wrote: > Michael Krufky wrote: >> On Fri, Dec 4, 2009 at 3:02 PM, VDR User <user.vdr@xxxxxxxxx> wrote: >> I have stated that I like Manu's proposal, but I would prefer that the >> get_property (s2api) interface were used, because it totally provides >> an interface that is sufficient for this feature. >> >> Manu and I agree that these values should all be read at once. >> >> I think we all (except Mauro) agree that the behavior within the >> driver should fetch all statistics at once and return it to userspace >> as a single structure with all the information as it all relates to >> each other. > > You're contradicting yourself: by using S2API, the userspace API won't > be using a single structure, since S2API will break them into pairs of > attributes/values. Incorrect. Userspace would issue a get_property call and kernelspace would return a block of key/value pairs. > Nothing limits that the in-kernel API will group those values into a struct, > but the internal API should be smart enough to not return to userspace > the values that weren't requested by the call. The call should be generic, something like get_property_signalstats ... Kernelspace should return all related information, and userspace should pick out what it needs. -Mike -- 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
