From: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"linux@prisktech.co.nz" <linux@prisktech.co.nz>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-renesas-soc@vger.kernel.org"
<linux-renesas-soc@vger.kernel.org>
Subject: RE: [PATCH 2/2] usb: host: ehci-platform: add a quirk to avoid stuck
Date: Thu, 23 Jan 2020 12:05:39 +0000 [thread overview]
Message-ID: <TYAPR01MB4544D171313D851666905BF1D80F0@TYAPR01MB4544.jpnprd01.prod.outlook.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.2001220956510.1636-100000@iolanthe.rowland.org>
Hi Alan,
> From: Alan Stern, Sent: Wednesday, January 22, 2020 11:59 PM
>
> On Wed, 22 Jan 2020, Yoshihiro Shimoda wrote:
>
> > > Okay, now I understand. I misread the code in the original patch.
> > > But now it looks like the code does roughly this:
> > >
> > > Timer routine: if (ehci_platform_quirk_poll_check_condition(ehci))
> > > schedule_work();
> > >
> > > Work routine: usleep_range(4000, 8000);
> > > udelay(10);
> > > if (!ehci_platform_quirk_poll_check_condition(ehci))
> > > return;
> > > udelay(10);
> > > if (!ehci_platform_quirk_poll_check_condition(ehci))
> > > return;
> > > ehci_platform_quirk_poll_rebind_companion(ehci);
> > >
> > > So there are three calls to quirk_poll_check_condition, with 4 - 8 ms
> > > between the first and second, and 10 us between the second and third.
> > > Do you really need to have this combination of a long delay followed by
> > > a short delay? Wouldn't two check_condition calls with only one delay
> > > be good enough?
> >
> > I had implemented this code by using hardware team's suggestion without
> > any doubt. So, I asked hardware team about this combination of delays.
> > The hardware team said this combination can reduce misdetection ratio
> > from noise and so on. They also said we can wait single 5 ms instead
> > this combination (but this cannot reduce misdetection ratio).
>
> Sure, the more times you delay and recheck, the better the error rate.
> But you don't want to go too far.
You're correct. However, my mind is changed a little...
I would like to remain rechecking as the same as before.
> > So, now I'm thinking that the following process (single wait) is
> > enough and it can improve readability. But, what do you think?
> >
> > Timer routine: if (ehci_platform_quirk_poll_check_condition(ehci))
> > schedule_delayed_work(5 ms);
> >
> > Delayed work routine:
> > if (!ehci_platform_quirk_poll_check_condition(ehci))
> > return;
> > ehci_platform_quirk_poll_rebind_companion(ehci);
>
> That looks good to me.
Thank you for your feedback! I'll submit v2 patch soon.
Best regards,
Yoshihiro Shimoda
> Alan Stern
prev parent reply other threads:[~2020-01-23 12:05 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-17 10:54 [PATCH 0/2] usb: host: ehci-platform: add a quirk to avoid stuck Yoshihiro Shimoda
2020-01-17 10:54 ` [PATCH 1/2] dt-bindings: usb: generic-ehci: add a quirk property " Yoshihiro Shimoda
2020-01-17 16:03 ` Geert Uytterhoeven
2020-01-20 8:05 ` Yoshihiro Shimoda
2020-01-23 8:17 ` Yoshihiro Shimoda
2020-01-23 8:57 ` Geert Uytterhoeven
2020-01-23 12:06 ` Yoshihiro Shimoda
2020-01-17 10:54 ` [PATCH 2/2] usb: host: ehci-platform: add a quirk " Yoshihiro Shimoda
2020-01-17 16:26 ` Alan Stern
2020-01-20 9:33 ` Yoshihiro Shimoda
2020-01-20 15:12 ` Alan Stern
2020-01-21 1:37 ` Yoshihiro Shimoda
2020-01-21 15:09 ` Alan Stern
2020-01-22 11:05 ` Yoshihiro Shimoda
2020-01-22 14:58 ` Alan Stern
2020-01-23 12:05 ` Yoshihiro Shimoda [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=TYAPR01MB4544D171313D851666905BF1D80F0@TYAPR01MB4544.jpnprd01.prod.outlook.com \
--to=yoshihiro.shimoda.uh@renesas.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@prisktech.co.nz \
--cc=mark.rutland@arm.com \
--cc=robh+dt@kernel.org \
--cc=stern@rowland.harvard.edu \
/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).