From: Sean Young <sean@mess.org>
To: A Sun <as1033x@comcast.net>
Cc: linux-media@vger.kernel.org, Mauro Carvalho Chehab <mchehab@kernel.org>
Subject: Re: [PATCH v2 2/3] [media] mceusb: Reword messages referring to "urb"
Date: Sat, 10 Aug 2019 13:17:24 +0100 [thread overview]
Message-ID: <20190810121724.7oo7uoggxg4hha6i@gofer.mess.org> (raw)
In-Reply-To: <49527290-a5b0-4b4f-c93a-ac54ff52edc8@comcast.net>
Hi,
On Sun, Jul 21, 2019 at 05:31:55PM -0400, A Sun wrote:
> FYI, I'm in progress on another mceusb patch to fix, and eliminate, the driver's
> TX IR length limits. Limit causes -EINVAL errors for > ~300 pulse/space samples and
> I've seen reports (and patches for) of appliances with IR over 400 pulse/spaces.
This always looked like it needed improvement. Thank you!
>
> The future patch rewrites:
> mceusb_tx_ir()
> And revises "write/tx" async I/O to sync I/O to do unlimited multipart TX IR.
> These functions will need rewrite and rename:
> mce_async_callback() -> mce_tx_callback()
> mce_request_packet() -> mce_tx()
> The present mce_async_out() name will become misleading. mce_command_out()
> or mce_request_out() (which calls mce_tx()), are probably better names.
>
> I'm still mulling over whether the more generic "read/write" term
> (e.g. mce_write() and mce_write_callback()) may be a better migration path,
> for future work.
Thanks.
Another thing the mceusb driver could do with is usb wakeup. I've hadn't
had the time to look at that.
Sean
next prev parent reply other threads:[~2019-08-10 12:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <999ae5cd-d72b-983f-2f96-5aaca72e8214@comcast.net>
2019-06-01 23:34 ` [PATCH v1 1/3] [media] mceusb: Disable "nonsensical irdata" messages A Sun
2019-06-01 23:34 ` [PATCH v1 2/3] [media] mceusb: Reword messages referring to "urb" A Sun
2019-06-01 23:35 ` [PATCH v1 3/3] [media] mceusb: Show USB halt/stall error recovery A Sun
2019-06-06 9:53 ` Sean Young
2019-06-06 21:11 ` A Sun
2019-06-08 8:37 ` Sean Young
2019-06-09 0:56 ` A Sun
2019-06-19 7:53 ` [PATCH v2 0/3] [media] mceusb: Error message text revisions A Sun
2019-06-19 7:53 ` [PATCH v2 1/3] [media] mceusb: Disable "nonsensical irdata" messages A Sun
2019-06-19 7:54 ` [PATCH v2 2/3] [media] mceusb: Reword messages referring to "urb" A Sun
2019-06-25 10:51 ` Sean Young
2019-06-25 15:01 ` A Sun
2019-06-25 16:12 ` Sean Young
2019-06-25 21:29 ` A Sun
2019-07-15 12:28 ` Sean Young
2019-07-21 21:31 ` A Sun
2019-08-10 12:17 ` Sean Young [this message]
2019-06-19 7:54 ` [PATCH v2 3/3] [media] mceusb: Show USB halt/stall error recovery A Sun
2019-07-15 2:54 ` A Sun
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20190810121724.7oo7uoggxg4hha6i@gofer.mess.org \
--to=sean@mess.org \
--cc=as1033x@comcast.net \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).