From: "Ji-Ze Hong (Peter Hong)" <hpeter@gmail.com>
To: Johan Hovold <johan@kernel.org>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, tom_tsai@fintek.com.tw,
peter_hong@fintek.com.tw,
"Ji-Ze Hong (Peter Hong)" <hpeter+linux_kernel@gmail.com>
Subject: Re: [PATCH V12 1/1] usb:serial: Add Fintek F81532/534 driver
Date: Tue, 29 Nov 2016 10:33:16 +0800 [thread overview]
Message-ID: <a2a89b71-1783-d0f5-46c5-bc2472d24af2@gmail.com> (raw)
In-Reply-To: <20161124150425.GA30963@localhost>
Hi Johan,
Johan Hovold 於 2016/11/24 下午 11:04 寫道:
> On Mon, Nov 14, 2016 at 01:37:59PM +0800, Ji-Ze Hong (Peter Hong) wrote:
>> This driver is for Fintek F81532/F81534 USB to Serial Ports IC.
>> + }
>> +
>> + if (size_bulk_out != F81534_WRITE_BUFFER_SIZE ||
>> + size_bulk_in != F81534_MAX_RECEIVE_BLOCK_SIZE) {
>> + dev_err(dev, "%s: endpoints packet size not matched\n",
>> + __func__);
>
> Similarly: "unsupported endpoint max packet size\n".
>
> But just to be clear: You do want to bail out if connected at full
> speed? You could also ask usb-serial core to allocate large enough
> buffers (e.g. by setting the bulk_out_size driver field) and the host
> controller will handle partitioning.
Yes, this product cannot run on USB full-speed currently due to the
bulk-out endpoint design. It need use 512 bytes packet size to transmit
4 ports TX data, but USB Full-speed only provide 64 byte. The F81534
will treat the all bulk-out data as port 0 although the host will spilt
512byte to 8 x 64bytes packets.
--
With Best Regards,
Peter Hong
next prev parent reply other threads:[~2016-11-29 2:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-14 5:37 [PATCH V12 1/1] usb:serial: Add Fintek F81532/534 driver Ji-Ze Hong (Peter Hong)
2016-11-24 15:04 ` Johan Hovold
2016-11-29 2:33 ` Ji-Ze Hong (Peter Hong) [this message]
2016-11-29 10:05 ` Johan Hovold
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=a2a89b71-1783-d0f5-46c5-bc2472d24af2@gmail.com \
--to=hpeter@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hpeter+linux_kernel@gmail.com \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter_hong@fintek.com.tw \
--cc=tom_tsai@fintek.com.tw \
/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