From: Frans Klaver <fransklaver@gmail.com>
To: Reinhard Speyerer <rspmn@arcor.de>
Cc: Johan Hovold <johan@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Frans Klaver <frans.klaver@vislink.com>,
stable@vger.kernel.org
Subject: Re: [PATCH v2] usb: serial: qcserial: add EM9191 support
Date: Fri, 15 Jul 2022 23:28:33 +0200 [thread overview]
Message-ID: <F3F460AC-05D0-4DF9-9C18-B95881B62F8F@gmail.com> (raw)
In-Reply-To: <YtHVfc40VGbB2Tkz@arcor.de>
On July 15, 2022 11:00:45 PM GMT+02:00, Reinhard Speyerer <rspmn@arcor.de> wrote:
>the qcserial driver used in the usb-devices output above does not seem
>to be built from the mainline qcserial.c with your patch applied as USB
>interface 4 is ignored by the QCSERIAL_SWI layout.
Right, I will need to look into that then. I won't be able to access the devices for a couple of weeks, though. It might also just have been me no paying attention while testing. I'll get back to this.
>To avoid potential side effects in case Sierra Wireless adds a vendor class
>USB interface 2 not intended to be used with qcserial.c it might be best
>to use a new QCSERIAL_SWI2 layout similar to what has been done in
>their MBPL drivers mentioned here
>https://forum.sierrawireless.com/t/rc7620-and-linux-driver/24308/ .
I'll have a look at this too.
Thanks,
Frans
prev parent reply other threads:[~2022-07-15 21:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-15 9:56 [PATCH v2] usb: serial: qcserial: add EM9191 support Frans Klaver
2022-07-15 21:00 ` Reinhard Speyerer
2022-07-15 21:28 ` Frans Klaver [this message]
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=F3F460AC-05D0-4DF9-9C18-B95881B62F8F@gmail.com \
--to=fransklaver@gmail.com \
--cc=frans.klaver@vislink.com \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=rspmn@arcor.de \
--cc=stable@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