stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: Macpaul Lin <macpaul.lin@mediatek.com>, Lars Melin <larsm17@gmail.com>
Cc: Andrey Arapov <andrey.arapov@gmail.com>,
	Johan Hovold <johan@kernel.org>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Mediatek WSD Upstream <wsd_upstream@mediatek.com>,
	linux-usb@vger.kernel.org, stable@vger.kernel.org
Subject: Re: [PATCH v5] cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader.
Date: Wed, 19 Dec 2018 09:56:22 +0100	[thread overview]
Message-ID: <1545209782.31763.2.camel@suse.com> (raw)
In-Reply-To: <1545192203.4134.11.camel@mtkswgap22>

On Mi, 2018-12-19 at 12:03 +0800, Macpaul Lin wrote:
> On Wed, 2018-12-19 at 10:31 +0700, Lars Melin wrote:
> > On 12/19/2018 10:16, Macpaul Lin wrote: 
> > 
> > Hi Macpaul,
> > your verbose usb listing show me that Mediatek has made two different 
> > 0e8d:003 devices, see my verbose lsusb listing below.
> > (Notice also the reverse order for cmd and data interfaces in it 
> > compared to yours).
> > USB id's are intended to identify a device and its needs so there should
> > never be more than one unique device per id.
> > 
> > 
> > Fairphone FP-1, MT6227  (no CDC union !!!)
> > 
> 
> Hi Lars,
> 
> Ha ha ha, it is a little bit embarrassing.
> What I've used to capture verbose log is MT6765 platform.
> Then I've checked Fairphone FP-1, which is MT6589 a pretty old platform.
> The BROM (boot ROM) has been maintained by other teams and will vary by
> different SoC project in Mediatek. I'm not sure why they changed the
> descriptors.
> 
> For the consistency of BROM's behavior, I'll update a new patch keeps
> PID:0003 remain untouched. I'll trying to report it to BROM team and see
> if they have any action on this issue.

Thank you all for taking care of these important issues.
Please submit that new patch.

	Regards
		Oliver

  reply	other threads:[~2018-12-19  8:56 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1544671676-23912-1-git-send-email-macpaul.lin@mediatek.com>
2018-12-18  5:00 ` [PATCH v2] cdc-acm: fix abnormal DATA RX issue for Mediatek Preloader Macpaul Lin
2018-12-18  9:02   ` Johan Hovold
2018-12-18 10:41 ` [PATCH v3] " Macpaul Lin
2018-12-18 10:54   ` Johan Hovold
2018-12-18 11:38 ` [PATCH v4] " Macpaul Lin
2018-12-18 11:44   ` Johan Hovold
2018-12-18 11:59 ` [PATCH v5] " Macpaul Lin
2018-12-18 12:38   ` Johan Hovold
2018-12-18 13:37     ` Oliver Neukum
2018-12-18 14:26       ` Macpaul Lin
2018-12-18 15:19         ` Macpaul Lin
2018-12-18 16:42           ` Lars Melin
2018-12-18 17:48             ` Macpaul Lin
2018-12-19  0:45               ` Lars Melin
2018-12-19  2:22               ` Macpaul Lin
2018-12-19  3:16                 ` Macpaul Lin
2018-12-19  3:31                   ` Lars Melin
2018-12-19  4:03                     ` Macpaul Lin
2018-12-19  8:56                       ` Oliver Neukum [this message]
2018-12-20 15:19                         ` Greg Kroah-Hartman
2018-12-18 15:37 ` [PATCH v6] " Macpaul Lin
2018-12-19  4:11 ` [PATCH v7] " Macpaul Lin
2018-12-19  9:00   ` Johan Hovold
2018-12-20 15:28     ` Oliver Neukum

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=1545209782.31763.2.camel@suse.com \
    --to=oneukum@suse.com \
    --cc=andrey.arapov@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=johan@kernel.org \
    --cc=larsm17@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=macpaul.lin@mediatek.com \
    --cc=stable@vger.kernel.org \
    --cc=wsd_upstream@mediatek.com \
    /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).