linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Daniel Scally <djrscally@gmail.com>,
	Heikki Krogerus <heikki.krogerus@linux.intel.com>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>,
	Hans de Goede <hdegoede@redhat.com>,
	linux-usb@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org,
	Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Subject: Re: [PATCH v4 7/7] usb: typec: mux: Add On Semi fsa4480 driver
Date: Mon, 7 Mar 2022 18:13:37 +0200	[thread overview]
Message-ID: <YiYvMf5X+S0WZ9lO@smile.fi.intel.com> (raw)
In-Reply-To: <YiYbOQpX4+fP8S1W@ripper>

On Mon, Mar 07, 2022 at 06:48:25AM -0800, Bjorn Andersson wrote:
> On Mon 07 Mar 02:16 PST 2022, Andy Shevchenko wrote:
> > On Sun, Mar 06, 2022 at 07:40:40PM -0800, Bjorn Andersson wrote:

...

> > > +		/* 15us to allow the SBU switch to turn off */
> > > +		usleep_range(15, 1000);
> > 
> > This is quite unusual range.
> > 
> > If you are fine with the long delay, why to stress the system on it?
> > Otherwise the use of 1000 is unclear.
> > 
> > That said, I would expect one of the below:
> > 
> > 		usleep_range(15, 30);
> > 		usleep_range(500, 1000);
> 
> Glad you asked about that, as you say the typical form is to keep the
> range within 2x of the lower value, or perhaps lower + 5.
> 
> But if the purpose is to specify a minimum time and then give a max to
> give the system some flexibility in it's decision of when to wake up.
> And in situations such as this, we're talking about someone connecting a
> cable, so we're in "no rush" and I picked the completely arbitrary 1ms
> as the max.
> 
> Do you see any drawback of this much higher number? (Other than it
> looking "wrong")

I see the drawback of low number. The 1000 makes not much sense to me with
the minimum 66x times less. If there is no rush, use some reasonable values,
what about

		usleep_range(100, 1000);

? 10x is way better than 66x.

-- 
With Best Regards,
Andy Shevchenko



  reply	other threads:[~2022-03-07 16:14 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-07  3:40 [PATCH v4 1/7] device property: Helper to match multiple connections Bjorn Andersson
2022-03-07  3:40 ` [PATCH v4 2/7] device property: Use multi-connection matchers for single case Bjorn Andersson
2022-03-07  3:40 ` [PATCH v4 3/7] usb: typec: mux: Check dev_set_name() return value Bjorn Andersson
2022-03-07 10:08   ` Andy Shevchenko
2022-03-07 14:33     ` Bjorn Andersson
2022-03-07 14:52       ` Heikki Krogerus
2022-03-07  3:40 ` [PATCH v4 4/7] usb: typec: mux: Introduce indirection Bjorn Andersson
2022-03-07  3:40 ` [PATCH v4 5/7] usb: typec: mux: Allow multiple mux_devs per mux Bjorn Andersson
2022-03-07  3:40 ` [PATCH v4 6/7] dt-bindings: usb: Add binding for fcs,fsa4480 Bjorn Andersson
2022-03-07  3:40 ` [PATCH v4 7/7] usb: typec: mux: Add On Semi fsa4480 driver Bjorn Andersson
2022-03-07 10:16   ` Andy Shevchenko
2022-03-07 14:48     ` Bjorn Andersson
2022-03-07 16:13       ` Andy Shevchenko [this message]
2022-03-07 21:04         ` Bjorn Andersson
2022-03-07 22:13           ` Andy Shevchenko
2022-03-08  0:01             ` Bjorn Andersson
2022-03-07 10:05 ` [PATCH v4 1/7] device property: Helper to match multiple connections Andy Shevchenko
2022-03-07 19:13   ` Bjorn Andersson

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=YiYvMf5X+S0WZ9lO@smile.fi.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=bjorn.andersson@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=djrscally@gmail.com \
    --cc=dmitry.baryshkov@linaro.org \
    --cc=hdegoede@redhat.com \
    --cc=heikki.krogerus@linux.intel.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=sakari.ailus@linux.intel.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).