> > mutex_lock(&ir_raw_handler_lock);
> > - list_for_each_entry(handler, &ir_raw_handler_list, list)
> > - handler->decode(raw->dev, ev);
> > + list_for_each_entry(handler, &ir_raw_handler_list, list) {
> > + /* use all protocol by default */
> > + if (raw->dev->allowed_protos == RC_TYPE_UNKNOWN ||
> > + raw->dev->allowed_protos & handler->protocols)
> > + handler->decode(raw->dev, ev);
> > + }
>
> Each IR protocol decoder already checks whether it is enabled or not;
> should it not be so that only allowed protocols can be enabled rather
> than checking both enabled_protocols and allowed_protocols?
>
> Just from reading store_protocols it looks like decoders which aren't
> in allowed_protocols can be enabled, which makes no sense. Also
> ir_raw_event_register all protocols are enabled rather than the
> allowed ones.
>
>
> Lastely I don't know why raw ir drivers should dictate which protocols
> can be enabled. Would it not be better to remove it entirely?
I agree with you. I just thought that the only thing a decoder should care
is its decoding logic, but not including decoder management. My idaea is:
1) use enabled_protocols to select decoders in ir_raw.c, but not
placed in decoders to do the judgement.
2) remove allowed_protocols or just use it to set the default
decoder (also should rename allowed_protocols to default_protocol).
I also have a question:
Is there a requirement that one more decoders are enabled for a
IR device at the same time?
And if that will lead to a issue that each decoder may decode a
same pulse sequence to different evnets since their protocol is
different?
[Du, Changbin]
>
>
> > raw->prev_ev = ev;
> > mutex_unlock(&ir_raw_handler_lock);
> > }
> > --
> > 1.7.9.5
> >
> > --
> > 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
--
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
