From: Mika Westerberg <mika.westerberg@linux.intel.com>
To: Mario Limonciello <superm1@kernel.org>
Cc: "open list:THUNDERBOLT DRIVER" <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org,
Andreas Noever <andreas.noever@gmail.com>,
Michael Jamet <michael.jamet@intel.com>,
Yehezkel Bernat <YehezkelShB@gmail.com>,
Mario Limonciello <mario.limonciello@amd.com>,
Richard Hughes <hughsient@gmail.com>
Subject: Re: [PATCH] thunderbolt: Don't display retimers unless nvm was initialized
Date: Mon, 9 Dec 2024 08:24:15 +0200 [thread overview]
Message-ID: <20241209062415.GG4955@black.fi.intel.com> (raw)
In-Reply-To: <20241206183318.1701180-1-superm1@kernel.org>
Hi Mario,
On Fri, Dec 06, 2024 at 12:33:18PM -0600, Mario Limonciello wrote:
> From: Mario Limonciello <mario.limonciello@amd.com>
>
> The read will never succeed if nvm wasn't initialized.
Okay but we would need to understand why it was not initialized in the
first place?
I see this is ThinkPad Thunderbolt 4 Dock so probably Intel hardware? You
say you can reproduce this too so can you send me full dmesg with
thunderbolt dynamic debugging enabled? I would like to understand this bit
more deeper before we add any workarounds.
> Reported-by: Richard Hughes <hughsient@gmail.com>
> Closes: https://github.com/fwupd/fwupd/issues/8200
> Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
> ---
> drivers/thunderbolt/retimer.c | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/thunderbolt/retimer.c b/drivers/thunderbolt/retimer.c
> index 89d2919d0193e..7be435aee7217 100644
> --- a/drivers/thunderbolt/retimer.c
> +++ b/drivers/thunderbolt/retimer.c
> @@ -321,9 +321,7 @@ static ssize_t nvm_version_show(struct device *dev,
> if (!mutex_trylock(&rt->tb->lock))
> return restart_syscall();
>
> - if (!rt->nvm)
> - ret = -EAGAIN;
> - else if (rt->no_nvm_upgrade)
> + if (rt->no_nvm_upgrade)
> ret = -EOPNOTSUPP;
> else
> ret = sysfs_emit(buf, "%x.%x\n", rt->nvm->major, rt->nvm->minor);
> @@ -342,6 +340,18 @@ static ssize_t vendor_show(struct device *dev, struct device_attribute *attr,
> }
> static DEVICE_ATTR_RO(vendor);
>
> +static umode_t retimer_is_visible(struct kobject *kobj,
> + struct attribute *attr, int n)
> +{
> + struct device *dev = kobj_to_dev(kobj);
> + struct tb_retimer *rt = tb_to_retimer(dev);
> +
> + if (!rt->nvm)
> + return 0;
> + return attr->mode;
> +
> +}
> +
> static struct attribute *retimer_attrs[] = {
> &dev_attr_device.attr,
> &dev_attr_nvm_authenticate.attr,
> @@ -351,6 +361,7 @@ static struct attribute *retimer_attrs[] = {
> };
>
> static const struct attribute_group retimer_group = {
> + .is_visible = retimer_is_visible,
> .attrs = retimer_attrs,
> };
>
> --
> 2.43.0
next prev parent reply other threads:[~2024-12-09 6:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 18:33 [PATCH] thunderbolt: Don't display retimers unless nvm was initialized Mario Limonciello
2024-12-09 6:24 ` Mika Westerberg [this message]
2024-12-09 14:15 ` Mario Limonciello
2024-12-09 15:40 ` Mika Westerberg
2024-12-09 15:44 ` Mario Limonciello
2024-12-09 15:47 ` 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=20241209062415.GG4955@black.fi.intel.com \
--to=mika.westerberg@linux.intel.com \
--cc=YehezkelShB@gmail.com \
--cc=andreas.noever@gmail.com \
--cc=hughsient@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=michael.jamet@intel.com \
--cc=superm1@kernel.org \
/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