public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Francisco Blas Izquierdo Riera (klondike)" <klondike@klondike.es>
To: linux-usb@vger.kernel.org
Cc: Andreas Noever <andreas.noever@gmail.com>,
	Michael Jamet <michael.jamet@intel.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Yehezkel Bernat <YehezkelShB@gmail.com>,
	Kranthi Kuntala <kranthi.kuntala@intel.com>,
	Rajmohan Mani <rajmohan.mani@intel.com>,
	Mario.Limonciello@dell.com,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Lukas Wunner <lukas@wunner.de>, Jonathan Corbet <corbet@lwn.net>,
	linux-doc@vger.kernel.org,
	"Francisco Blas Izquierdo Riera (klondike)"
	<klondike@klondike.es>
Subject: [PATCH 0/2] Thunderbolt: allow vendor ID override for NVM programming
Date: Wed, 24 Nov 2021 17:34:23 +0100	[thread overview]
Message-ID: <8d29b41b-3590-c4b0-a2f8-fa34063bafb3@klondike.es> (raw)

Currently, the vendor ID reported by the chipset is checked before to
avoid accidentally programming devices from unsupported vendors with
a different NVM structure.

Certain Thunderbolt devices store the vendor ID in the NVM, therefore
if the NVM has become corrrupted the device will report an invalid
vendor ID and reflashing will be impossible on GNU/Linux even if the
device can boot in safe mode.

Such devices can still be programmed just fine if the vendor ID check
is overridden. Nevertheless, overriding these checks introduces the
risk of damaging controllers from other manufacturers which is a
clearly undesirable result.

Instead we allow the user to make a concious choice to override the
vendor ID by passing it as a parameter to this module. Currently,
this is done by expanding the condition to validate the vendor ID
to also check this parameter's value but, if new NVM structures
are added and a choice has to be made, the code should prefer this
parameter over the harrdware reported one when making the choice.

This patch also updates the Thunderbolt documentation to explain
how this parameter works.

root (2):
thunderbolt: allow vendor ID override for NVM programming
Documentation: explain how to override Thunderbolt Vendor ID

Documentation/admin-guide/thunderbolt.rst | 10 ++++++++++
drivers/thunderbolt/switch.c | 9 ++++++++-
2 files changed, 18 insertions(+), 1 deletion(-)

             reply	other threads:[~2021-11-24 16:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-24 16:34 Francisco Blas Izquierdo Riera (klondike) [this message]
2021-11-24 16:37 ` [PATCH 1/2] thunderbolt: allow vendor ID override for NVM programming Francisco Blas Izquierdo Riera (klondike)
2021-11-24 18:26   ` Greg Kroah-Hartman
     [not found]     ` <9b8ea990-558b-c2ba-100f-4e06c3a10f69@klondike.es>
2021-11-24 18:37       ` Greg Kroah-Hartman
     [not found]         ` <6520dbb5-d842-4ce1-c1e5-ad653eb3deca@klondike.es>
2021-11-25  6:02           ` Greg Kroah-Hartman
2021-11-25  6:16   ` Mika Westerberg
2021-11-24 16:37 ` [PATCH 2/2] Documentation: explain how to override Thunderbolt Vendor ID Francisco Blas Izquierdo Riera (klondike)

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=8d29b41b-3590-c4b0-a2f8-fa34063bafb3@klondike.es \
    --to=klondike@klondike.es \
    --cc=Mario.Limonciello@dell.com \
    --cc=YehezkelShB@gmail.com \
    --cc=andreas.noever@gmail.com \
    --cc=corbet@lwn.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=kranthi.kuntala@intel.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=lukas@wunner.de \
    --cc=michael.jamet@intel.com \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rajmohan.mani@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