All of lore.kernel.org
 help / color / mirror / Atom feed
From: "mika.westerberg@linux.intel.com" <mika.westerberg@linux.intel.com>
To: "mohamed.rayan@siemens.com" <mohamed.rayan@siemens.com>
Cc: "andreas.noever@gmail.com" <andreas.noever@gmail.com>,
	"michael.jamet@intel.com" <michael.jamet@intel.com>,
	"YehezkelShB@gmail.com" <YehezkelShB@gmail.com>,
	"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
	"mohamed.samy@siemens.com" <mohamed.samy@siemens.com>,
	"mohamed.el_nahas@siemens.com" <mohamed.el_nahas@siemens.com>,
	"ahmed_mohammed@siemens.com" <ahmed_mohammed@siemens.com>
Subject: Re: Inquiry about tb/usb4 driver
Date: Thu, 29 Feb 2024 14:55:36 +0200	[thread overview]
Message-ID: <20240229125536.GI8454@black.fi.intel.com> (raw)
In-Reply-To: <SEZPR06MB5439B1EDA735894215D6263BF35F2@SEZPR06MB5439.apcprd06.prod.outlook.com>

On Thu, Feb 29, 2024 at 12:48:46PM +0000, mohamed.rayan@siemens.com wrote:
> Hello Mike,
> 
> Thanks for your reply,
> 
> Yes, I see a problem in my case, because When " tb_cfg_get_upstream_port", " upstream_port" variable gets updated with wrong value not the actual "upstream port" corresponding value in the Router configuration space of the USB4 host controller.

Can you share full dmesg with thunderbolt.dyndbg=+p in the command line
so we can take a look?

  reply	other threads:[~2024-02-29 12:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <SEZPR06MB5439E9D11593D4550BDCA4AFF35F2@SEZPR06MB5439.apcprd06.prod.outlook.com>
2024-02-29 12:30 ` Inquiry about tb/usb4 driver mika.westerberg
2024-02-29 12:48   ` mohamed.rayan
2024-02-29 12:55     ` mika.westerberg [this message]
2024-03-11 11:11       ` mohamed.rayan
2024-03-11 11:56         ` mika.westerberg
2024-03-11 14:03           ` mohamed.rayan
2024-03-11 14:08             ` 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=20240229125536.GI8454@black.fi.intel.com \
    --to=mika.westerberg@linux.intel.com \
    --cc=YehezkelShB@gmail.com \
    --cc=ahmed_mohammed@siemens.com \
    --cc=andreas.noever@gmail.com \
    --cc=linux-usb@vger.kernel.org \
    --cc=michael.jamet@intel.com \
    --cc=mohamed.el_nahas@siemens.com \
    --cc=mohamed.rayan@siemens.com \
    --cc=mohamed.samy@siemens.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.