diff options
author | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-04-08 01:02:49 -0300 |
---|---|---|
committer | Mauro Carvalho Chehab <mchehab@redhat.com> | 2010-05-19 12:57:02 -0300 |
commit | b320f80a6a02bbf31f7ed6ab3332f7c4ebaaac2c (patch) | |
tree | 56dc5821a102227fc0d7b676dd53425ee9c1d2a9 /scripts | |
parent | 626cf6979e99bf2c642456308bed7bb25a37569b (diff) | |
download | talos-op-linux-b320f80a6a02bbf31f7ed6ab3332f7c4ebaaac2c.tar.gz talos-op-linux-b320f80a6a02bbf31f7ed6ab3332f7c4ebaaac2c.zip |
V4L/DVB: ir-core: properly present the supported and current protocols
Hardware decoders have a more limited set of decoders than software ones.
In general, they support just one protocol at a given time, but allow
changing between a few options.
Rename the previous badly named "current_protocol" as just "protocol",
meaning the current protocol(s) accepted by the driver, and
add a "support_protocols" to represent the entire universe of supported
protocols by that specific hardware.
As commented on http://lwn.net/Articles/378884/, the "one file, one value"
rule doesn't fit nor does make much sense for bitmap or enum values. So, the
supported_protocols will enum all supported protocols, and the protocol
will present all active protocols.
Signed-off-by: Mauro Carvalho Chehab <mchehab@redhat.com>
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions