From: Mauro Carvalho Chehab <mchehab@s-opensource.com>
To: Brad Love <brad@nextdimension.cc>
Cc: linux-media@vger.kernel.org
Subject: Re: [PATCH 2/9] em28xx: Bulk transfer implementation fix
Date: Tue, 30 Jan 2018 10:07:50 -0200 [thread overview]
Message-ID: <20180130100750.06487d7a@vela.lan> (raw)
In-Reply-To: <1515110659-20145-3-git-send-email-brad@nextdimension.cc>
Em Thu, 4 Jan 2018 18:04:12 -0600
Brad Love <brad@nextdimension.cc> escreveu:
> Set appropriate bulk/ISOC transfer multiplier on capture start.
> This sets ISOC transfer to 940 bytes (188 * 5)
> This sets bulk transfer to 48128 bytes (188 * 256)
>
> The above values are maximum allowed according to Empia.
>
> Signed-off-by: Brad Love <brad@nextdimension.cc>
> ---
> drivers/media/usb/em28xx/em28xx-core.c | 12 ++++++++++++
> 1 file changed, 12 insertions(+)
>
> diff --git a/drivers/media/usb/em28xx/em28xx-core.c b/drivers/media/usb/em28xx/em28xx-core.c
> index ef38e56..67ed6a3 100644
> --- a/drivers/media/usb/em28xx/em28xx-core.c
> +++ b/drivers/media/usb/em28xx/em28xx-core.c
> @@ -638,6 +638,18 @@ int em28xx_capture_start(struct em28xx *dev, int start)
> dev->chip_id == CHIP_ID_EM28174 ||
> dev->chip_id == CHIP_ID_EM28178) {
> /* The Transport Stream Enable Register moved in em2874 */
> + if (dev->dvb_xfer_bulk) {
> + /* Max Tx Size = 188 * 256 = 48128 - LCM(188,512) * 2 */
> + em28xx_write_reg(dev, (dev->ts == PRIMARY_TS) ?
> + EM2874_R5D_TS1_PKT_SIZE :
> + EM2874_R5E_TS2_PKT_SIZE,
> + 0xFF);
> + } else {
> + /* TS2 Maximum Transfer Size = 188 * 5 */
> + em28xx_write_reg(dev, (dev->ts == PRIMARY_TS) ?
> + EM2874_R5D_TS1_PKT_SIZE :
> + EM2874_R5E_TS2_PKT_SIZE, 0x05);
> + }
Hmm... for ISOC, the USB descriptors inform the max transfer size, with
are detected at probe time, on this part of em28xx_usb_probe:
if (size > dev->dvb_max_pkt_size_isoc) {
has_dvb = true; /* see NOTE (~) */
dev->dvb_ep_isoc = e->bEndpointAddress;
dev->dvb_max_pkt_size_isoc = size;
dev->dvb_alt_isoc = i;
}
If we're touching TS PKT size register, it should somehow be
aligned what's there. I mean, we should either do:
em28xx_write_reg(dev, (dev->ts == PRIMARY_TS) ?
EM2874_R5D_TS1_PKT_SIZE :
EM2874_R5E_TS2_PKT_SIZE, dev->dvb_max_pkt_size_isoc / 188);
Or the other way around, setting dev->dvb_max_pkt_size_isoc after
writing to EM2874_R5D_TS1_PKT_SIZE or EM2874_R5E_TS2_PKT_SIZE.
Not sure what's more accurate here: the USB descriptors or the
contents of the TS size register. I doubt, I would stick with
the USB descriptor info.
Btw, I wander what happens if we write a bigger value than 5 to those
registers. Would it support a bigger transfer size than 940 for ISOCH?
Cheers,
Mauro
next prev parent reply other threads:[~2018-01-30 12:08 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-05 0:04 [PATCH 0/9] Hauppauge em28xx/lgdt3306a soloHD/DualHD support Brad Love
2018-01-05 0:04 ` [PATCH 1/9] em28xx: Hauppauge DualHD second tuner functionality Brad Love
2018-01-05 0:21 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 2/9] em28xx: Bulk transfer implementation fix Brad Love
2018-01-05 0:22 ` Michael Ira Krufky
2018-01-05 14:20 ` Devin Heitmueller
2018-01-05 15:21 ` Brad Love
2018-01-30 19:56 ` Brad Love
2018-01-30 12:07 ` Mauro Carvalho Chehab [this message]
2018-01-30 19:33 ` Brad Love
2018-02-01 22:04 ` [PATCH v2 " Brad Love
2018-01-05 0:04 ` [PATCH 3/9] em28xx: USB bulk packet size fix Brad Love
2018-01-05 0:23 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 4/9] em28xx: Increase max em28xx boards to max dvb adapters Brad Love
2018-01-05 0:23 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 5/9] em28xx: Add Hauppauge SoloHD/DualHD bulk models Brad Love
2018-01-05 0:24 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 6/9] em28xx: Enable Hauppauge SoloHD rebranded 292e SE Brad Love
2018-01-05 0:24 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 7/9] lgdt3306a: Set fe ops.release to NULL if probed Brad Love
2018-01-05 0:19 ` Michael Ira Krufky
2018-01-05 1:37 ` Brad Love
2018-01-09 5:17 ` Matthias Schwarzott
2018-01-09 13:00 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 8/9] lgdt3306a: QAM streaming improvement Brad Love
2018-01-05 0:26 ` Michael Ira Krufky
2018-01-05 1:34 ` Brad Love
2018-01-05 1:30 ` [PATCH v2 " Brad Love
2018-01-05 11:57 ` Michael Ira Krufky
2018-01-05 0:04 ` [PATCH 9/9] lgdt3306a: Add QAM AUTO support Brad Love
2018-01-05 0:27 ` Michael Ira Krufky
2018-02-12 20:52 ` [PATCH v2 " Brad Love
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=20180130100750.06487d7a@vela.lan \
--to=mchehab@s-opensource.com \
--cc=brad@nextdimension.cc \
--cc=linux-media@vger.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