From: <Mario.Limonciello@dell.com>
To: <andreas.noever@gmail.com>, <michael.jamet@intel.com>,
<mika.westerberg@linux.intel.com>, <YehezkelShB@gmail.com>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: RE: [PATCH 0/2] Allow breaking up Thunderbolt/USB4 updates
Date: Mon, 22 Jun 2020 14:39:36 +0000 [thread overview]
Message-ID: <40e7c39346244df283859ffa90e26a0d@AUSX13MPC105.AMER.DELL.COM> (raw)
In-Reply-To: <20200622143035.25327-1-mario.limonciello@dell.com>
> -----Original Message-----
> From: Limonciello, Mario <Mario_Limonciello@Dell.com>
> Sent: Monday, June 22, 2020 9:31 AM
> To: Andreas Noever; Michael Jamet; Mika Westerberg; Yehezkel Bernat
> Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org; Limonciello,
> Mario
> Subject: [PATCH 0/2] Allow breaking up Thunderbolt/USB4 updates
>
> Currently updates to Thunderbolt and USB4 controllers are fully atomic
> actions. When writing into the non-active NVM nothing gets flushed to
> the hardware until authenticate is sent.
>
> There has been some desire to improve the perceived performance of these
> updates, particularly for userland that may perform the update upon
> a performance sensitive time like logging out.
>
> So allow userland to flush the image to hardware at runtime, and then
> allow authenticating the image at another time.
>
> For the Dell WD19TB some specific hardware capability exists that allows
> extending this to automatically complete the update when unplugged.
> Export that functionality to userspace as well.
>
> This patch series is done relative thunderbolt.git/next.
>
> Mario Limonciello (2):
> thunderbolt: Add support for separating the flush to SPI and
> authenticate
> thunderbolt: Add support for authenticate on disconnect
>
> .../ABI/testing/sysfs-bus-thunderbolt | 24 +++++-
> drivers/thunderbolt/Makefile | 1 +
> drivers/thunderbolt/eeprom.c | 2 +
> drivers/thunderbolt/lc.c | 14 ++++
> drivers/thunderbolt/quirks.c | 38 +++++++++
> drivers/thunderbolt/switch.c | 81 +++++++++++++++----
> drivers/thunderbolt/tb-quirks.h | 16 ++++
> drivers/thunderbolt/tb.h | 4 +
> drivers/thunderbolt/tb_regs.h | 1 +
> 9 files changed, 162 insertions(+), 19 deletions(-)
> create mode 100644 drivers/thunderbolt/quirks.c
> create mode 100644 drivers/thunderbolt/tb-quirks.h
>
> --
> 2.25.1
Just to connect the dots, here is the matching userspace changes for this
change: https://github.com/fwupd/fwupd/pull/2204
next prev parent reply other threads:[~2020-06-22 14:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-22 14:30 [PATCH 0/2] Allow breaking up Thunderbolt/USB4 updates Mario Limonciello
2020-06-22 14:30 ` [PATCH 1/2] thunderbolt: Add support for separating the flush to SPI and authenticate Mario Limonciello
2020-06-22 16:42 ` Mika Westerberg
2020-06-22 14:30 ` [PATCH 2/2] thunderbolt: Add support for authenticate on disconnect Mario Limonciello
2020-06-22 16:52 ` Mika Westerberg
2020-06-22 14:39 ` Mario.Limonciello [this message]
2020-06-22 16:37 ` [PATCH 0/2] Allow breaking up Thunderbolt/USB4 updates Mika Westerberg
2020-06-22 16:41 ` Mario.Limonciello
2020-06-22 17:09 ` Mika Westerberg
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=40e7c39346244df283859ffa90e26a0d@AUSX13MPC105.AMER.DELL.COM \
--to=mario.limonciello@dell.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=michael.jamet@intel.com \
--cc=mika.westerberg@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).