[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAHp75Vdok4WxH9b2q1GK7W_mcmNW-OuReC0y1wLQH9YLYqupmg@mail.gmail.com>
Date: Thu, 7 May 2020 12:06:24 +0300
From: Andy Shevchenko <andy.shevchenko@...il.com>
To: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc: Alan Cooper <alcooperx@...il.com>,
": Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>,
Alan Stern <stern@...land.harvard.edu>,
BCM Kernel Feedback <bcm-kernel-feedback-list@...adcom.com>,
DTML <devicetree@...r.kernel.org>,
Krzysztof Kozlowski <krzk@...nel.org>,
USB list <linux-usb@...r.kernel.org>,
Mathias Nyman <mathias.nyman@...el.com>,
Rob Herring <robh+dt@...nel.org>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@...esas.com>,
Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Subject: Re: [PATCH v6 3/4] usb: ehci: Add new EHCI driver for Broadcom STB SoC's
On Thu, May 7, 2020 at 9:41 AM Greg Kroah-Hartman
<gregkh@...uxfoundation.org> wrote:
> On Thu, May 07, 2020 at 12:01:16AM +0300, Andy Shevchenko wrote:
> > On Wed, May 6, 2020 at 11:23 PM Alan Cooper <alcooperx@...il.com> wrote:
> > > On Tue, May 5, 2020 at 7:00 AM Greg Kroah-Hartman
> > > <gregkh@...uxfoundation.org> wrote:
> > > > > + /* Hook the hub control routine to work around a bug */
> > > >
> > > > What bug? This feels wrong.
> > >
> > > The bug is explained in a comment above the ehci_brcm_hub_control()
> > > routine as follows:
> > > /*
> > > * ehci_brcm_hub_control
> > > * Intercept echi-hcd request to complete RESUME and align it to the start
> > > * of the next microframe.
> > > * If RESUME is complete too late in the microframe, host controller
> > > * detects babble on suspended port and resets the port afterwards.
> > > * This s/w workaround allows to avoid this problem.
> > > * See SWLINUX-1909 for more details
> > > */
> > > I'll remove the internal bug tracking reference from the comment.
> >
> > I guess you may leave the internal bug reference. I can tell from my
> > experience that's hard to understand what was going on in the driver
> > in years perspective. It will help whoever in this company have a
> > chance to look after the driver.
>
> "internal bug references" mean nothing to the 99% of the people that can
> see this. Document the heck out of what this is instead please.
As far as I understand the bug is being described in the same file
somewhere else, that's why internal reference *on top of explanation*
would be valid.
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists