[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191023161819.GD2819@lahna.fi.intel.com>
Date: Wed, 23 Oct 2019 19:18:19 +0300
From: Mika Westerberg <mika.westerberg@...ux.intel.com>
To: Mario.Limonciello@...l.com
Cc: linux-usb@...r.kernel.org, andreas.noever@...il.com,
michael.jamet@...el.com, YehezkelShB@...il.com,
rajmohan.mani@...el.com,
nicholas.johnson-opensource@...look.com.au, lukas@...ner.de,
gregkh@...uxfoundation.org, stern@...land.harvard.edu,
anthony.wong@...onical.com, oneukum@...e.com, ckellner@...hat.com,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/25] thunderbolt: Add support for USB4
On Wed, Oct 23, 2019 at 03:55:48PM +0000, Mario.Limonciello@...l.com wrote:
> > I did not yet add the hw_vendor_id and hw_product_id attributes because I
> > clocked that 'dd if=nvm_activeX/nvmem of=/dev/null bs=64 count=2' (that's
> > what fwupd does) takes typically less than 10 ms when the controller is powered
> > on. That should not slow down fwupd. We can add them later if it is really a
> > problem (I'm just trying to avoid adding too much attributes that we need to
> > maintain forever).
>
> Maybe the controller going into D3 is the key to why it measured slow for me when
> I checked.
Yeah, that's most likely the case.
Powered by blists - more mailing lists