From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: "open list:THUNDERBOLT DRIVER" <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org, Sanju.Mehta@amd.com
Subject: Re: [PATCH v2 1/5] thunderbolt: Retry DROM reads for more failure scenarios
Date: Fri, 4 Mar 2022 16:17:45 +0200 [thread overview]
Message-ID: <YiIfiYyJrdmavuAD@lahna> (raw)
In-Reply-To: <20220303131328.4150454-1-mario.limonciello@amd.com>
Hi Mario,
On Thu, Mar 03, 2022 at 07:13:24AM -0600, Mario Limonciello wrote:
> Currently DROM reads are only retried in the case that parsing failed.
> However if the size or CRC fails, then there should also be a retry.
>
> This helps with reading the DROM on TBT3 devices connected to AMD
> Yellow Carp which will sometimes fail on the first attempt.
>
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
This and the rest of the patches applied to thunderbolt.git/next,
thanks!
prev parent reply other threads:[~2022-03-04 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-03 13:13 [PATCH v2 1/5] thunderbolt: Retry DROM reads for more failure scenarios Mario Limonciello
2022-03-03 13:13 ` [PATCH v2 2/5] thunderbolt: Do not resume routers if UID is not set Mario Limonciello
2022-03-03 13:13 ` [PATCH v2 3/5] thunderbolt: Do not make DROM read success compulsory Mario Limonciello
2022-03-03 13:13 ` [PATCH v2 4/5] thunderbolt: Clarify register definitions for `tb_cap_plug_events` Mario Limonciello
2022-03-03 13:13 ` [PATCH v2 5/5] thunderbolt: Rename EEPROM handling bits to match USB4 spec Mario Limonciello
2022-03-04 14:17 ` Mika Westerberg [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=YiIfiYyJrdmavuAD@lahna \
--to=mika.westerberg@linux.intel.com \
--cc=Sanju.Mehta@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.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