linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Pavel Machek <pavel@ucw.cz>, Sebastian Reichel <sre@kernel.org>,
	Kishon Vijay Abraham I <kishon@ti.com>,
	linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
	linux-omap@vger.kernel.org, devicetree@vger.kernel.org,
	Mark Rutland <mark.rutland@arm.com>,
	Marcel Partap <mpartap@gmx.net>,
	Michael Scott <michael.scott@linaro.org>,
	Rob Herring <robh+dt@kernel.org>
Subject: Re: [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4
Date: Mon, 26 Mar 2018 17:45:31 -0700	[thread overview]
Message-ID: <20180327004531.GH5700@atomide.com> (raw)
In-Reply-To: <e756d74aaff6b0a4546944393e1b98bf51ae4900.camel@redhat.com>

* Dan Williams <dcbw@redhat.com> [180326 15:18]:
> On Sun, 2018-03-25 at 13:52 -0700, Tony Lindgren wrote:
> > Anyways, looks like qmi_wwan needs to be loaded before
> > qcserial module, otherwise we get nine ttyUSB instances
> > and ModemManager can't find any modems.
> 
> Use qcaux.c or option, unless the 6600 actually *does* have the same
> layout as Gobi 1K/2K/etc devices.

OK yeah I don't think it's Gobi.

> If you're going to use qcaux or optoin, then you need to use some
> variant of USB_DEVICE_AND_INTERFACE_INFO to lock the serial driver to
> the specific USB interfaces that expose the TTYs and to ignore the QMI
> interfaces and netdevs.

OK thanks I'll take a look and post a patch after some testing.

Regards,

Tony

  reply	other threads:[~2018-03-27  0:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  2:37 [PATCHv4] phy: mapphone-mdm6600: Add USB PHY driver for MDM6600 on Droid 4 Tony Lindgren
2018-03-09  9:44 ` Pavel Machek
2018-03-09 14:52   ` Tony Lindgren
2018-03-22 13:55 ` Pavel Machek
2018-03-22 16:46   ` Tony Lindgren
2018-03-22 19:28     ` Pavel Machek
2018-03-22 22:23       ` Dan Williams
2018-03-23 10:54         ` Pavel Machek
2018-03-23 11:35           ` Sebastian Reichel
2018-03-23 20:13             ` Pavel Machek
2018-03-24 13:59               ` Dan Williams
2018-03-24 14:25                 ` Tony Lindgren
2018-03-24 20:02                   ` Pavel Machek
2018-03-25 15:45                     ` Tony Lindgren
2018-03-25 18:58                       ` Pavel Machek
2018-03-25 20:52                         ` Tony Lindgren
2018-03-25 22:55                           ` Pavel Machek
2018-03-26  0:22                             ` Tony Lindgren
2018-03-26  0:30                               ` Tony Lindgren
2018-03-26 15:16                           ` Dan Williams
2018-03-27  0:45                             ` Tony Lindgren [this message]
2018-03-29 19:44                 ` Pavel Machek

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=20180327004531.GH5700@atomide.com \
    --to=tony@atomide.com \
    --cc=dcbw@redhat.com \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=michael.scott@linaro.org \
    --cc=mpartap@gmx.net \
    --cc=pavel@ucw.cz \
    --cc=robh+dt@kernel.org \
    --cc=sre@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).